Harden coding retro resolver selection

workplans/ACTIVITY-WP-0008-weekly-coding-retro.md

@@ -8,7 +8,7 @@ status: blocked
 owner: codex
 topic_slug: custodian
 created: "2026-06-07"
-updated: "2026-06-07"
+updated: "2026-06-17"
 state_hub_workstream_id: "7387fc50-1f2c-471a-9d85-bb085cbd0b63"
 ---
 
@@ -47,6 +47,12 @@ resolver. It reads recent `/progress/` items, selects the latest
 `event_type=coding_retro`, normalizes `suggestions[]`, and returns an empty
 suggestion list while the upstream publisher has not produced a read model yet.
 
+**2026-06-17:** Hardened the resolver lookup after live review found recent
+non-retro progress could hide older retro events. The resolver now queries
+State Hub with `event_type=coding_retro` and only selects a read model matching
+the requested `window_days`, so the weekly schedule cannot accidentally route a
+broader 30-day retro batch.
+
 ## `weekly-coding-retro` Activity-Definition
 
 ```task
@@ -92,3 +98,12 @@ make fix-consistency REPO=activity-core
 Live State Hub did not yet expose a published `event_type=coding_retro` progress
 item, so the real dry-run, duplicate check, and `enabled: true` flip remain
 blocked on `AGENTIC-WP-0010`.
+
+**2026-06-17:** `AGENTIC-WP-0010` is finished and State Hub has
+`coding_retro` progress. A live no-write smoke now resolves the matching weekly
+read model `ec20ac1c-ef50-4db4-a5dc-364d31a259a5`
+(`generated_at=2026-06-07T19:25:19Z`, `window.days=7`) and emits zero task
+specs because that weekly read model has zero suggestions. The schedule remains
+disabled until a non-empty weekly read model, or an explicit operator decision
+that a zero-suggestion dry-run is an acceptable enablement proof, confirms
+correct routing and no duplicate target tasks on re-run.