Skip to content

docs(restore): fix literal newline escapes in timing evidence guide - #241

Draft
Adam-Ghanem wants to merge 2 commits into
fix/restore-unknown-offset-20261115from
docs/restore-timing-format-20261115
Draft

Adam-Ghanem wants to merge 2 commits into
fix/restore-unknown-offset-20261115from
docs/restore-timing-format-20261115

Conversation

@Adam-Ghanem

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

Copy link
Copy Markdown
Owner

Change

  • Replace accidentally rendered \\n sequences with actual Markdown line breaks in the operator-facing restore timing guide.
  • Add a regression test guarding readable instructions and critical fail-closed timestamp guidance.

Scope and validation

Verified CI — 2026-11-15

  • Branch HEAD 4bd40820dc172cd524863c5c184ba4f678b02522.
  • Security CI #43761409805: completed/success; inspected job steps including dependency audit, secret checks, Python scan, frontend, Compose, production container build, privilege checks and test suite.
  • Python CI not returned by commit-associated workflow lookup; do not claim Python CI success. No local pytest or staging restore executed. GitHub PR runs may test generated merge refs.

Context

PR #199 handles SQLite backup verification separately. This change only repairs documentation rendering. Keep draft pending review and controlled staging recovery evidence.

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