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.

activity-definitions/daily-statehub-wsjf-triage.md

@@ -17,7 +17,7 @@ context_sources:
   - type: static
     bind_to: context.prompt_path
     config:
-      value: /home/worsch/the-custodian/runtime/prompts/daily_statehub_wsgi_triage.md
+      value: custodian://runtime/prompts/daily_statehub_wsgi_triage.md
   - type: state-hub
     query: daily_triage_digest
     params:
@@ -50,7 +50,7 @@ Current active runner:
 
 - activity-core Temporal schedule from this ActivityDefinition
 - Prompt source:
-  `/home/worsch/the-custodian/runtime/prompts/daily_statehub_wsgi_triage.md`
+  `custodian://runtime/prompts/daily_statehub_wsgi_triage.md`
 
 Railiance projection note:
 
@@ -124,7 +124,7 @@ prompt: |
   {context.daily_triage_digest}
 
   Return only JSON matching
-  `/home/worsch/the-custodian/schemas/daily-triage-report.json`. Do not wrap
+  `activity-core://schemas/daily-triage-report.json`. Do not wrap
   the JSON in Markdown fences or add prose before or after it:
   {
     "summary": "short operator-facing summary",
@@ -146,11 +146,11 @@ prompt: |
       }
     ]
   }
-output_schema: /home/worsch/the-custodian/schemas/daily-triage-report.json
+output_schema: activity-core://schemas/daily-triage-report.json
 review_required: false
 report_sinks:
   - type: working-memory
-    path: /home/worsch/the-custodian/memory/working
+    path: custodian://memory/working
     timezone: Europe/Berlin
     filename_template: "daily-triage-{date}-{run_id_short}.md"
   - type: state-hub-progress
@@ -165,7 +165,7 @@ report_sinks:
 The run should produce:
 
 - a dated working-memory note under
-  `/home/worsch/the-custodian/memory/working/`
+  `custodian://memory/working/`
 - a State Hub progress event with `event_type: daily_triage`
 - no direct workplan/canon edits
 - no task status changes unless a later human request explicitly asks for an

activity-definitions/phase5-stabilization-closeout.md

@@ -0,0 +1,55 @@
+---
+id: "e7d2b5a8-4c1f-4e9a-b6d3-8f2a1c4e6b09"
+name: "Phase 5 Stabilization Closeout Check"
+type: activity-definition
+version: "1.0"
+enabled: true
+owner: custodian
+governance: custodian
+status: active
+created: "2026-07-06"
+trigger:
+  type: scheduled
+  at: "2026-07-09T17:35:00+00:00"
+  timezone: UTC
+context_sources:
+  - type: state-hub
+    query: phase5_stabilization_check
+    required: true
+    params:
+      source: activity-core
+      closeout: true
+      window_start: "2026-07-06T17:35:00+00:00"
+      window_end: "2026-07-09T17:35:00+00:00"
+      baseline:
+        workstreams: 640
+        tasks: 4002
+        topics: 14
+      sweep_limit: 6
+      triage_max_age_hours: 36
+      evidence_sinks:
+        - type: state-hub-progress
+          event_type: phase5_stabilization_closeout
+          author: activity-core
+          workstream_id: 8a828444-dd49-4d7b-a2d1-9952b5bc929d
+          task_id: e91db8d0-973d-4a31-b3c2-ca37fd002ec7
+    bind_to: context.phase5_stabilization_check
+---
+
+# ActivityDefinition: Phase 5 Stabilization Closeout Check
+
+## Purpose
+
+One-shot closeout gate at the end of the `CUST-WP-0054-T05` stabilization
+window. Fails visibly when hub-visible gates are not green. When gates pass,
+records `operator_signoff_needed: true` for coulombcore teardown approval.
+
+## Trigger
+
+Scheduled once at **2026-07-09T17:35:00Z** (72h after window open).
+
+## Output Contract
+
+- one State Hub progress event with `event_type: phase5_stabilization_closeout`
+- fails the ActivityRun when any gate is red at closeout time
+- no LLM call and no direct workplan edits

activity-definitions/phase5-stabilization-daily.md

@@ -0,0 +1,58 @@
+---
+id: "f3a8c2e1-9b4d-4a6f-8e2d-1c5b7a9e3f04"
+name: "Phase 5 Stabilization Daily Check"
+type: activity-definition
+version: "1.0"
+enabled: true
+owner: custodian
+governance: custodian
+status: active
+created: "2026-07-06"
+trigger:
+  type: cron
+  cron_expression: "0 9 * * *"
+  timezone: Europe/Berlin
+  misfire_policy: skip
+context_sources:
+  - type: state-hub
+    query: phase5_stabilization_check
+    required: true
+    params:
+      source: activity-core
+      closeout: false
+      window_start: "2026-07-06T17:35:00+00:00"
+      window_end: "2026-07-09T17:35:00+00:00"
+      baseline:
+        workstreams: 640
+        tasks: 4002
+        topics: 14
+      sweep_limit: 6
+      triage_max_age_hours: 36
+      evidence_sinks:
+        - type: state-hub-progress
+          event_type: phase5_stabilization_check
+          author: activity-core
+          workstream_id: 8a828444-dd49-4d7b-a2d1-9952b5bc929d
+          task_id: e91db8d0-973d-4a31-b3c2-ca37fd002ec7
+    bind_to: context.phase5_stabilization_check
+---
+
+# ActivityDefinition: Phase 5 Stabilization Daily Check
+
+## Purpose
+
+Scheduled hub-visible health gate for `CUST-WP-0054-T05` during the 72h
+stabilization window (2026-07-06 → 2026-07-09). Complements the manual
+`tools/phase5-stabilization-check.sh` script with fleet-side evidence in State
+Hub progress.
+
+## Trigger
+
+Daily at 09:00 Europe/Berlin while the stabilization window is open. Runs
+outside the window are recorded as `skipped` with `reason=outside_stabilization_window`.
+
+## Output Contract
+
+- one State Hub progress event with `event_type: phase5_stabilization_check`
+- compact pass/fail detail for health, totals, sweeps, and daily triage freshness
+- no LLM call and no direct workplan edits