fix(rs2000): prepare W1 resource closeout #422

Merged

pdurlej merged 1 commit from codex/waves/formal-closeout into main

2026-05-24 14:28:57 +02:00

codex commented

2026-05-24 14:26:20 +02:00

Collaborator

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

Canary Context Pack

Product story

Operator wants the post-cutoff waves to stop drifting between old F/F2/F3 plans, Claude feedback, and current chat shorthand. W0 should be formally closed, W1 should finish real RS2000 resource hardening, and W2 should be ready to close from LD0/LD1 evidence without pretending legacy deletion is safe.

What changed

Canonicalized the W0-W9 wave map in state/roadmap/current-platform-roadmap.md and reconciled Claude feedback.
Marked W0 closed in state/cycle/W0-triage-output.md.
Added W1/W2 cycle artifacts with explicit closure gates.
Updated STATUS_NOW.md to point future forks at the durable wave map.
Added canonical compose resource limits for karakeep-chrome.
Imported live voice-transcription into canonical compose with the existing tailnet API, volumes, healthcheck, and resource limits.
Added tests for the W1 resource contract and updated the deploy-control test to match LD1 runtime-root mounts.

Why it changed

Read-only evidence showed W1 was not actually closable: karakeep-chrome had no CPU/memory limit and live voice-transcription still carried legacy/orphan compose metadata. Closing the wave as docs-only would have hidden real drift from future agents.

Files touched

compose/apps/compose.yaml
compose/base/compose.yaml
modules/voice-transcription/module.yaml
modules/voice-transcription/runbook.md
modules/karakeep/runbook.md
tests/test_wave_resource_contract.py
tests/test_deploy_control_cutoff_contract.py
state/STATUS_NOW.md
state/roadmap/current-platform-roadmap.md
state/cycle/W0-triage-output.md
state/cycle/W1-resource-hardening-output.md
state/cycle/W2-legacy-inventory-output.md

Relevant context

Current roadmap: state/roadmap/current-platform-roadmap.md
W0 output: state/cycle/W0-triage-output.md
LD0/LD1 plan: state/cutover/rs2000-live-data-config-migration.md
ADR-0020/0021/0022 sequencing constraints

Runtime evidence

Read-only RS2000 checks before this PR:

release root: /opt/pdurlej-platform/current -> releases/181269f5a4a816aae3be430adcccb49b89d42e1e
home-platform-voice-transcription-1 running healthy, no Docker CPU/memory limit, about 3.256GiB sample memory
home-platform-karakeep-chrome-1 running, no Docker CPU/memory limit, about 90MiB sample memory
voice-transcription container metadata still pointed at legacy compose config files
zero unhealthy containers in read-only spot check

Known constraints

No production mutation was performed in this PR.
W1 is not marked formally closed until merge + deploy/apply + smokes are green.
W2 is not destructive cleanup; it is inventory/plan closure only.
Broad module upgrades remain blocked by DR and metadata gates.

Explicit out-of-scope

Deleting or pruning /opt/vps-home-platform-infra.
Running production apply from this PR.
Moving remaining live data/config batches.
DR drill execution.
Secrets/access hardening beyond documenting the sequence.

Requested decision

Merge after checks. Then run trusted-main deploy/apply and smoke voice-transcription plus karakeep before recording W1 as closed and W2 as formally closed.

Merge blockers

YAML/schema/test failure.
Compose config failure with runtime env files.
Reviewer finds that the imported voice-transcription compose contract diverges from live runtime.

Spec sources read

state/roadmap/current-platform-roadmap.md — active durable roadmap and stale W-map.
state/STATUS_NOW.md — operator-facing current state.
state/cycle/W0-triage-output.md — formal W0 evidence.
state/cutover/rs2000-live-data-config-migration.md — LD0/LD1/W2 evidence.
compose/apps/compose.yaml and compose/base/compose.yaml — W1 resource targets.
modules/voice-transcription/module.yaml and runbook — W1 target contract.
modules/karakeep/runbook.md — Chrome sidecar contract.
tests/test_deploy_control_cutoff_contract.py — stale LD1 mount expectation found during test run.

Test plan

python3 -m pytest tests/test_wave_resource_contract.py tests/test_l4_verify.py::test_yaml_syntax_valid -q → 105 passed
bash tests/validate-schema.sh voice-transcription && bash tests/validate-schema.sh karakeep → PASS/PASS
python3 -m pytest tests/test_wave_resource_contract.py tests/test_kan_runtime_contract.py tests/test_deploy_control_cutoff_contract.py control-plane/platformctl/tests/test_forgejo_ci_scripts_contract.py -q → 44 passed
git diff --check → clean
bash tests/validate-schema.sh --all → all module schemas pass
RS2000 read-only compose config with copied compose files and runtime env files → exit 0; existing mirotalk-admin unset-variable warnings only

Post-merge operator action

Trigger trusted-main deploy/apply for voice-transcription.
Smoke tests/smoke.sh voice-transcription.
Trigger/smoke karakeep so the karakeep-chrome sidecar limit is applied.
Confirm zero unhealthy containers and no runner pickup regression.

