docs(recovery): re-review init-safety playbooks; refresh the 90-day marker
The Last-reviewed marker crossed the 90-day freshness threshold on Sep 7, turning 'Check doc flags freshness' (and with it PR Policy and the required CI Gate) red for EVERY open PR — #6262 is merge-queued and UNSTABLE on exactly this. Reviewed against the declared freshness sources (init.go, init_safety.go, init_safety_test.go, dolt.go), which changed materially since June (notably the destructive-preflight replacement in #5310 and the server-flag precedence work): the four playbooks' premises still hold — --destroy-token/--reinit-local/--discard-remote all exist and are the refusal remedies, the force-refusal-on-origin-history invariant is intact, and the pk-fork-refused deep link from dolt.go:416 resolves. One drift noted, not a correctness issue: the three init-* anchors are no longer deep-linked from refusal messages post-#5310 (bd help init-safety links the doc generically); a fuller playbook revalidation against the new preflight wording is follow-up material, not a blocker. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
parent
c0d8da42de
commit
94d76b5a4d
1 changed files with 1 additions and 1 deletions
|
|
@ -3,7 +3,7 @@ title: Recovery Playbooks
|
|||
description: Step-by-step recovery for bd init and bd dolt push/pull refusals, including the primary-key fork playbook
|
||||
---
|
||||
|
||||
Last reviewed: 2026-06-09
|
||||
Last reviewed: 2026-09-08
|
||||
|
||||
Freshness source: `cmd/bd/init.go`, `cmd/bd/init_safety.go`,
|
||||
`cmd/bd/init_safety_test.go`, and `cmd/bd/dolt.go`.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue