Conversation
James3014
force-pushed
the
codex/issue-115-pr-delivery-g0-g3
branch
from
September 15, 2026 04:58
509e878 to
e9b03b2
Compare
added 2 commits
September 15, 2026 14:06
…le-before-retry (#115)
James3014
force-pushed
the
codex/issue-115-pr-delivery-g0-g3
branch
from
September 15, 2026 06:14
e9b03b2 to
e4a9897
Compare
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.
Controllers could push an accepted Candidate but discover only at the end that PR delivery was unavailable. This adds a bounded G0-G3 core milestone: an effect-free delivery preflight that truthfully separates read readiness from unproven write capability, plus one durable PR-delivery primitive built on the existing DurableOperationStore (same operationId, attemptKey, requestHash, createOrReplay, outcome_unknown, and replay-conflict semantics; no second ledger).
The primitive binds the exact Candidate (repository, base/head branches and SHAs, title, body, optional Issue), revalidates remote identity immediately before any write and refuses on drift with zero creates, and reconciles lost acknowledgements against exact remote PR state so a successful remote create is never duplicated. Only a proven CONFIRMED_NO_EFFECT permits safe retry on the same attempt. No MCP exposure, no merge authority, no CI or live claims.