Skip to content

docs(recovery): validate actual SQLite schema instead of stale version - #244

Draft
Adam-Ghanem wants to merge 3 commits into
mainfrom
docs/recovery-schema-version-guard-20261116
Draft

Adam-Ghanem wants to merge 3 commits into
mainfrom
docs/recovery-schema-version-guard-20261116

Conversation

@Adam-Ghanem

@Adam-Ghanem Adam-Ghanem commented Nov 16, 2026 •

Copy link
Copy Markdown
Owner

Why

The deployment guide on main says the current migration advances SQLite to version 9, while the documented isolated Track A restore drill verifies schema 10. This inconsistency can mislead recovery operators into using a stale --expected-schema value.

Change

  • Remove the fixed version-9 claim and require operators to check the actual snapshot/runtime schema and investigate mismatches.
  • Add a focused documentation regression test.
  • Fix Black formatting in the regression test on commit cd404ec0dc9f6598eba8b5075830abfe2d632089.

Verified CI — 2026-11-16

Latest branch commit: cd404ec.

  • Python CI #43795434390: completed/success (test job success).
  • Security CI #43795434379: completed/success (test job success).
  • Previous Python CI failed Black formatting on 7cafce6; fixed by cd404ec.
    These are commit-associated pull-request runs; GitHub may execute a generated merge ref. No local pytest, raw-head verification, or actual staging restore was performed.

Scope and review

Documentation and test only; no database operations, scans, deployment, credentials, paid API calls or direct main push. Based directly on main (29941838) to avoid the extensive draft backup/recovery PR stack (#199 and #239–#243). Keep draft; reconcile with existing recovery docs and actual runtime schema before merge. End-to-end recovery still requires isolated synthetic restore, authenticated readiness/inventory, audit integrity and measured RTO/RPO.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant