Repository navigation
docs(recovery): validate actual SQLite schema instead of stale version - #244
Draft
Adam-Ghanem wants to merge 3 commits into
Draft
Adam-Ghanem wants to merge 3 commits into
Adam-Ghanem wants to merge 3 commits into
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.
Why
The deployment guide on
mainsays 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-schemavalue.Change
cd404ec0dc9f6598eba8b5075830abfe2d632089.Verified CI — 2026-11-16
Latest branch commit:
cd404ec.7cafce6; fixed bycd404ec.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.