docs(dr): record W3 restore smoke #431

Merged

pdurlej merged 1 commit from codex/w3/restore-smoke-report into main

2026-05-24 16:46:14 +02:00

codex commented

2026-05-24 16:31:38 +02:00

Collaborator

Canary status: missing - docs/status W3 restore-smoke report; rely on required Forgejo checks before merge

Canary Context Pack

Product story

W3 needs concrete restore evidence before destructive cleanup or broad upgrades. This PR records the first approved W3 execution slice: rerunning the existing Forgejo restore smoke under operator gate.

What changed

Adds state/reports/w3-restore-smoke-2026-05-24.md with metadata-only restore-smoke evidence.
Updates state/cycle/W3-dr-restore-confidence-output.md to mark W3b green and W3c gated.
Updates runbooks/dr-restore-test.md, state/STATUS_NOW.md, and roadmap with the current restore status.

Why it changed

The operator approved w3-restore-smoke-approved. Codex ran only the existing hp-restore-smoke.service, which restores Forgejo SQL into a disposable Postgres container and removes it on exit.

Files touched

state/reports/w3-restore-smoke-2026-05-24.md
state/cycle/W3-dr-restore-confidence-output.md
runbooks/dr-restore-test.md
state/STATUS_NOW.md
state/roadmap/current-platform-roadmap.md

Runtime evidence

Gate phrase: w3-restore-smoke-approved.
Start: 2026-05-24T14:27:36Z.
End: 2026-05-24T14:27:42Z.
Duration: 6 seconds.
Command path: systemctl start hp-restore-smoke.service.
Exit code: 0.
Systemd status: status=0/SUCCESS.
Restore image: postgres:16.12-alpine.
Backup used: /opt/vps-home-platform-infra/backups/20260524-120007-critical.
Unhealthy containers after run: 0.
Disposable restore-test-postgres container count after run: 0.
Runner/watchdog after run: active/active.

Known constraints

This proves the existing Forgejo SQL restore-smoke path only.
It does not prove Honcho memory restore.
It does not prove full sandbox OpenClaw/Iskra restore.
It did not restart production services, apply changes, promote release-root, or restore production data.

Explicit out-of-scope

Production restore.
Production service restart.
Honcho partial restore. That is W3c and requires w3-honcho-partial-restore-approved.
Full sandbox DR drill.
Legacy cleanup.

Requested decision

Merge as W3b green evidence. Next gate is w3-honcho-partial-restore-approved.

Merge blockers

Any contradiction between status, runbook, and W3 cycle output.
Any missing statement that W3 is not complete yet.
Any failed required Forgejo check.

Spec sources read

state/reports/w3-dr-restore-preflight-2026-05-24.md - W3a evidence and gates.
state/cycle/W3-dr-restore-confidence-output.md - W3 status carrier.
runbooks/dr-restore-test.md - restore cadence/runbook.
state/STATUS_NOW.md - canonical operator status.
state/roadmap/current-platform-roadmap.md - wave map and W3 next work.

Test plan

git diff --cached --check
Operator-approved W3b runtime smoke: hp-restore-smoke.service exit 0.
Post-run read-only checks: unhealthy containers 0, restore container count 0, runner/watchdog active.

Canary status: missing - docs/status W3 restore-smoke report; rely on required Forgejo checks before merge ## Canary Context Pack ### Product story W3 needs concrete restore evidence before destructive cleanup or broad upgrades. This PR records the first approved W3 execution slice: rerunning the existing Forgejo restore smoke under operator gate. ### What changed - Adds `state/reports/w3-restore-smoke-2026-05-24.md` with metadata-only restore-smoke evidence. - Updates `state/cycle/W3-dr-restore-confidence-output.md` to mark W3b green and W3c gated. - Updates `runbooks/dr-restore-test.md`, `state/STATUS_NOW.md`, and roadmap with the current restore status. ### Why it changed The operator approved `w3-restore-smoke-approved`. Codex ran only the existing `hp-restore-smoke.service`, which restores Forgejo SQL into a disposable Postgres container and removes it on exit. ### Files touched - `state/reports/w3-restore-smoke-2026-05-24.md` - `state/cycle/W3-dr-restore-confidence-output.md` - `runbooks/dr-restore-test.md` - `state/STATUS_NOW.md` - `state/roadmap/current-platform-roadmap.md` ### Runtime evidence - Gate phrase: `w3-restore-smoke-approved`. - Start: 2026-05-24T14:27:36Z. - End: 2026-05-24T14:27:42Z. - Duration: 6 seconds. - Command path: `systemctl start hp-restore-smoke.service`. - Exit code: 0. - Systemd status: `status=0/SUCCESS`. - Restore image: `postgres:16.12-alpine`. - Backup used: `/opt/vps-home-platform-infra/backups/20260524-120007-critical`. - Unhealthy containers after run: 0. - Disposable `restore-test-postgres` container count after run: 0. - Runner/watchdog after run: active/active. ### Known constraints - This proves the existing Forgejo SQL restore-smoke path only. - It does not prove Honcho memory restore. - It does not prove full sandbox OpenClaw/Iskra restore. - It did not restart production services, apply changes, promote release-root, or restore production data. ### Explicit out-of-scope - Production restore. - Production service restart. - Honcho partial restore. That is W3c and requires `w3-honcho-partial-restore-approved`. - Full sandbox DR drill. - Legacy cleanup. ### Requested decision Merge as W3b green evidence. Next gate is `w3-honcho-partial-restore-approved`. ### Merge blockers - Any contradiction between status, runbook, and W3 cycle output. - Any missing statement that W3 is not complete yet. - Any failed required Forgejo check. ## Spec sources read - `state/reports/w3-dr-restore-preflight-2026-05-24.md` - W3a evidence and gates. - `state/cycle/W3-dr-restore-confidence-output.md` - W3 status carrier. - `runbooks/dr-restore-test.md` - restore cadence/runbook. - `state/STATUS_NOW.md` - canonical operator status. - `state/roadmap/current-platform-roadmap.md` - wave map and W3 next work. ## Test plan - `git diff --cached --check` - Operator-approved W3b runtime smoke: `hp-restore-smoke.service` exit 0. - Post-run read-only checks: unhealthy containers 0, restore container count 0, runner/watchdog active.

codex added 1 commit

2026-05-24 16:31:38 +02:00

docs(dr): record W3 restore smoke

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

Details

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

Details

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

Details

canary-required / canary (pull_request) Has been skipped

Details

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