fix(cutover): move runtime defaults off legacy root #579

Merged

pdurlej merged 1 commit from codex/m01-runtime-defaults-off-legacy into main

2026-05-28 23:28:46 +02:00

codex commented

2026-05-28 23:21:21 +02:00

Collaborator

Canary status: missing - fire canary 3+3 manually before merge

Summary

Moves repo-side M01 runtime defaults off /opt/vps-home-platform-infra without mutating RS2000 runtime state.

This is the first post-audit closeout step after Wave 1: the read-only RS2000 legacy audit reported blocker references in active Compose defaults and in platformctl apply's default remote root. This PR removes those live defaults while preserving safety guard references as review-only audit findings.

What changed

platformctl apply now defaults to /opt/pdurlej-platform/current instead of the old legacy root.
Compose defaults now point env/config/data mounts to /opt/pdurlej-platform/runtime/legacy-import/....
control-plane/platformctl/safety.py remains allowed to mention the legacy root as a sacred-path guardrail, but the audit classifies it as review-only rather than a live blocker.
Tests were updated for the new default root and the audit classification.

Runtime precondition

Before the first real deploy/apply using these defaults, RS2000 must have the conservative copy in place:

/opt/pdurlej-platform/runtime/legacy-import/env
/opt/pdurlej-platform/runtime/legacy-import/config/integrations
/opt/pdurlej-platform/runtime/legacy-import/data/integrations

If runtime env overrides are already set, they may continue to override these defaults. This PR does not copy data, restart containers, or delete old paths.

Safety

No runtime mutation.
No deletion.
No restart.
No secret values printed or committed.
Old /opt/vps-home-platform-infra data/env paths remain protected by safety.py.
Destructive cleanup remains blocked by m01-destructive-cleanup-approved.

Validation

UV_CACHE_DIR=/private/tmp/platform-uv-cache uv run pytest platformctl/tests/test_rs2000_legacy_audit.py platformctl/tests/test_apply_phase3.py platformctl/tests/test_apply_env_file.py => 68 passed
UV_CACHE_DIR=/private/tmp/platform-uv-cache PYTHONPATH=control-plane uv run --project control-plane python -m platformctl.cli cutover rs2000-legacy-audit --json => exit 0; 0 blockers, 0 unknown, 0 commandErrors
UV_CACHE_DIR=/private/tmp/platform-uv-cache PYTHONPATH=control-plane uv run --project control-plane python -m platformctl.cli validate all --json => exit 0
git diff --check => pass
DeepSeek V4 Pro review => OK; noted the runtime precondition above.

Spec sources read

state/cutover/rs2000-live-data-config-migration.md
state/cutover/rs2000-post-soak-legacy-cleanup.md
decisions/0020-post-soak-legacy-cleanup-and-platform-modularization.md
compose/apps/compose.yaml
compose/core/compose.yaml
control-plane/platformctl/apply.py
control-plane/platformctl/cutover/rs2000_legacy_audit.py

Non-goals

No data copy.
No service remount.
No Docker restart.
No runtime smoke claim.
No quarantine/tombstone.
No destructive cleanup.

Canary status: missing - fire canary 3+3 manually before merge ## Summary Moves repo-side M01 runtime defaults off `/opt/vps-home-platform-infra` without mutating RS2000 runtime state. This is the first post-audit closeout step after Wave 1: the read-only RS2000 legacy audit reported blocker references in active Compose defaults and in `platformctl apply`'s default remote root. This PR removes those live defaults while preserving safety guard references as review-only audit findings. ## What changed - `platformctl apply` now defaults to `/opt/pdurlej-platform/current` instead of the old legacy root. - Compose defaults now point env/config/data mounts to `/opt/pdurlej-platform/runtime/legacy-import/...`. - `control-plane/platformctl/safety.py` remains allowed to mention the legacy root as a sacred-path guardrail, but the audit classifies it as review-only rather than a live blocker. - Tests were updated for the new default root and the audit classification. ## Runtime precondition Before the first real deploy/apply using these defaults, RS2000 must have the conservative copy in place: - `/opt/pdurlej-platform/runtime/legacy-import/env` - `/opt/pdurlej-platform/runtime/legacy-import/config/integrations` - `/opt/pdurlej-platform/runtime/legacy-import/data/integrations` If runtime env overrides are already set, they may continue to override these defaults. This PR does not copy data, restart containers, or delete old paths. ## Safety - No runtime mutation. - No deletion. - No restart. - No secret values printed or committed. - Old `/opt/vps-home-platform-infra` data/env paths remain protected by `safety.py`. - Destructive cleanup remains blocked by `m01-destructive-cleanup-approved`. ## Validation - `UV_CACHE_DIR=/private/tmp/platform-uv-cache uv run pytest platformctl/tests/test_rs2000_legacy_audit.py platformctl/tests/test_apply_phase3.py platformctl/tests/test_apply_env_file.py` => 68 passed - `UV_CACHE_DIR=/private/tmp/platform-uv-cache PYTHONPATH=control-plane uv run --project control-plane python -m platformctl.cli cutover rs2000-legacy-audit --json` => exit 0; `0` blockers, `0` unknown, `0` commandErrors - `UV_CACHE_DIR=/private/tmp/platform-uv-cache PYTHONPATH=control-plane uv run --project control-plane python -m platformctl.cli validate all --json` => exit 0 - `git diff --check` => pass - DeepSeek V4 Pro review => OK; noted the runtime precondition above. ## Spec sources read - `state/cutover/rs2000-live-data-config-migration.md` - `state/cutover/rs2000-post-soak-legacy-cleanup.md` - `decisions/0020-post-soak-legacy-cleanup-and-platform-modularization.md` - `compose/apps/compose.yaml` - `compose/core/compose.yaml` - `control-plane/platformctl/apply.py` - `control-plane/platformctl/cutover/rs2000_legacy_audit.py` ## Non-goals - No data copy. - No service remount. - No Docker restart. - No runtime smoke claim. - No quarantine/tombstone. - No destructive cleanup.

codex added this to the 01 - RS2000 closeout and legacy cleanup milestone

2026-05-28 23:21:21 +02:00

codex added the

cutover-gate

phase/03

kind/infra

class/security-sensitive

labels