docs(waves): formally close W0 W1 W2 #429

Merged

pdurlej merged 1 commit from codex/waves/formal-close-w0-w2 into main

2026-05-24 16:13:20 +02:00

codex commented

2026-05-24 16:06:54 +02:00

Collaborator

Canary status: missing - docs/status closeout; rely on required Forgejo checks before merge

Canary Context Pack

Product story

The operator needs a single clear point where the RS2000 wave train moves out of W0/W1/W2 and into W3 DR/restore confidence. This PR records that W0 triage, W1 resource hardening, and W2 legacy inventory are formally closed.

What changed

Updates state/STATUS_NOW.md to mark W0/W1/W2 closed and W3 as next.
Marks state/cycle/W1-resource-hardening-output.md closed with runtime evidence.
Marks state/cycle/W2-legacy-inventory-output.md closed with LD0/LD1 closure evidence.
Updates state/roadmap/current-platform-roadmap.md so immediate next work is W3, not more W1/W2 closure.

Why it changed

W1 resource hardening has merged, released, backed up, dispatched, and smoked green. W2 inventory artifacts already exist; remaining legacy path work is Milestone 01 execution, not inventory discovery.

Files touched

state/STATUS_NOW.md
state/cycle/W1-resource-hardening-output.md
state/cycle/W2-legacy-inventory-output.md
state/roadmap/current-platform-roadmap.md

Runtime evidence

Captured before this PR; this PR itself performs no runtime mutation.

Release root after closeout: /opt/pdurlej-platform/current -> releases/dc7b1454e97d091c5d580e3597dd24e0bee24011.
platformctl-auto-apply.yml dispatch #1918 for voice-transcription: success.
platformctl-auto-apply.yml dispatch #1840 for karakeep: success.
home-platform-voice-transcription-1: running, healthy, NanoCpus=4000000000, Memory=6442450944, canonical compose labels under /opt/pdurlej-platform/current/compose/apps.
home-platform-karakeep-chrome-1: running, NanoCpus=1000000000, Memory=1073741824, canonical compose labels under /opt/pdurlej-platform/current/compose/apps.
tests/smoke.sh voice-transcription: 4 PASS, 0 FAIL, 3 SKIP.
tests/smoke.sh karakeep: 5 PASS, 0 FAIL, 2 SKIP.
Unhealthy containers: 0.
Deploy-runner watchdog during closeout window: only no stuck trusted-main auto-apply jobs; no positive restart.

Merged/closed PRs recorded

These were verified as merge commits on main and then closed because Forgejo's PR merge endpoint returned 405 during the maintenance window:

#423 fix(rs2000): complete W1 health metadata -> bebbd425...
#424 fix(ci): defer stateful push auto-apply -> 2ad6fdfd...
#425 fix(ci): skip merged-pr lookup for deferred auto-apply -> abe8433...
#427 fix(ci): resolve PR from direct merge commit hint -> 6824dea...
#428 fix(ci): approve direct merge commit fallback -> dc7b145...

Remaining risks

Forgejo shows those PRs as merged=false because they were closed after verified git merge commits, not merged through the PR API.
That risk is narrowed by CI fallbacks requiring a PR-shaped merge commit and PR head SHA as a non-main parent. Plain direct commits remain blocked.
Milestone 01 legacy cleanup is not complete; #387 remains the carrier and destructive cleanup is still blocked.

Known constraints

No runtime apply, promote, restart, or production mutation is part of this PR.
No legacy deletion or archival is part of this PR.
W3 DR/restore confidence is next, but this PR does not execute it.

Explicit out-of-scope

Running W3 restore drills.
Moving additional live data/config paths.
Removing legacy material.
Broad module upgrades.

Requested decision

Approve/merge as the formal W0/W1/W2 closeout and handoff to W3.

Merge blockers

Any contradiction between STATUS_NOW.md, the W1/W2 cycle docs, and the roadmap.
Any failed required Forgejo check.

Spec sources read

state/STATUS_NOW.md - canonical operator-facing status.
state/cycle/W0-triage-output.md - W0 closure baseline.
state/cycle/W1-resource-hardening-output.md - W1 closure record.
state/cycle/W2-legacy-inventory-output.md - W2 closure record.
state/roadmap/current-platform-roadmap.md - canonical wave/milestone map.

Test plan

git diff --check
literal scan for stale W1/W2 pending statuses in touched status/roadmap files

