Repository navigation
test(recovery): record bounded offline RTO/RPO drill timing evidence - #239
Draft
Adam-Ghanem wants to merge 15 commits into
Draft
Adam-Ghanem wants to merge 15 commits into
Adam-Ghanem wants to merge 15 commits into
Conversation
Owner
Author
|
2026-11-15 follow-up: commit |
This was referenced Nov 15, 2026
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.
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.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
b59dc0cadds 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 to3066514.Latest head CI verification — 2026-11-15
Commit
b59dc0c7697ee9970884a7bbefcd4e59b9d2ae53: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
732a94b7a650e857485e46f09303d00f8c64101a.Strict timestamp evidence parsing — 2026-11-15
6bcfddd.732a94bonly. 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
bbe2611638ba5d974133355981e825b85d6084f5.