Repository navigation
docs(restore): fix literal newline escapes in timing evidence guide - #241
Draft
Adam-Ghanem wants to merge 2 commits into
Draft
Adam-Ghanem wants to merge 2 commits into
Adam-Ghanem wants to merge 2 commits into
Conversation
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.
Change
\\nsequences with actual Markdown line breaks in the operator-facing restore timing guide.Scope and validation
fix/restore-unknown-offset-20261115) to avoid duplicating unmerged changes. Do not merge until parent is reconciled.Verified CI — 2026-11-15
4bd40820dc172cd524863c5c184ba4f678b02522.Context
PR #199 handles SQLite backup verification separately. This change only repairs documentation rendering. Keep draft pending review and controlled staging recovery evidence.