Canary status: missing — rely on required Forgejo checks before merge ## Canary Context Pack ### Product story Operator wants the post-cutoff waves to stop drifting between old F/F2/F3 plans, Claude feedback, and current chat shorthand. W0 should be formally closed, W1 should finish real RS2000 resource hardening, and W2 should be ready to close from LD0/LD1 evidence without pretending legacy deletion is safe. ### What changed - Canonicalized the W0-W9 wave map in `state/roadmap/current-platform-roadmap.md` and reconciled Claude feedback. - Marked W0 closed in `state/cycle/W0-triage-output.md`. - Added W1/W2 cycle artifacts with explicit closure gates. - Updated `STATUS_NOW.md` to point future forks at the durable wave map. - Added canonical compose resource limits for `karakeep-chrome`. - Imported live `voice-transcription` into canonical compose with the existing tailnet API, volumes, healthcheck, and resource limits. - Added tests for the W1 resource contract and updated the deploy-control test to match LD1 runtime-root mounts. ### Why it changed Read-only evidence showed W1 was not actually closable: `karakeep-chrome` had no CPU/memory limit and live `voice-transcription` still carried legacy/orphan compose metadata. Closing the wave as docs-only would have hidden real drift from future agents. ### Files touched - `compose/apps/compose.yaml` - `compose/base/compose.yaml` - `modules/voice-transcription/module.yaml` - `modules/voice-transcription/runbook.md` - `modules/karakeep/runbook.md` - `tests/test_wave_resource_contract.py` - `tests/test_deploy_control_cutoff_contract.py` - `state/STATUS_NOW.md` - `state/roadmap/current-platform-roadmap.md` - `state/cycle/W0-triage-output.md` - `state/cycle/W1-resource-hardening-output.md` - `state/cycle/W2-legacy-inventory-output.md` ### Relevant context - Current roadmap: `state/roadmap/current-platform-roadmap.md` - W0 output: `state/cycle/W0-triage-output.md` - LD0/LD1 plan: `state/cutover/rs2000-live-data-config-migration.md` - ADR-0020/0021/0022 sequencing constraints ### Runtime evidence Read-only RS2000 checks before this PR: - release root: `/opt/pdurlej-platform/current -> releases/181269f5a4a816aae3be430adcccb49b89d42e1e` - `home-platform-voice-transcription-1` running healthy, no Docker CPU/memory limit, about `3.256GiB` sample memory - `home-platform-karakeep-chrome-1` running, no Docker CPU/memory limit, about `90MiB` sample memory - voice-transcription container metadata still pointed at legacy compose config files - zero unhealthy containers in read-only spot check ### Known constraints - No production mutation was performed in this PR. - W1 is not marked formally closed until merge + deploy/apply + smokes are green. - W2 is not destructive cleanup; it is inventory/plan closure only. - Broad module upgrades remain blocked by DR and metadata gates. ### Explicit out-of-scope - Deleting or pruning `/opt/vps-home-platform-infra`. - Running production apply from this PR. - Moving remaining live data/config batches. - DR drill execution. - Secrets/access hardening beyond documenting the sequence. ### Requested decision Merge after checks. Then run trusted-main deploy/apply and smoke `voice-transcription` plus `karakeep` before recording W1 as closed and W2 as formally closed. ### Merge blockers - YAML/schema/test failure. - Compose config failure with runtime env files. - Reviewer finds that the imported `voice-transcription` compose contract diverges from live runtime. ## Spec sources read - `state/roadmap/current-platform-roadmap.md` — active durable roadmap and stale W-map. - `state/STATUS_NOW.md` — operator-facing current state. - `state/cycle/W0-triage-output.md` — formal W0 evidence. - `state/cutover/rs2000-live-data-config-migration.md` — LD0/LD1/W2 evidence. - `compose/apps/compose.yaml` and `compose/base/compose.yaml` — W1 resource targets. - `modules/voice-transcription/module.yaml` and runbook — W1 target contract. - `modules/karakeep/runbook.md` — Chrome sidecar contract. - `tests/test_deploy_control_cutoff_contract.py` — stale LD1 mount expectation found during test run. ## Test plan - `python3 -m pytest tests/test_wave_resource_contract.py tests/test_l4_verify.py::test_yaml_syntax_valid -q` → 105 passed - `bash tests/validate-schema.sh voice-transcription && bash tests/validate-schema.sh karakeep` → PASS/PASS - `python3 -m pytest tests/test_wave_resource_contract.py tests/test_kan_runtime_contract.py tests/test_deploy_control_cutoff_contract.py control-plane/platformctl/tests/test_forgejo_ci_scripts_contract.py -q` → 44 passed - `git diff --check` → clean - `bash tests/validate-schema.sh --all` → all module schemas pass - RS2000 read-only compose config with copied compose files and runtime env files → exit 0; existing mirotalk-admin unset-variable warnings only ## Post-merge operator action 1. Trigger trusted-main deploy/apply for `voice-transcription`. 2. Smoke `tests/smoke.sh voice-transcription`. 3. Trigger/smoke `karakeep` so the `karakeep-chrome` sidecar limit is applied. 4. Confirm zero unhealthy containers and no runner pickup regression.

codex added 1 commit

2026-05-24 14:26:20 +02:00

fix(rs2000): prepare W1 resource closeout

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

platformctl plan / auto-apply scope (pull_request) Successful in 20s

Details

python-ci / Python 3.11 (pull_request) Successful in 41s