Repository navigation
feat: persist immutable payout intents through submit and show - #311
Merged
Merged
Conversation
Exzentttt
marked this pull request as ready for review
November 5, 2026 15:12
This was referenced Nov 5, 2026
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.
Add durable
submitandshowcommands for explicit payout intents while preserving the no-argument receipt-verification CLI. Equal namespace/allocation identities replay the same immutable UUID; changed transfer fields conflict. Success is emitted only after commit. Storage/configuration failures use finite JSON without SQL, payload, URL or traceback. Fixes #188.Add the table in unused V111 and its UPDATE/DELETE/TRUNCATE guards in a repeatable migration. All 103 existing migration files remain unchanged. Preserve current V92/V94/V107/V110 test-bootstrap dependencies and add V111 before repeatables. No dependency, global configuration, shared conftest or legacy payout changes. Application rollback retains the table, guards and data.
Validation: the frozen shared-schema implementation passed 2,523 backend tests with two skips. The later typed CLI exception-handling delta passed 237 affected tests and independent review; final current-head CI passed all five checks, including the whole backend suite. Actual PostgreSQL concurrency, commit/rollback, immutability, SQL guard mutation/restoration and SQLAlchemy pool/disposal privacy cases passed. Failed setup, quality-gate and CI attempts remain recorded; no check was waived.
Installed on production as
c1fbc58c46c9bd23b3f4cbda3813ef7028b37e77after full isolated native migration/image rehearsal, independent operator review and separate production migration/backend admissions. Root postcheck verified source hashes, schema111, internal and both public health endpoints, and preservation of all other services, volumes, skill mounts and A4 settings. Installation evidence. This is intent intake; reward accrual, signing and token transfers were not enabled.