Repository navigation
Add PPR-2 nonproduction acceptance evidence - #52
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
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.
Summary
Adds reproducible nonproduction evidence for PPR-2 account lifecycle operations and documents the proposed same-Store WordPress salt-loss recovery procedure, with actual-site validation clearly marked as outstanding.
The integration fixture exercises the real Compose/CLI/database and encryption path against disposable PostgreSQL 16.15, including scoped exports, wrong-Tenant rejection, archive-copy failure without erasure, encrypted ledger recovery, older backup restore, stopped-app replay, and repeat isolation. Cleanup removes only the test container and its temporary workspace; PostgreSQL volumes are retained.
Reported validation
The implementation report records 59 focused Jest tests, backend build, privacy and backup-crypto wrappers, export-artifact checks, connector contract checks, and the PHP 8.4 reconciliation fixture as passing. The volume-retaining cleanup correction was not rerun.
Evidence limits