Skip to content

test(recovery): record bounded offline RTO/RPO drill timing evidence - #239

Draft
Adam-Ghanem wants to merge 15 commits into
mainfrom
test/restore-rto-rpo-evidence-20261115
Draft

Adam-Ghanem wants to merge 15 commits into
mainfrom
test/restore-rto-rpo-evidence-20261115

Conversation

@Adam-Ghanem

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

Copy link
Copy Markdown
Owner

Scope

Add a pure offline CLI that calculates observed recovery timing from explicitly timezone-aware operator evidence, with regression tests for offsets, invalid timestamps and impossible ordering. Add an isolated staging runbook that distinguishes measurements from actual restore/readiness/audit proof.

Verified CI — 2026-11-15

Commit-associated head: 306651467add44cd8e5e355a723accaf1b4985a4.

  • Python CI #43687821285: completed/success. Inspected job steps: formatting/imports, lint/type-check, compilation, tests with coverage and Codecov upload all succeeded.
  • Security CI #43687821223: completed/success. Inspected job steps: dependency audit, secret boundary check, Python scan, frontend JS, Compose, production container build, privilege checks and test suite all succeeded.

These are commit-associated PR runs and may use GitHub-generated merge refs, not a separately tested raw HEAD checkout. No local pytest executed.

Safety and review gates

No database access, network calls, active recovery, production actions, credentials, or provider spend. This does not duplicate the stacked backup verifier PR #199–#228. Does not claim end-to-end recovery acceptance. Require controlled staging restore, authenticated application checks, audit integrity, and measured RTO/RPO evidence before recovery acceptance. Leave draft for review; no direct main push, merge or deployment.

Additional CLI regression coverage — 2026-11-15

Commit b59dc0c adds focused tests for JSON stdout, RTO/RPO values, fail-closed exit code 2 and no JSON on malformed or out-of-order operator timestamps. Existing isolated staging runbook documents the CLI and limitations. CI for this new head has not yet been confirmed; previous green runs above apply only to 3066514.

Latest head CI verification — 2026-11-15

Commit b59dc0c7697ee9970884a7bbefcd4e59b9d2ae53:

  • Python CI #43701681322: completed/success. Verified job steps: formatting/imports, lint/type-check, compilation, tests with coverage and Codecov upload.
  • Security CI #43701681311: completed/success. Verified job steps: dependency audit, secret boundaries, Python scan, frontend/Compose checks, production container build, privilege checks and test suite.
    These are commit-associated pull-request workflow runs and may execute on GitHub-generated merge refs. No local pytest or isolated staging restore executed. Authenticated application recovery, audit integrity and actual RTO/RPO acceptance remain unverified.

Latest head CI — 2026-11-15 13:56 UTC

  • Exact branch HEAD 732a94b7a650e857485e46f09303d00f8c64101a.
  • Python CI #43716852034: completed/success (commit-associated).
  • Security CI #43716852018: completed/success (commit-associated).
  • Re-read CLI and boundary regression tests on feature branch. No local full pytest or isolated staging restore run. GitHub PR workflows may test generated merge refs, so green checks do not establish raw-HEAD execution or end-to-end recovery.
  • Keep draft; next gate remains synthetic isolated restore with authenticated readiness/inventory, audit verification and measured RTO/RPO. No production action or API spend.

Strict timestamp evidence parsing — 2026-11-15

  • Latest branch HEAD: 6bcfddd.
  • Reject ambiguous datetime separators, week dates, offset seconds, oversized trailing input, and fractional precision above six digits. Preserve timezone-aware seconds and microseconds.
  • Added regression tests and clarified offline drill documentation. No network calls, restores, credentials, or paid API requests.
  • CI on this new head not yet confirmed; earlier green checks apply to 732a94b only. Do not mark verified until Python/Security CI for this exact commit succeeds. Keep draft.

CI verification on current head — 2026-11-15 18:01 UTC

  • Head bbe2611638ba5d974133355981e825b85d6084f5.
  • Python CI #43738894654: completed/success. Verified job steps: formatting/imports, lint/type check, compile, pytest with coverage, Codecov.
  • Security CI #43738894779: completed/success. Verified job steps: dependency audit, secret boundaries, Python security scan, frontend, Compose, container build, privilege checks, test suite.
  • These are commit-associated PR runs, potentially testing GitHub's generated merge ref. No local pytest or staging restore executed. Keep draft pending manual review and isolated restore acceptance; no production recovery claims.

Copy link
Copy Markdown
Owner Author

2026-11-15 follow-up: commit 6bcfddd had Python CI failure (run #43727264836) at Check formatting and imports; subsequent lint, mypy and pytest steps were skipped. Security CI #43727264929 succeeded. Pushed targeted Black-style parametrization fix in f4fcb7c. This is a suspected formatting culprit, not yet confirmed from raw logs; CI on the new head is pending. No local Black/pytest (offline environment lacks Black and package installation access). Keep draft; do not infer passing tests.

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