fix(cutover): remount np meerkat data import #588

Merged

pdurlej merged 1 commit from codex/m01-remount-np-meerkat-data into main

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

codex commented

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

Collaborator

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

Summary

M01 stateful remount batch for np-meerkat-backend.

This PR moves Meerkat backend data defaults to prepared legacy-import paths:

/opt/pdurlej-platform/runtime/legacy-import/data/np/meerkat-data
/opt/pdurlej-platform/runtime/legacy-import/data/np/meerkat-photos

The old legacy paths remain available as explicit rollback env vars 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. np-meerkat-backend is a small active stateful service with low-volume data and an existing healthcheck.

What changed

compose/apps/compose.yaml: Meerkat backend data/photo mounts now default to copied legacy-import paths.
modules/np-meerkat-backend/runbook.md: documents data sources and rollback env vars.

Why it changed

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

Files touched

compose/apps/compose.yaml
modules/np-meerkat-backend/runbook.md

Relevant context

M01 RS2000 closeout critical path
Prior remount batches applied cleanly: ntfy, dashboard, searxng, coredns, matrix-well-known, shelfmark
This is stateful, so it is split as its own PR

Runtime evidence

Prep copy already run on RS2000 before this PR:

scripts/cutover/prepare-legacy-import.sh --dry-run --path data/np/meerkat-data
scripts/cutover/prepare-legacy-import.sh --yes --path data/np/meerkat-data
target_size 236K /opt/pdurlej-platform/runtime/legacy-import/data/np/meerkat-data

scripts/cutover/prepare-legacy-import.sh --dry-run --path data/np/meerkat-photos
scripts/cutover/prepare-legacy-import.sh --yes --path data/np/meerkat-photos
target_size 4.0K /opt/pdurlej-platform/runtime/legacy-import/data/np/meerkat-photos

No service restart was performed for this PR.

Known constraints

This does not delete or quarantine legacy paths.
This does not change Meerkat data contents intentionally.
This does not recreate the container before merge.

Explicit out-of-scope

destructive cleanup
quarantine/tombstone
other NP apps
Matrix/Synapse data
Traefik ACME/certs

Requested decision

Approve this as a small stateful remount if checks are green or pending-only Actions are handled by admin force-merge under operator authorization.

Merge blockers

copied Meerkat targets missing on RS2000
compose syntax failure
local validation failure
reviewer identifies a rollback risk not covered by rollback env vars

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/np-meerkat-backend/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 stateful remount batch for `np-meerkat-backend`. This PR moves Meerkat backend data defaults to prepared `legacy-import` paths: - `/opt/pdurlej-platform/runtime/legacy-import/data/np/meerkat-data` - `/opt/pdurlej-platform/runtime/legacy-import/data/np/meerkat-photos` The old legacy paths remain available as explicit rollback env vars 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. `np-meerkat-backend` is a small active stateful service with low-volume data and an existing healthcheck. ### What changed - `compose/apps/compose.yaml`: Meerkat backend data/photo mounts now default to copied `legacy-import` paths. - `modules/np-meerkat-backend/runbook.md`: documents data sources and rollback env vars. ### Why it changed The legacy root must stop being the default runtime source. This keeps old paths as rollback material while making the canonical release root independent of the legacy project tree. ### Files touched - `compose/apps/compose.yaml` - `modules/np-meerkat-backend/runbook.md` ### Relevant context - M01 RS2000 closeout critical path - Prior remount batches applied cleanly: `ntfy`, `dashboard`, `searxng`, `coredns`, `matrix-well-known`, `shelfmark` - This is stateful, so it is split as its own PR ### Runtime evidence Prep copy already run on RS2000 before this PR: ```text scripts/cutover/prepare-legacy-import.sh --dry-run --path data/np/meerkat-data scripts/cutover/prepare-legacy-import.sh --yes --path data/np/meerkat-data target_size 236K /opt/pdurlej-platform/runtime/legacy-import/data/np/meerkat-data scripts/cutover/prepare-legacy-import.sh --dry-run --path data/np/meerkat-photos scripts/cutover/prepare-legacy-import.sh --yes --path data/np/meerkat-photos target_size 4.0K /opt/pdurlej-platform/runtime/legacy-import/data/np/meerkat-photos ``` No service restart was performed for this PR. ### Known constraints - This does not delete or quarantine legacy paths. - This does not change Meerkat data contents intentionally. - This does not recreate the container before merge. ### Explicit out-of-scope - destructive cleanup - quarantine/tombstone - other NP apps - Matrix/Synapse data - Traefik ACME/certs ### Requested decision Approve this as a small stateful remount if checks are green or pending-only Actions are handled by admin force-merge under operator authorization. ### Merge blockers - copied Meerkat targets missing on RS2000 - compose syntax failure - local validation failure - reviewer identifies a rollback risk not covered by rollback env vars ## 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/np-meerkat-backend/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:29:26 +02:00

codex added the

risk/runtime

cutover-gate

phase/03

class/security-sensitive

labels