Repository navigation
Persist verified legacy execution correlation in Action slot - #216
Merged
pcvantol merged 1 commit intoOct 1, 2026
Merged
Conversation
pcvantol
deleted the
codex/forge-serial-execution-slot-migration-20261001
branch
October 1, 2026 18:53
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
1 participant
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.
Forge LANE_3 assignment
Implements
L3-FORGE-SERIAL-EXECUTION-SLOT-MIGRATION-V1-20261001(registration revision 8, plan revision 1) in #207.An explicit Forge runtime entrypoint copies one unambiguous existing serial Mission/Action correlation into an immutable, Action-keyed execution slot. Schema 42 adds the storage, integrity checks and reset classification/fences. Replay of identical source is idempotent; ambiguous or changed source fails without a partial write. The existing serial scheduler and EP adapter are unchanged. Authenticated installed Mission detail exposes only migration status and selected identities, with no private request bytes or derived digests.
Evidence
bash scripts/validate.sh: 1069 tests passed, one existing skip; product version 2.7.46 and generated projection PASS.f4aaadcf5cdf5f49078beded571afa4daa0c6938. The initial Security finding about private-derived digests in the migration receipt was fixed and both reviewers re-reviewed the exact head.e3b41fcfdbbccdbbed97d4d176fc22ad2bacf7f4on main. Exact merge source built into noneditableforge_autonomy-2.7.46-py3-none-any.whl, SHA-2563ad2065db5694f6a7dd47b6fb62882418a9ef968dd08722f2246f79e1ba7dc56. Fresh isolated installed Python-Iproved ambiguous legacy state rejects with zero slots, valid migration and identical replay, and a separate installed process served real loopback HTTP: safe positive 200, wrong bearer 401, deliberate synthetic stored-digest corruption 409MISSION_EXECUTION_SLOTS_INVALID, with no private prompt, credential or derived digest leakage.No Mission lifecycle change, producer grant, host execution, peer source change, production runtime migration or full PA-F1/F2/F3 qualification is claimed.