Repair production automation truth and schedule cleanup

workplans/ADHOC-2026-08-20.md

@@ -0,0 +1,43 @@
+---
+id: ADHOC-2026-08-20
+type: workplan
+title: "Ad hoc — activity-core opportunistic fixes 2026-08-20"
+domain: infotech
+repo: activity-core
+status: finished
+owner: codex
+topic_slug: activity-core
+created: "2026-08-20"
+updated: "2026-08-20"
+---
+
+# ADHOC-2026-08-20 — activity-core opportunistic fixes
+
+## Reconcile the daily TODO review sink warning
+
+```task
+id: ADHOC-2026-08-20-T01
+status: done
+priority: low
+```
+
+The projected `daily-todo-md-stale-review` definition still said that
+`IssueSink` defaulted to `rest` and that re-enabling the definition would
+unconditionally recreate Forgejo issues. That warning described the state before
+ACTIVITY-WP-0022 and contradicted the current code, deployment configuration,
+and `weekly-sbom-staleness` definition.
+
+Correct the warning to state that `ISSUE_SINK_TYPE=state-hub` is the safe fleet
+default, `rest` is explicit opt-in, and State Hub progress is visibility rather
+than claim authority. Keep the schedule disabled so a documentation correction
+does not silently change production cadence, and document the operational checks
+needed before it is deliberately re-enabled. Add a projection test so the stale
+`default rest` claim cannot recur unnoticed.
+
+Verification:
+
+- Focused regression and IssueSink tests: `7 passed`.
+- Full suite: `342 passed, 1 skipped, 4 failed`. The four failures are unrelated
+  existing inconsistencies: rules boundary allowlisting, the State Hub image pin
+  assertion, a schedule-health response double missing `status_code`, and the
+  sync-service expectation omitting the returned `errors` count.