docs(cutover): plan live data config migration #412

Merged

pdurlej merged 1 commit from codex/cutover/live-data-config-migration-plan into main

2026-05-24 10:54:57 +02:00

codex commented

2026-05-24 10:05:12 +02:00

Collaborator

Canary status: missing — fire canary via python -m platformctl.tools.run_review before merge

Summary

Adds the missing Milestone 01 execution plan for moving live data/config/env/product runtime material off /opt/vps-home-platform-infra before any destructive legacy cleanup. This is plan-only: no server-side data move, compose change, restart, deletion, or credential change.

Changes

Adds state/cutover/rs2000-live-data-config-migration.md with LD0-LD5 waves, target layout, per-path migration record, rollback, privacy rules, and stop conditions.
Links the new live-migration plan from the post-soak legacy cleanup plan.
Updates the active roadmap so Milestone 01 explicitly moves live dependencies before ADR-0020 cleanup.
Updates STATUS_NOW.md with the Milestone 01 planning state and a read-only RS2000 spot check.

Verification

git diff --check
Read-only RS2000 spot check: release-root symlink, zero unhealthy containers, deploy runner active, watchdog timer active, deploy-control healthy.
No production mutation performed.

Test plan

Operator review of migration sequence before any runtime move.
Required Forgejo checks green.
After merge: start LD0 read-only inventory for issue #387.

Canary Context Pack

Product story

The operator wants to close the RS2000 cutoff cleanly without accidentally treating /opt/vps-home-platform-infra as disposable while it still contains live data/config/env/product runtime material.

What changed

A dedicated live-dependency migration plan now sits between cutoff acceptance and destructive legacy cleanup.

Why it changed

ADR-0020 already says live data/config must move first. The repo needed a concrete execution contract for inventory, target layout, remount PRs, smoke evidence, rollback, and 48h observation.

Files touched

state/cutover/rs2000-live-data-config-migration.md
state/cutover/rs2000-post-soak-legacy-cleanup.md
state/roadmap/current-platform-roadmap.md
state/STATUS_NOW.md

Relevant context

ADR-0020: post-soak cleanup and modularization boundary.
ADR-0021: bounded contexts for platform monorepo.
ADR-0022: module source and release boundaries.
Issue #387: post-soak legacy cleanup flight.

Runtime evidence

Read-only check on 2026-05-24 10:02 CEST:

/opt/pdurlej-platform/current -> releases/5982e2eca04f3dfd3de99072ce4aebb5035dbf8f
Unhealthy containers: 0
forgejo-deploy-runner.service: active
forgejo-deploy-runner-watchdog.timer: active
home-platform-deploy-control-1: running and healthy

Known constraints

The plan must not print env values, private user data, emails, Signal/Matrix content, Iskra memory, or secrets. Actual runtime moves remain operator-gated and must use PR/apply/smoke evidence.

Explicit out-of-scope

No deletion, no pruning, no server-side copy, no compose remount, no production restart, no credential rotation, no broad module upgrades.

Requested decision

Approve the plan as the next Milestone 01 source of truth before LD0 inventory and later runtime migration PRs.

Merge blockers

Any reviewer finds that the plan permits destructive cleanup before live bind mounts are gone.
Any reviewer finds a privacy/secret evidence rule gap.
Required Forgejo checks fail.

Spec sources read

decisions/0020-post-soak-legacy-cleanup-and-platform-modularization.md — cleanup classes and live-data-first rule.
state/cutover/rs2000-post-soak-legacy-cleanup.md — existing cleanup plan to link and refine.
state/cutover/rs2000-control-plane-cutoff.md — cutoff semantics and known legacy mount families.
state/roadmap/current-platform-roadmap.md — milestone and W-wave mapping.
state/STATUS_NOW.md — current operator-facing status.
decisions/0021-ddd-bounded-contexts-for-platform-monorepo.md — repo boundary context.
decisions/0022-module-source-and-release-boundaries.md — source/artifact boundary context.
docs/forgejo-agent-operations.md — Forgejo identity/write contract.

Refs #387.

