Repository navigation
Complete exact execution reservations on coordinated target ownership - #12
Merged
Merged
Conversation
added 9 commits
November 6, 2026 11:36
…ng-completion-20261106
…nding-completion-20261106
…ng-completion-20261106
SaiFlyBy
marked this pull request as ready for review
November 6, 2026 17:41
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.
New opt-in missions bind complete transport identity and launch intent to the accepted coordination authority in one durable transaction. Exact reservation selectors fence lifecycle mutations, settlement, retry and lookup; scope proofs, changed-base handoffs and dependency delivery preserve that binding and accepted evidence.
This completes the original dirty-v17 binding mechanism and revision3 session/terminal observations, independent ContextReceipt session mapping, accepted/history lookup and definite no-launch recovery. Recovery preserves immutable replayable receipts and the same attempt with a new fence/intent. Provider failure/cancellation cannot establish ACCEPTED. Existing frozen v16/v18/v19/v20 contracts remain unchanged; explicit opt-in composition declares v21, including optional lineage.
Provider authentication, actual launch and writer termination remain trusted adapter/operator responsibilities. Adapter records and the independent exact-generation writer-domain fence retain separate evidence, allowing delayed observations after safe release. Repository relinquishment keeps its all-claims guard, including never-reserved and archived reservations.
Independent review found no remaining material issues after selector-bypass, registration, delayed-observation and release-replay fixes. Candidate848a3917c311d50a1a8f1edea699d47c85ac86da is serially based on accepted main364f3177; its full tree matches5fe1cba and only the reservation scope remains in the diff.
Validation on exact clean848a3917: reservation/adoption protocol PASS (107.6s); reservation+lineage handoff/qualification/CLOSED PASS (137.1s). Hosted full bridge Linux and Windows PASS (42262526793), including v16 compatibility, coordination, dependency delivery, all lineage modes, reservations and real Worktrunk ordinary/changed-base golden flows. Required normal CI, including full Rust Linux/Windows, lint, feature checks and lockfile/doctests/rustdoc PASS (42262526990). Release plan, coverage and advisory affected Linux/Windows PASS. Skipped conditional checks and canceled duplicate runs are retained separately and not counted as passes.