diff --git a/workplans/CB-WP-0005-assertion-coverage.md b/workplans/CB-WP-0005-assertion-coverage.md
index ffb6fb3..9ec9b92 100644
--- a/workplans/CB-WP-0005-assertion-coverage.md
+++ b/workplans/CB-WP-0005-assertion-coverage.md
@@ -279,7 +279,7 @@ state_hub_task_id: "774b1c8a-3b26-4c4f-a2c8-46cb0b7ba5a7"
 
 ```task
 id: CB-WP-0005-T07
-status: todo
+status: done
 priority: high
 state_hub_task_id: "a34baa46-fbfd-473b-9e15-811e17697791"
 ```
@@ -390,6 +390,14 @@ having**. `mutation-check` fails that test and still produced the most
 valuable findings of the pass. T06 stated it too strongly; this pass is
 the counter-example.
 
+**Attribution note.** T07 and T08 shipped in one commit, and CA-08 keys on
+the first qualified task id in the subject — so T07's bucket ($3.06 over
+13 responses) covers the substantive work of both, and T08's own figure
+covers only its close. `make task-done` refused to close T08 at all until
+a commit named it, which is the "no estimates" contract working as
+designed rather than a defect. The lesson is cheap: **one commit, one
+task id**.
+
 **InnerLoop v1.4** adopted: where a claim rests on numbers, the
 adversarial reviewer must read the assertion behind each quoted number and
 **mutate it**. Re-running the command that prints a number is not