fix: verify SQLite backup before HFS startup - #6
Merged
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
1 participant
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.
Adds a fail-closed startup chain after SQLite initialization and before Uvicorn: consistent backup, manifest/integrity verification, and an isolated restore rehearsal. Startup backups use unique names and retain the newest seven; rehearsal copies stay under /tmp and never overwrite active databases. The operation ledger records backup, verify, and restore_rehearsal results for /_ops/persistence readback. Local validation: python3 scripts/static_check.py, python3 scripts/hardening_regression_test.py, and git diff --check.