fix(cutover): remount matrix well-known import #586

Merged

pdurlej merged 1 commit from codex/m01-remount-matrix-well-known into main

2026-05-29 00:21:29 +02:00

codex commented

2026-05-29 00:16:34 +02:00

Collaborator

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

Summary

M01 static-data remount batch for matrix-well-known.

This PR moves the .well-known static directory default to the prepared legacy-import path:

/opt/pdurlej-platform/runtime/legacy-import/data/matrix/well-known

The old legacy path remains available as an explicit rollback env var for one rollback cycle.

Canary Context Pack

Product story

M01 needs active services to stop depending on /opt/vps-home-platform-infra before quarantine/destructive cleanup. matrix-well-known is a small static-data move with a healthcheck and clear rollback path.

What changed

compose/apps/compose.yaml: matrix-well-known mount now defaults to the copied legacy-import directory.
modules/matrix-well-known/runbook.md: documents the new source and rollback env var.

Why it changed

The legacy root must stop being the default runtime source. This keeps the old path as rollback material while making the canonical release root independent of the legacy project tree.

Files touched

compose/apps/compose.yaml
modules/matrix-well-known/runbook.md

Relevant context

M01 RS2000 closeout critical path
Prior remount batches applied cleanly: ntfy, dashboard, searxng, coredns
This PR intentionally does not touch synapse data or the orphan element-web runtime

Runtime evidence

Prep copy already run on RS2000 before this PR:

scripts/cutover/prepare-legacy-import.sh --dry-run --path data/matrix/well-known
scripts/cutover/prepare-legacy-import.sh --yes --path data/matrix/well-known
target_size 20K /opt/pdurlej-platform/runtime/legacy-import/data/matrix/well-known

No service restart was performed for this PR.

Known constraints

This does not delete or quarantine legacy paths.
This does not change .well-known contents.
This does not recreate the container before merge.

Explicit out-of-scope

Synapse data migration
Element-web orphan runtime cleanup
service restart before merge
destructive cleanup
quarantine/tombstone

Requested decision

Approve this as the next static-data remount if checks are green.

Merge blockers

copied .well-known target missing on RS2000
compose syntax failure
reviewer finds a public-routing rollback risk not covered by rollback env var

Validation

git diff --check: passed
PYTHONPATH=control-plane uv run --project control-plane python -m platformctl.cli validate all --json: passed, exit 0

Spec sources read

compose/apps/compose.yaml — mount declaration
modules/matrix-well-known/runbook.md — operator rollback/runbook update

Non-goals

No DB, no service, no webhooks, no issue/comment mutation, no destructive cleanup.

Canary status: missing — fire canary 3+3 manually before merge ## Summary M01 static-data remount batch for `matrix-well-known`. This PR moves the `.well-known` static directory default to the prepared `legacy-import` path: `/opt/pdurlej-platform/runtime/legacy-import/data/matrix/well-known` The old legacy path remains available as an explicit rollback env var for one rollback cycle. ## Canary Context Pack ### Product story M01 needs active services to stop depending on `/opt/vps-home-platform-infra` before quarantine/destructive cleanup. `matrix-well-known` is a small static-data move with a healthcheck and clear rollback path. ### What changed - `compose/apps/compose.yaml`: `matrix-well-known` mount now defaults to the copied `legacy-import` directory. - `modules/matrix-well-known/runbook.md`: documents the new source and rollback env var. ### Why it changed The legacy root must stop being the default runtime source. This keeps the old path as rollback material while making the canonical release root independent of the legacy project tree. ### Files touched - `compose/apps/compose.yaml` - `modules/matrix-well-known/runbook.md` ### Relevant context - M01 RS2000 closeout critical path - Prior remount batches applied cleanly: `ntfy`, `dashboard`, `searxng`, `coredns` - This PR intentionally does not touch `synapse` data or the orphan `element-web` runtime ### Runtime evidence Prep copy already run on RS2000 before this PR: ```text scripts/cutover/prepare-legacy-import.sh --dry-run --path data/matrix/well-known scripts/cutover/prepare-legacy-import.sh --yes --path data/matrix/well-known target_size 20K /opt/pdurlej-platform/runtime/legacy-import/data/matrix/well-known ``` No service restart was performed for this PR. ### Known constraints - This does not delete or quarantine legacy paths. - This does not change `.well-known` contents. - This does not recreate the container before merge. ### Explicit out-of-scope - Synapse data migration - Element-web orphan runtime cleanup - service restart before merge - destructive cleanup - quarantine/tombstone ### Requested decision Approve this as the next static-data remount if checks are green. ### Merge blockers - copied `.well-known` target missing on RS2000 - compose syntax failure - reviewer finds a public-routing rollback risk not covered by rollback env var ## Validation - `git diff --check`: passed - `PYTHONPATH=control-plane uv run --project control-plane python -m platformctl.cli validate all --json`: passed, exit 0 ## Spec sources read - `compose/apps/compose.yaml` — mount declaration - `modules/matrix-well-known/runbook.md` — operator rollback/runbook update ## Non-goals No DB, no service, no webhooks, no issue/comment mutation, no destructive cleanup.

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

2026-05-29 00:16:34 +02:00

codex added the

risk/runtime

cutover-gate

phase/03

class/security-sensitive

labels