docs(dr): accept W3 immediate restore gate #434

Merged

pdurlej merged 1 commit from codex/w3/accept-immediate-gate into main

2026-05-24 18:27:38 +02:00

codex commented

2026-05-24 18:22:58 +02:00

Collaborator

Canary status: missing - rely on required Forgejo checks before merge

Canary Context Pack

Product story

W3 restore-confidence work is now good enough for non-destructive Milestone 01 progress, but future agents need a clear stop line before irreversible cleanup and W8 upgrades.

What changed

Records W3a/b/c as the accepted immediate restore-confidence gate.
Moves W3d full sandbox DR into issue #433.
Closes the stale #45/#238 framing in status/roadmap language.
Adds m01-destructive-cleanup-gate wording to ADR-0020 and the cleanup plan.

Why it changed

Pan Herbatka's PR #432 comment #9292 accepted W3a/b/c for the immediate gate while requiring W3d before irreversible cleanup or broad module upgrade waves.

Files touched

state/STATUS_NOW.md
state/cycle/W3-dr-restore-confidence-output.md
state/roadmap/current-platform-roadmap.md
state/cutover/rs2000-post-soak-legacy-cleanup.md
decisions/0020-post-soak-legacy-cleanup-and-platform-modularization.md

Relevant context

PR #430 W3 preflight
PR #431 W3b restore smoke
PR #432 W3c Honcho partial restore
PR #432 comment #9292
New W3d follow-up issue #433

Runtime evidence

No runtime mutation in this PR. Existing accepted evidence:

W3b: hp-restore-smoke.service exit 0/SUCCESS, disposable restore cleanup, zero unhealthy containers.
W3c: Honcho pgvector backup restored into isolated disposable target, metadata-only checks green, zero unhealthy containers.

Known constraints

W3a/b/c do not prove coordinated full sandbox DR.
Destructive Class A/B/D cleanup remains blocked until W3d-equivalent evidence and m01-destructive-cleanup-approved.
W8 broad upgrades remain blocked until W3d-level DR confidence and metadata foundations.

Explicit out-of-scope

No production restore.
No production restart.
No legacy delete/prune/rename.
No W3d execution.

Requested decision

Approve merge if required checks pass. This is documentation/status closeout for the W3 immediate gate.

Merge blockers

Any statement that suggests full DR is proven by W3a/b/c.
Any weakening of the destructive cleanup gate.
Any accidental closure of #433.

Spec sources read

PR #432 comment #9292 - Pan Herbatka verdict and gate wording.
state/STATUS_NOW.md - operator-facing current status.
state/cycle/W3-dr-restore-confidence-output.md - W3 evidence artifact.
state/roadmap/current-platform-roadmap.md - durable wave/milestone plan.
state/cutover/rs2000-post-soak-legacy-cleanup.md - cleanup gate plan.
decisions/0020-post-soak-legacy-cleanup-and-platform-modularization.md - accepted cleanup ADR.

Refs #433.

Canary status: missing - rely on required Forgejo checks before merge ## Canary Context Pack ### Product story W3 restore-confidence work is now good enough for non-destructive Milestone 01 progress, but future agents need a clear stop line before irreversible cleanup and W8 upgrades. ### What changed - Records W3a/b/c as the accepted immediate restore-confidence gate. - Moves W3d full sandbox DR into issue #433. - Closes the stale #45/#238 framing in status/roadmap language. - Adds `m01-destructive-cleanup-gate` wording to ADR-0020 and the cleanup plan. ### Why it changed Pan Herbatka's PR #432 comment #9292 accepted W3a/b/c for the immediate gate while requiring W3d before irreversible cleanup or broad module upgrade waves. ### Files touched - `state/STATUS_NOW.md` - `state/cycle/W3-dr-restore-confidence-output.md` - `state/roadmap/current-platform-roadmap.md` - `state/cutover/rs2000-post-soak-legacy-cleanup.md` - `decisions/0020-post-soak-legacy-cleanup-and-platform-modularization.md` ### Relevant context - PR #430 W3 preflight - PR #431 W3b restore smoke - PR #432 W3c Honcho partial restore - PR #432 comment #9292 - New W3d follow-up issue #433 ### Runtime evidence No runtime mutation in this PR. Existing accepted evidence: - W3b: `hp-restore-smoke.service` exit `0/SUCCESS`, disposable restore cleanup, zero unhealthy containers. - W3c: Honcho pgvector backup restored into isolated disposable target, metadata-only checks green, zero unhealthy containers. ### Known constraints - W3a/b/c do not prove coordinated full sandbox DR. - Destructive Class A/B/D cleanup remains blocked until W3d-equivalent evidence and `m01-destructive-cleanup-approved`. - W8 broad upgrades remain blocked until W3d-level DR confidence and metadata foundations. ### Explicit out-of-scope - No production restore. - No production restart. - No legacy delete/prune/rename. - No W3d execution. ### Requested decision Approve merge if required checks pass. This is documentation/status closeout for the W3 immediate gate. ### Merge blockers - Any statement that suggests full DR is proven by W3a/b/c. - Any weakening of the destructive cleanup gate. - Any accidental closure of #433. ## Spec sources read - PR #432 comment #9292 - Pan Herbatka verdict and gate wording. - `state/STATUS_NOW.md` - operator-facing current status. - `state/cycle/W3-dr-restore-confidence-output.md` - W3 evidence artifact. - `state/roadmap/current-platform-roadmap.md` - durable wave/milestone plan. - `state/cutover/rs2000-post-soak-legacy-cleanup.md` - cleanup gate plan. - `decisions/0020-post-soak-legacy-cleanup-and-platform-modularization.md` - accepted cleanup ADR. Refs #433.

codex added 1 commit

2026-05-24 18:22:58 +02:00

docs(dr): accept W3 immediate restore gate

base-is-main / guard (pull_request) Successful in 1s

Details

canary-required / collect-diff (pull_request) Successful in 5s

Details

patchwarden-pr-sanity / collect-diff (pull_request) Successful in 4s

Details

canary-required / canary (pull_request) Successful in 14s

Details

patchwarden-pr-sanity / sanity (pull_request) Successful in 22s