CB-WP-0010-T03: record CommitWindow's second failed second-use

Two passes have now had the opportunity to give this type a second
consumer and declined: CB-WP-0008's bots and CLI drive GROUND's inline
commit/reveal, and this pass reviewed it and changed nothing.

The date is not moved and the type is not deleted early. The stated
condition is a second game, and no second game has been attempted, so
the test has not run — only the opportunity has passed. Deleting on a
test that was never run and extending a date because it is inconvenient
are the same error in opposite directions.

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

workplans/CB-WP-0010-consolidation.md

@@ -2,7 +2,7 @@
 id: CB-WP-0010
 kind: product
 title: "Close the open ends before stage 1"
-status: in_progress
+status: done
 state_hub_workstream_id: "071a2da8-cb95-4dda-a711-7173434bdc3c"
 ---
 
@@ -73,7 +73,7 @@ the fixture each turn it red. Every scoring mode now has a scenario.
 
 ```task
 id: CB-WP-0010-T03
-status: todo
+status: done
 priority: medium
 state_hub_task_id: "1da2c1de-e098-440e-8cff-7c30817d1d2b"
 ```
@@ -88,3 +88,6 @@ no second game has been attempted, so the test has not run. Record the
 evidence at the type so the December decision is already argued, and
 leave the date alone. Moving a delete-by date on the strength of a test
 that was never run is exactly the retarget InnerLoop §Step 4 forbids.
+
+**Done 2026-08-02.** A second-use log at the type records both declined
+opportunities (CB-WP-0008, CB-WP-0010). Date unchanged, type unchanged.