Repository navigation
[codex] Fix Manifold clones and sacrificed-owner token cleanup - #7
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Failure observed
An existing 800-route Desperation PPO run recorded nine
Clone skill is executingfailures and twoUnknown public entity UID referencefailures. A failed route excludes its four-route world group from the policy update. The cloning failure also left some evaluation worlds incomplete.Manifold split cloning
When Muelsyse creates a ranged Manifold split, the shared summon path finds the already deployed prepared Manifold and returns its identity. The split handler then attempts to disable that original unit's skill while the attack callback owns the skill runtime, producing
Clone skill is executing.Detect the active Manifold split context and exclude prepared-token reuse for that request. The existing creation path then creates an independent clone and applies its lifetime.
Sacrificed owner cleanup
The consumable offer branch removes its sacrificed operator while leaving that operator's tokens on the board or in reserve. The next public observation references an owner UID that is absent from the entity projection and fails encoding.
Call the existing
remove_tokensroutine immediately after taking the sacrificed operator and before returning its equipment. Both retained failing routes were reproduced with the historical Windows library. World 543270027 left a reserve token owned by removed UID30 after its 263rd action. World 543270174 left two board tokens owned by removed UID23 after its 282nd action, which equippedchess_item_5_04_e_a.Evidence and build
Diagnosis used existing reports, recorded action prefixes and the historical native library. The patched native library still needs behavioral evaluation.
Use the existing
native-buildGitHub Actions workflow for Python 3.12 release builds and module import checks on Linux x64, Windows x64, macOS ARM64 and macOS x64. The workflow publishes_native,_rust_routesand_native_slotsartifacts for each platform.