Repository navigation
PAY-002B2B: add command leases, fencing, and terminal commitments - #172
Merged
Merged
Conversation
✅ Deploy Preview for luminous-fox-7c393f ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
11 tasks
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.
Outcome
Adds an unused, server-only command lifecycle foundation that keeps the PAY-002B2A registration records immutable while preventing expired or superseded workers from finalizing a command.
Security contract
Compatibility and migration
There is no runtime adoption and no data migration. Existing PAY-002B2A command roots and revision-1 audits remain byte-preserving. The new source has no endpoint or Functions index export. PAY-002B2C still owns provider-plan binding, ambiguous-send handling, reconciliation, and safe provider-attempt advancement before any Stripe call can claim retry safety.
Verification
Clock/retry amendment and redacted pre-PR evidence: #169 (comment)
Officer impact: None. This is unused server-only safety source and synthetic tests; no officer workflow or public behavior changes.
Officer documentation: None — no public content, admin duty, collected data, permission, deployment step, payment/refund operation, backup, or recovery procedure changes. Engineering and security design/status documents are updated.
Deployment evidence: Source merged as 2eff107 and exact post-merge CI passed. Production release 29273070135 passed the exact-main/CI preflight, then failed closed before checkout/build because the required public App Check site-key variable was absent. The Firebase and GitHub Pages jobs were skipped. No Netlify production deploy was recorded; a dated HTTP check showed runmprc.com still serving older main.58ede287.js and main.cdd8bda4.css assets instead of the exact-merge local build assets. No Stripe/provider setting or production data changed, and the unused source has no live behavior.
Closes #169