Record CUST-WP-0045 implementation start

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

@@ -106,7 +106,7 @@ 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"
 ```
@@ -128,7 +128,7 @@ 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"
@@ -308,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.