fix: expose exact lifecycle tool contracts - #130
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.
Observed blocker
Fresh real Codex attempt 4 on
main@e052299completed five role bootstraps and registered the sole kickoff turn, then failedthreadmesh_lifecycle_publication_action_mismatchbefore the first event-pump dispatch. The live model selected the kickoff tool without being given the exact coordinator-bound lifecycle arguments required by the existing fail-closed publication contract. Normal cleanup passed 5/5.Bounded correction
Evidence
npm test: 379/379 tests, schemas/transitions/docs clean;Boundary
This does not add a protocol field, relax lifecycle authority, script a phase prompt, add an adapter, or claim a live chain pass. A fresh real run is still required.