5d9a2110ba
Refs #100368. The forensics thread established that a sqlite3 CLI with the WAL-reset opener bug (fixed 3.51.3+ / backports 3.50.7 / 3.44.6; Debian/Ubuntu system shells 3.45.1/3.46.1 are in the vulnerable band) unlinks the live -wal/-shm pair when pointed at a live state.db whose writer's DMS lock has been cancelled, splitting the store into two concurrent generations whose acknowledged writes vanish while both report integrity_check ok. Hermes' own corruption banners instructed exactly that command. - gateway corruption broadcast, run_agent corrupt-cause explanation, hermes_state repair-budget and forensic-backup refusals, and the kanban manual-recovery hint now route operators to `hermes sessions recover --source <db>` (which snapshots the damaged bundle before any shell touches it) and warn against a raw sqlite3 shell on the live file - find_sqlite3_cli() now refuses a WAL-reset-vulnerable shell for the page-level salvage lane even on the snapshot, reusing the canonical gate from hermes_cli.sqlite_runtime so the embedded runtime and the salvage shell can never disagree - find_sqlite3_cli_refusal() records why a shell was refused so the lost_and_found lane can tell the operator exactly what to install instead of a generic "not found" - regression tests cover the version gate (vulnerable/fixed matrix, the mirror check), every refusal reason, and each guidance site Test plan: - scripts/run_tests.sh tests/hermes_cli/test_sqlite3_cli_salvage_gate.py tests/test_state_db_repair_loop_cap.py tests/run_agent/test_corruption_recovery_guidance.py tests/hermes_cli/test_session_recovery_lost_and_found.py tests/hermes_cli/test_session_recovery.py tests/test_sqlite_wal_reset_gate.py tests/hermes_cli/test_sqlite_runtime.py - 91 passed, 1 skipped locally (cherry picked from commit e62940d1021e80e9b7d6423ced1cbdfe7dd0c37d)