diff --git a/workplans/CUST-WP-0074-qualified-wait-states.md b/workplans/CUST-WP-0074-qualified-wait-states.md
index 2954b7f..27063de 100644
--- a/workplans/CUST-WP-0074-qualified-wait-states.md
+++ b/workplans/CUST-WP-0074-qualified-wait-states.md
@@ -132,7 +132,7 @@ Founder accepted 2026-09-28; standard set to `accepted`, revision `accepted-1`.
 
 ```task
 id: CUST-WP-0074-T02
-status: progress
+status: done
 priority: high
 state_hub_task_id: "e5a05f83-1db5-59a7-8cae-095237f50b7d"
 ```
@@ -159,6 +159,18 @@ founder-run step (agent deploy blocked by harness policy):
 commit `appVersion`, then `make fix-consistency` across the touched repos
 writes the ~130 parked task edges.
 
+**Done 2026-09-29 00:21 CEST** — founder ran the promote: release rev 66,
+`main-85cc6d7` on both pods, `schema.applied = e8f9a0b1c2d3`, `appVersion`
+recorded (`65cda5d`). Sync across the 21 repos wrote 126 task-scoped
+dependency rows. First read-model answer: blocked workplans by
+`blocked_kind` = human 29, external 22, none 59; wait tasks by `wait_kind`
+= external 63, human 28, both 11, unqualified 147 (the hub counts
+`blocked_on: message-from:` waits as unqualified — the rule-6 follow-up —
+plus the long tail). Fabric's coordination export consumes the fields
+(63/28/11) but reports `task_depends_on_edges: 0` because it reads
+`/state/deps` stubs, which do not carry `from_task_id` yet — T04 follow-up
+in RAIL-FAB-WP-0029, not a blocker.
+
 Owner: state-hub. Founder 2026-09-28: implement directly from this plan,
 no delegated `STATE-WP` workplan — keep the layer count down while getting
 a grip on exactly this. Receipt (commits, checks, tests) is recorded here.