Record CUST-WP-0045 implementation start

workplans/CUST-WP-0045-activity-core-daily-triage-runner.md

@@ -11,6 +11,7 @@ planning_priority: high
 planning_order: 45
 created: "2026-05-19"
 updated: "2026-05-19"
+state_hub_workstream_id: "d9d9a3ec-f736-4041-beac-bb92c7ad314e"
 ---
 
 # CUST-WP-0045 - Activity-Core Daily Triage Runner Cutover
@@ -105,8 +106,9 @@ Cutover rule: do not enable both runners at the same time. The handoff is:
 
 ```task
 id: CUST-WP-0045-T01
-status: todo
+status: done
 priority: high
+state_hub_task_id: "01f57ed4-0473-42bf-b61c-0491f7ac7e2c"
 ```
 
 Record the 2026-05-19 failed automation evidence in the implementation notes
@@ -126,9 +128,10 @@ agents do not try to fix this by adding another local cron path.
 
 ```task
 id: CUST-WP-0045-T02
-status: todo
+status: done
 priority: high
 depends_on: [CUST-WP-0045-T01]
+state_hub_task_id: "c4303b24-6f6b-445e-8e2e-94441589a7f2"
 ```
 
 Extend activity-core's existing `state-hub` context resolver instead of adding
@@ -155,6 +158,7 @@ id: CUST-WP-0045-T03
 status: todo
 priority: high
 depends_on: [CUST-WP-0045-T02]
+state_hub_task_id: "e766ff2e-1887-49e6-9c66-598bb395e76c"
 ```
 
 Finish the activity-core instruction/report execution path needed for judgement
@@ -185,6 +189,7 @@ id: CUST-WP-0045-T04
 status: todo
 priority: high
 depends_on: [CUST-WP-0045-T03]
+state_hub_task_id: "04e56428-d3a8-4aa7-a6e1-172c974ece3a"
 ```
 
 Add deterministic output sinks for report instructions.
@@ -208,6 +213,7 @@ id: CUST-WP-0045-T05
 status: todo
 priority: medium
 depends_on: [CUST-WP-0045-T02, CUST-WP-0045-T03, CUST-WP-0045-T04]
+state_hub_task_id: "0c6d54ec-7ed1-4e80-9cfa-ccb914e65fbf"
 ```
 
 Update `activity-definitions/daily-statehub-wsjf-triage.md` so it is executable
@@ -234,6 +240,7 @@ id: CUST-WP-0045-T06
 status: todo
 priority: high
 depends_on: [CUST-WP-0045-T05]
+state_hub_task_id: "545162d7-0198-4519-a30b-06e88c6db915"
 ```
 
 Run the cutover safely.
@@ -260,6 +267,7 @@ id: CUST-WP-0045-T07
 status: todo
 priority: medium
 depends_on: [CUST-WP-0045-T06]
+state_hub_task_id: "b977c721-cadc-461f-8ffb-715d438e4c31"
 ```
 
 Document and, where cheap, automate how to tell whether the daily run happened.
@@ -283,6 +291,7 @@ id: CUST-WP-0045-T08
 status: todo
 priority: medium
 depends_on: [CUST-WP-0045-T06, CUST-WP-0045-T07]
+state_hub_task_id: "f4a985fd-8cce-4175-983e-cf3b437e19a5"
 ```
 
 Run three consecutive daily canaries from activity-core and compare the
@@ -299,6 +308,26 @@ Feed the result back into `CUST-WP-0044-T06`:
 Done when CUST-WP-0044 can close its calibration task using activity-core runs,
 not Codex app automation runs.
 
+## Implementation Notes - 2026-05-19
+
+T01 is complete. The 2026-05-19 failed Codex automation run is captured in this
+workplan's context, and the runner boundary is explicit: activity-core owns the
+schedule, retries, context resolution, run log, and audit trail; State Hub stays
+the read model and progress sink; the-custodian owns the prompt and guardrails.
+
+T02 is complete in activity-core. The existing `state-hub` context resolver now
+supports the daily triage queries `state_summary`, `next_steps`,
+`workplan_index`, and `hub_inbox` while preserving `domain_summary` and
+`repo_sbom_status`. Resolver failures return `{}` so the workflow can degrade
+to offline context instead of failing the whole run.
+
+Verification:
+
+- `uv run pytest tests/test_state_hub_context_resolver.py -q`:
+  5 passed
+- `uv run pytest -q` in activity-core:
+  95 passed, 1 skipped
+
 ## Acceptance Criteria
 
 - The daily State Hub WSJF triage runs from activity-core, not Codex app cron.