feat: schedule Phase 5 checks; start T06 path decoupling

Add phase5 daily/closeout ActivityDefinitions, document schedules in Phase 5
evidence, and migrate daily triage sinks to custodian:// runtime URIs.

workplans/CUST-WP-0054-workstation-independence-and-fleet-realignment.md

@@ -236,13 +236,15 @@ kickoff baseline green — `docs/state-hub-railiance01-cutover-phase5-2026-07-06
 Post-cutover daily triage verified (manual 2026-07-06T17:50Z, event `a99e644e`).
 Forgejo CI image promoted (`main-375961c`, Helm rev 7). Day-1 check (2026-07-06T22:35Z):
 640/4002/14, pod 0 restarts, 6/6 sweeps exit_code=0 proc=11 missing=0,
-`state-hub-primary` LIVE. Remaining: 72h window + operator coulombcore teardown sign-off.
+`state-hub-primary` LIVE. Phase 5 checks scheduled in activity-core:
+`phase5-stabilization-daily` (09:00 Europe/Berlin) and one-shot closeout
+`2026-07-09T17:35Z`. Remaining: 72h window + operator coulombcore teardown sign-off.
 
 ## Task: Working-memory and sink path decoupling
 
 ```task
 id: CUST-WP-0054-T06
-status: todo
+status: progress
 priority: medium
 state_hub_task_id: "f2c5dd4b-9af4-4e8c-8619-6814e7d1666e"
 ```
@@ -252,6 +254,13 @@ working-memory sink and any prompt/context paths become repo-relative or
 PVC-native with a defined sync-to-repo step (commit via the sweep). Done when
 no ActivityDefinition or sink references a workstation-specific absolute path.
 
+**Started (2026-07-06):** `custodian://` and `activity-core://` runtime path
+URIs in activity-core (`runtime_paths.py`); daily triage definition + Railiance
+projection decoupled from `/home/worsch/...`; working-memory mount moved to
+`/var/custodian/memory/working`; prompt projected via `actcore-custodian-runtime`
+ConfigMap. Remaining: sweep sync-to-repo for working-memory notes, audit remaining
+ActivityDefinitions/sinks.
+
 ## Task: Dev-environment beachhead (files-first)
 
 ```task