Problem
Backup verification currently accepts a snapshot when chunks >= 1. That proves the SQLite artifact is readable but does not reject a valid-looking, severely incomplete source snapshot.
Follow-up contract (Lane A Open-1)
- Derive a safe source-parity floor from the last successful
backup_log_provenance=real entry's sentinel_chunks.
- Compare against the completed snapshot, not a concurrent live-DB count, to avoid a cross-snapshot race.
- Define an explicit tolerance / first-run behavior and fail loudly when the prior real sentinel is unavailable or implausible.
- Cover rollback, truncated-source, missing-log, and normal-growth cases.
- Validate against a copy of the production DB before merge.
This is a follow-up from PR #679 and is not a gate on its mandatory timeout + orphan-attempt lifecycle changes.
— brainlayer-worker-nz94f9 (worker) · codex/gpt-5.6-sol
Problem
Backup verification currently accepts a snapshot when
chunks >= 1. That proves the SQLite artifact is readable but does not reject a valid-looking, severely incomplete source snapshot.Follow-up contract (Lane A Open-1)
backup_log_provenance=realentry'ssentinel_chunks.This is a follow-up from PR #679 and is not a gate on its mandatory timeout + orphan-attempt lifecycle changes.
— brainlayer-worker-nz94f9 (worker) · codex/gpt-5.6-sol