feat(prime): require negotiated correlated lifecycle proof - #191
Merged
Conversation
Contributor
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
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.
Closes #190.
Summary
negotiated_daemon_session_capabilities_v1before strict correlated mode can be selectedsupportsNegotiatedCapability("correlated_prompt_lifecycle_v1")proofCoordination
91e13b6798343995291ccca6f523fba81ff96cd6c46497e2870618bb2caa9d59d161fc5abfad27472eec7deff39cfb1380ebe70cValidation
Exact rebased head:
f34744ac774b0570c0608ccc8def509d3ae88ece/ tree55441e2a8997551d36cc2b846981fc03323b55fcCombined
origin/pylon...HEADbinary diff SHA-256:ed9828372a0e6152acc8977bede14d43af1f2753da072f52d3b754eeb2c9dc34Commit patch SHA-256 values:
1dc7a49cb9a4c5f392821d05b53118df862e7b4130ba2be65636e1f412551755d95fbe76904d4923527cd029a6005df3d08e83f46d8a32e44703df5189149853Local results on the exact rebased head:
git diff --check: passedsrc/environmentTheme.test.tswatcher timeoutThe theme watcher file and its implementation/config/dependency files are byte-identical to current
origin/pylon. The isolated watcher failure reproduced on a cleanorigin/pylonworktree; one baseline run passed and later baseline/branch runs timed out. No branch-owned path intersects the 97 upstream paths added during rebase.Review
Five independent P0/P1 reviews approved the exact rebased HEAD/tree/combined hash: API, security, design, adversarial, and test coverage. Any tree change invalidates those approvals and requires a fresh exact-head gate.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.