d724bd0376
The Aug 2026 incident in #69603 documented a fail-open: when the pre-repair backup was refused (another same-process handle open), repair_state_db_schema() recorded backup_path=None and proceeded — leaving the writable_schema surgery, FTS-schema deletion, REINDEX and VACUUM strategies reachable against the only remaining copy of the damaged DB. _backup_db_file() now returns (path, reason) and the repair path treats any refused/failed backup as an unconditional hard stop: abort before the first mutating strategy and surface the reason in report['error']. Explicit backup=False (CLI --no-backup) is unchanged — that is the operator opting out, not a silent failure. Three new tests: refusal hard-stops with source bytes untouched, OS-level copy failure hard-stops with the reason surfaced, and backup=False still repairs.