Skip to content

test(recovery): fail closed on unknown offsets across CLI fields - #243

Draft
Adam-Ghanem wants to merge 2 commits into
test/restore-unknown-offset-all-fields-20261115from
test/restore-cli-offset-fields-20261115
Draft

Adam-Ghanem wants to merge 2 commits into
test/restore-unknown-offset-all-fields-20261115from
test/restore-cli-offset-fields-20261115

Conversation

@Adam-Ghanem

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

Copy link
Copy Markdown
Owner

Change

  • Add CLI-level regression coverage for unknown -00:00 in each of --last-durable, --failure, and --ready: exit 2, no JSON, no traceback.
  • Verify known +00:00 remains accepted with unchanged timing arithmetic.
  • Document operator-facing offset contract and limits.

Dependency and safety

Stacked on draft #242 → #241 → #240 → #239; separate from backup verifier #199. No restore, network scan, credentials, remediation, deployment or API spend. Do not merge until parents are reviewed.

Verified CI — 2026-11-16

  • Latest commit 777e354692bdaebaa0d872536b36c6c1c6ae2508.
  • Security CI #43777287857: completed/success. Inspected test job: dependency audit, secret checks, Python security scan, compilation, frontend JS, Compose, production container build, privilege checks and test suite all succeeded.
  • Commit-associated lookup returned no Python CI. Do not infer Python CI success. GitHub PR runs may use generated merge refs; no raw-head local pytest or isolated staging recovery performed.

Outstanding gate

Controlled isolated staging restore using synthetic SQLite data, authenticated readiness and inventory, audit integrity verification, and measured RTO/RPO. CI is not evidence of end-to-end recovery.

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