Repository navigation
Release 0.2.28: bounded final recovery allowance and fenced SCM writes - #40
Merged
Merged
Conversation
added 9 commits
October 20, 2026 12:14
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.
A current native factory administrator can reserve one final fifth Codex or Claude dispatch after a known, drained fourth-attempt process failure. Reservation spends the allowance immediately and seals it with the linked admission and implementation intent in one WAL transaction. Current source, executable and operator authority remain required; there is no sixth dispatch. Legacy recovery and worker-feedback contracts retain their four-attempt limit, with a separate allowance-bound feedback variant for attempt five.
Studio guides review of the failed attempt, mitigation and final confirmation. It retains the original request before its single POST and supports exact readback after an uncertain response or lost browser storage. The SDK exposes separate candidate, reservation and receipt methods.
Owned source-control writes now preserve their ownership requirement across token preparation and the final authority callback, then revalidate the native PostgreSQL fence before the POST. Releasing the lease, losing its connection or draining the owner stops the write, including when the Engine poller has stopped. Existing unowned manual writes keep their authorization path. PostgreSQL checks and remote provider writes remain separate boundaries.
Validation for
66366f11f96745809933002c6ecfcb62707dc7b5:The administrator's mitigation attestation does not establish that the mitigation fixed the failure or that the generated product passed QA. Live provider recovery and generated-product acceptance require separate execution evidence. Release publication remains pending.