Repository navigation
Conversation
…e with immutable source witnesses
…s and retain evidence
… criterion mappings
…eptance criteria without widening scope
…tract requirements
…ations before restore
…ackup destinations
…osed on unknown or unmapped requirements
…lds for acceptance criteria
…d case-insensitive mounts
…-bound independent review receipts
…ing source-bound reviews
…ess to acceptance gate
…d role attestations
…D, and require post-matrix acceptance
…acceptance boundary
…s independent attestation
…terialization writes
This branch has not been deployed
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.
Scope
Hardening of accepted T04 State Engine V2 on top of T01–T04 development baseline. Addresses AUD-05 ledger scalability, AUD-06 multiprocess locking/sequencing, AUD-07 backup restore realpath boundaries, and crash-recovery durability. T05+ excluded.
This is a cumulative validation PR against main because existing CI only triggers there. Do not merge this cumulative PR until the approved release integration gate.
Verification
Red regression tests first, followed by bounded fixes, independent review and full Windows/Ubuntu
npm run release:validate. No release/version bump.