forge-recoverylisted

# forge-recovery: Backup and recovery ## Purpose Verify recoverability of data and service against explicit RPO, RTO, corruption, deletion, and regional scenarios. Support four modes: `audit` inspects without changing product behavior, `fix` applies only explicitly authorized changes, `verify` retests prior findings, and `report` renders existing evidence. If no mode is supplied, use `audit`. ## Trigger conditions Use this module when a request names `forge-recovery`, asks about backup and recovery, or discovery finds an applicable boundary. Run it from the repository root after project discovery. ## When it applies - Durable production data or stateful critical services ## When it does not apply - Reproducible stateless artifacts with no unique data Do not silently skip it. Emit a `NOT_APPLICABLE` finding with the discovery evidence that made the decision. ## Inputs from project discovery - data inventory - backup configuration - restore and disaster runbooks Prefer `.forge/project-profile.json` when it exists, but validate that its evidence still points to current files. Read `../fullstack-forge/references/PROTOCOL.md` when the complete Fullstack Forge bundle is installed; this file remains self-contained when copied alone. ## Inspection procedure 1. Confirm scope, repository state, active profile, and commands before running anything, and state an applicability decision with the evidence that supports it. 2. Inventory data stores and their backup mechanisms,