Canary status: missing - docs/status closeout; rely on required Forgejo checks before merge ## Canary Context Pack ### Product story The operator needs a single clear point where the RS2000 wave train moves out of W0/W1/W2 and into W3 DR/restore confidence. This PR records that W0 triage, W1 resource hardening, and W2 legacy inventory are formally closed. ### What changed - Updates `state/STATUS_NOW.md` to mark W0/W1/W2 closed and W3 as next. - Marks `state/cycle/W1-resource-hardening-output.md` closed with runtime evidence. - Marks `state/cycle/W2-legacy-inventory-output.md` closed with LD0/LD1 closure evidence. - Updates `state/roadmap/current-platform-roadmap.md` so immediate next work is W3, not more W1/W2 closure. ### Why it changed W1 resource hardening has merged, released, backed up, dispatched, and smoked green. W2 inventory artifacts already exist; remaining legacy path work is Milestone 01 execution, not inventory discovery. ### Files touched - `state/STATUS_NOW.md` - `state/cycle/W1-resource-hardening-output.md` - `state/cycle/W2-legacy-inventory-output.md` - `state/roadmap/current-platform-roadmap.md` ### Runtime evidence Captured before this PR; this PR itself performs no runtime mutation. - Release root after closeout: `/opt/pdurlej-platform/current -> releases/dc7b1454e97d091c5d580e3597dd24e0bee24011`. - `platformctl-auto-apply.yml` dispatch #1918 for `voice-transcription`: success. - `platformctl-auto-apply.yml` dispatch #1840 for `karakeep`: success. - `home-platform-voice-transcription-1`: running, healthy, `NanoCpus=4000000000`, `Memory=6442450944`, canonical compose labels under `/opt/pdurlej-platform/current/compose/apps`. - `home-platform-karakeep-chrome-1`: running, `NanoCpus=1000000000`, `Memory=1073741824`, canonical compose labels under `/opt/pdurlej-platform/current/compose/apps`. - `tests/smoke.sh voice-transcription`: `4 PASS, 0 FAIL, 3 SKIP`. - `tests/smoke.sh karakeep`: `5 PASS, 0 FAIL, 2 SKIP`. - Unhealthy containers: `0`. - Deploy-runner watchdog during closeout window: only `no stuck trusted-main auto-apply jobs`; no positive restart. ### Merged/closed PRs recorded These were verified as merge commits on `main` and then closed because Forgejo's PR merge endpoint returned 405 during the maintenance window: - #423 `fix(rs2000): complete W1 health metadata` -> `bebbd425...` - #424 `fix(ci): defer stateful push auto-apply` -> `2ad6fdfd...` - #425 `fix(ci): skip merged-pr lookup for deferred auto-apply` -> `abe8433...` - #427 `fix(ci): resolve PR from direct merge commit hint` -> `6824dea...` - #428 `fix(ci): approve direct merge commit fallback` -> `dc7b145...` ### Remaining risks - Forgejo shows those PRs as `merged=false` because they were closed after verified git merge commits, not merged through the PR API. - That risk is narrowed by CI fallbacks requiring a PR-shaped merge commit and PR head SHA as a non-main parent. Plain direct commits remain blocked. - Milestone 01 legacy cleanup is not complete; #387 remains the carrier and destructive cleanup is still blocked. ### Known constraints - No runtime apply, promote, restart, or production mutation is part of this PR. - No legacy deletion or archival is part of this PR. - W3 DR/restore confidence is next, but this PR does not execute it. ### Explicit out-of-scope - Running W3 restore drills. - Moving additional live data/config paths. - Removing legacy material. - Broad module upgrades. ### Requested decision Approve/merge as the formal W0/W1/W2 closeout and handoff to W3. ### Merge blockers - Any contradiction between `STATUS_NOW.md`, the W1/W2 cycle docs, and the roadmap. - Any failed required Forgejo check. ## Spec sources read - `state/STATUS_NOW.md` - canonical operator-facing status. - `state/cycle/W0-triage-output.md` - W0 closure baseline. - `state/cycle/W1-resource-hardening-output.md` - W1 closure record. - `state/cycle/W2-legacy-inventory-output.md` - W2 closure record. - `state/roadmap/current-platform-roadmap.md` - canonical wave/milestone map. ## Test plan - `git diff --check` - literal scan for stale W1/W2 pending statuses in touched status/roadmap files

codex added 1 commit

2026-05-24 16:06:54 +02:00

docs(waves): formally close W0 W1 W2

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

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) Has been skipped

Details

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