Canary status: missing — fire canary via `python -m platformctl.tools.run_review` before merge ## Summary Adds the missing Milestone 01 execution plan for moving live data/config/env/product runtime material off `/opt/vps-home-platform-infra` before any destructive legacy cleanup. This is plan-only: no server-side data move, compose change, restart, deletion, or credential change. ## Changes - Adds `state/cutover/rs2000-live-data-config-migration.md` with LD0-LD5 waves, target layout, per-path migration record, rollback, privacy rules, and stop conditions. - Links the new live-migration plan from the post-soak legacy cleanup plan. - Updates the active roadmap so Milestone 01 explicitly moves live dependencies before ADR-0020 cleanup. - Updates `STATUS_NOW.md` with the Milestone 01 planning state and a read-only RS2000 spot check. ## Verification - [x] `git diff --check` - [x] Read-only RS2000 spot check: release-root symlink, zero unhealthy containers, deploy runner active, watchdog timer active, deploy-control healthy. - [x] No production mutation performed. ## Test plan - [ ] Operator review of migration sequence before any runtime move. - [ ] Required Forgejo checks green. - [ ] After merge: start LD0 read-only inventory for issue #387. ## Canary Context Pack ### Product story The operator wants to close the RS2000 cutoff cleanly without accidentally treating `/opt/vps-home-platform-infra` as disposable while it still contains live data/config/env/product runtime material. ### What changed A dedicated live-dependency migration plan now sits between cutoff acceptance and destructive legacy cleanup. ### Why it changed ADR-0020 already says live data/config must move first. The repo needed a concrete execution contract for inventory, target layout, remount PRs, smoke evidence, rollback, and 48h observation. ### Files touched - `state/cutover/rs2000-live-data-config-migration.md` - `state/cutover/rs2000-post-soak-legacy-cleanup.md` - `state/roadmap/current-platform-roadmap.md` - `state/STATUS_NOW.md` ### Relevant context - ADR-0020: post-soak cleanup and modularization boundary. - ADR-0021: bounded contexts for platform monorepo. - ADR-0022: module source and release boundaries. - Issue #387: post-soak legacy cleanup flight. ### Runtime evidence Read-only check on 2026-05-24 10:02 CEST: - `/opt/pdurlej-platform/current -> releases/5982e2eca04f3dfd3de99072ce4aebb5035dbf8f` - Unhealthy containers: `0` - `forgejo-deploy-runner.service`: active - `forgejo-deploy-runner-watchdog.timer`: active - `home-platform-deploy-control-1`: running and healthy ### Known constraints The plan must not print env values, private user data, emails, Signal/Matrix content, Iskra memory, or secrets. Actual runtime moves remain operator-gated and must use PR/apply/smoke evidence. ### Explicit out-of-scope No deletion, no pruning, no server-side copy, no compose remount, no production restart, no credential rotation, no broad module upgrades. ### Requested decision Approve the plan as the next Milestone 01 source of truth before LD0 inventory and later runtime migration PRs. ### Merge blockers - Any reviewer finds that the plan permits destructive cleanup before live bind mounts are gone. - Any reviewer finds a privacy/secret evidence rule gap. - Required Forgejo checks fail. ## Spec sources read - `decisions/0020-post-soak-legacy-cleanup-and-platform-modularization.md` — cleanup classes and live-data-first rule. - `state/cutover/rs2000-post-soak-legacy-cleanup.md` — existing cleanup plan to link and refine. - `state/cutover/rs2000-control-plane-cutoff.md` — cutoff semantics and known legacy mount families. - `state/roadmap/current-platform-roadmap.md` — milestone and W-wave mapping. - `state/STATUS_NOW.md` — current operator-facing status. - `decisions/0021-ddd-bounded-contexts-for-platform-monorepo.md` — repo boundary context. - `decisions/0022-module-source-and-release-boundaries.md` — source/artifact boundary context. - `docs/forgejo-agent-operations.md` — Forgejo identity/write contract. Refs #387.

codex added 1 commit

2026-05-24 10:05:12 +02:00

docs(cutover): plan live data config migration

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 22s

Details

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