Refresh verified stack components and foreground same-case review - #86
Merged
Merged
Conversation
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.
Refresh Rail and MandateBound to their reviewed, CI-verified producer merges. Consumer checks now cover canonical bytes, currency validation, contradictory signed evidence and replay of a case exported with previous pins. The documentation follows one rail case through compensation, review, export and replay, and explains fail-closed handling of legacy canonicalization differences. The Constitutional component pin and CLI defaults are unchanged.
Update the connector example for consumed recourse: same-key retries return the original remedy; a new key is refused without restoring inventory twice. GUI copy clarifies the separate response-fixture policy gate, and documentation accounts for local command writes.
Validation: four compatibility checks passed, three failing against the original pins; 181 unit passes with six explicit platform skips; clean detached bootstrap with zero npm advisories; full committed-candidate integration; refund/inventory handoff and expected refusal; all 13 real Chromium workflows. The corrected connector example passes all six rules, independently repeated. No production connector, new authorization protocol, or deployment is included.