Reevaluate blocked workplans WP-0008/0009/0010/0015

Unblock lifecycle statuses after daily triage trust evidence closed
(06-28 through 07-03 clean scheduled runs). Finish WP-0010, return
WP-0008/0009/0015 to active with accurate wait reasons, and document
the scheduled-wait vs hard-blocker distinction.

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

@@ -4,11 +4,11 @@ type: workplan
 title: "Weekly Coding Retrospection schedule (Saturday evenings)"
 domain: custodian
 repo: activity-core
-status: blocked
+status: active
 owner: codex
 topic_slug: custodian
 created: "2026-06-07"
-updated: "2026-06-17"
+updated: "2026-07-03"
 state_hub_workstream_id: "7387fc50-1f2c-471a-9d85-bb085cbd0b63"
 ---
 
@@ -107,3 +107,11 @@ 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.
+
+2026-07-03 reevaluation: `AGENTIC-WP-0010` remains finished and the resolver
+smoke still works, but State Hub still has only the 2026-06-07 weekly
+`coding_retro` read model (`ec20ac1c`, `window.days=7`) with zero suggestions.
+No newer weekly publish exists yet. This is a **time-controlled wait** on the
+next Saturday 19:00 Europe/Berlin publish (or an operator decision to enable on
+the zero-suggestion proof), not a hard blocker. Workplan status returns to
+`active`; T03 stays `wait`.