Sync hub IDs for CB-WP-0006; T04-T06 cancel not deferred

The hub's task status vocabulary is wait|todo|progress|done|cancel, so
'deferred' was rejected by fix-consistency. 'cancel' is the accurate one:
these task records are superseded and equivalents live in CB-WP-0006
T05-T07. The work is deferred, not abandoned, and the workplan says so.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

workplans/CB-WP-0005-assertion-coverage.md

@@ -238,6 +238,11 @@ downgrade inline, so a reader of the spec cannot reach the old claim.
 > T04, T05 and T06 stay in this file, unstarted, with their analysis
 > intact; they move to **CB-WP-0006**, which is scoped to the finding that
 > was actually measured rather than the one that was predicted.
+>
+> They carry `status: cancel` — the hub's status vocabulary is
+> `wait|todo|progress|done|cancel`, and of those `cancel` is the accurate
+> one: *these* task records are superseded, and equivalents live in
+> CB-WP-0006 T05–T07. The work is deferred, not abandoned.
 
 ## Phase C — implement what the instruments expose (deferred)
 
@@ -245,7 +250,7 @@ downgrade inline, so a reader of the spec cannot reach the old claim.
 
 ```task
 id: CB-WP-0005-T04
-status: deferred
+status: cancel
 priority: high
 state_hub_task_id: "35876b28-97ac-4379-bb71-72e74c4116d4"
 ```
@@ -273,7 +278,7 @@ the length prefix → reject. K11's operative clause is *detection*.
 
 ```task
 id: CB-WP-0005-T05
-status: deferred
+status: cancel
 priority: high
 state_hub_task_id: "8592b6e7-8b83-4b47-b310-90e16a35eb6a"
 ```
@@ -308,7 +313,7 @@ charged to **AM-4b** (9.4% headroom), not AM-4a.
 
 ```task
 id: CB-WP-0005-T06
-status: deferred
+status: cancel
 priority: medium
 state_hub_task_id: "774b1c8a-71c1-4e0a-91b1-0247a3e397cf"
 ```