Sync embedded daily-todo-md-stale-review ConfigMap: paused (enabled: false)

Mirrors the-custodian's ADR-001 source-of-truth change (2026-07-20): this
activity was the fleet's only consumer of the task_template rule action,
which unconditionally routes through IssueSink -> issue-core -> Forgejo
-- the sole source of 5 stale-review issues that had to be manually
reviewed and closed. Embedded copy in this ConfigMap had drifted from
the source file (still enabled: true) since there's no automated sync
between the-custodian/activity-definitions/ and this k8s manifest; the
Deploy runbook in k8s/railiance/README.md re-applies the ConfigMap as
committed here, so this had to be updated before re-running actcore-sync.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

k8s/railiance/20-runtime.yaml

@@ -208,12 +208,13 @@ data:
     id: "b8e4f1a2-3c6d-4e9f-a1b2-7d8e9f0a1b2c"
     name: "Daily TODO.md Stale Review"
     type: activity-definition
-    version: "1.0"
-    enabled: true
+    version: "1.1"
+    enabled: false
     owner: custodian
     governance: custodian
-    status: active
+    status: paused
     created: "2026-07-08"
+    updated: "2026-07-20"
     trigger:
       type: cron
       cron_expression: "30 8 * * *"
@@ -232,10 +233,41 @@ data:
         author: activity-core
     ---
 
-    # ActivityDefinition: Daily TODO.md Stale Review
+    # Daily TODO.md Stale Review
 
-    Kubernetes projection of the Custodian-owned definition in
-    `/home/worsch/the-custodian/activity-definitions/daily-todo-md-stale-review.md`.
+    > **Paused 2026-07-20.** The matched rule below always produces a
+    > `TaskSpec` (`rules/actions.py::_task_spec_for_rule`), which
+    > `RunActivityWorkflow` unconditionally routes through `emit_tasks` →
+    > the deployment-wide `IssueSink` (`ISSUE_SINK_TYPE`, default `rest` →
+    > issue-core → Forgejo). There is no per-activity sink override in the
+    > current schema, and this activity is the fleet's *only* consumer of
+    > `task_template` — it was the sole source of 5 stale-review Forgejo
+    > issues (`the-custodian` #1–#5, opened 2026-07-08, all reviewed and
+    > closed 2026-07-20). Per current policy, Forgejo issue tracking is not
+    > the fleet coordination mechanism (binky-control housekeeping session,
+    > 2026-07-20) — so this activity is disabled (`enabled: false`) rather
+    > than left to recreate the same sidetrack daily.
+    >
+    > **Re-enable path:** redirect the rule's output onto the work-record
+    > backbone (`work-record-types_v0.1.md`, `kind: intake` — "a stale TODO.md
+    > is exactly a finding/directive") instead of `IssueSink`. This needs
+    > either a new report-sink type in activity-core (file-based intake-item
+    > authoring in the target repo, mirroring `state-hub-progress`) or routing
+    > through the stage-3 promotion tooling seeded in `CUST-WP-0060`'s closure
+    > review (item 6, added 2026-07-20). Do not re-enable with `enabled: true`
+    > alone; that only restores the Forgejo-issue behavior.
+    >
+    > This file change is the ADR-001 source of truth; the live activity-core
+    > DB row picks it up on the next `make sync-activity-definitions` run
+    > (Railiance-deployed, not run from this edit).
+
+    Runs daily at 08:30 Europe/Berlin (after WSJF triage at 07:20). Scans
+    registered workstation repos for `TODO.md` files that have not changed in
+    6+ days and emits a review task per stale repo.
+
+    Policy: TODO.md is a pragmatic interruption buffer only. Stale files should
+    be reviewed — archive done items, delete noise, or promote durable work into
+    a workplan via ADR-001.
 
     ```rule
     id: flag-stale-todo-md
@@ -1277,3 +1309,4 @@ spec:
                 name: actcore-runtime-config
             - secretRef:
                 name: actcore-runtime-secret
+