CB-WP-0010: close the open ends before stage 1

Tier S (structural S; chaos d4=1, no override; declaration 5 of 12).
Three items carried out of the last two passes: CB-WP-0007 left at 2/6
with both remaining tasks overtaken, GR-E03 with no scenario at all, and
CommitWindow's second failed second-use. CB-EV-0008 §4 also says the next
pass should be product, and this is how the meta share comes back down.

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

WORK-RECORDS.md

@@ -16,7 +16,7 @@
 | workplan | CB-WP-0006 | done | — | workplans/CB-WP-0006-instrument-the-table.md |
 | workplan | CB-WP-0007 | in_progress | — | workplans/CB-WP-0007-session-shape.md |
 | workplan | CB-WP-0008 | done | — | workplans/CB-WP-0008-ship-stage-0.md |
-| workplan | CB-WP-0009 | proposed | — | workplans/CB-WP-0009-adaptive-gates.md |
+| workplan | CB-WP-0009 | done | — | workplans/CB-WP-0009-adaptive-gates.md |
 | task | CB-WP-0001-T01 | done | — | workplans/CB-WP-0001-inner-loop.md |
 | task | CB-WP-0001-T02 | done | — | workplans/CB-WP-0001-inner-loop.md |
 | task | CB-WP-0001-T03 | done | — | workplans/CB-WP-0001-inner-loop.md |
@@ -77,7 +77,7 @@
 | task | CB-WP-0008-T02 | done | — | workplans/CB-WP-0008-ship-stage-0.md |
 | task | CB-WP-0008-T03 | done | — | workplans/CB-WP-0008-ship-stage-0.md |
 | task | CB-WP-0008-T04 | done | — | workplans/CB-WP-0008-ship-stage-0.md |
-| task | CB-WP-0009-T01 | todo | — | workplans/CB-WP-0009-adaptive-gates.md |
-| task | CB-WP-0009-T02 | todo | — | workplans/CB-WP-0009-adaptive-gates.md |
-| task | CB-WP-0009-T03 | todo | — | workplans/CB-WP-0009-adaptive-gates.md |
-| task | CB-WP-0009-T04 | todo | — | workplans/CB-WP-0009-adaptive-gates.md |
+| task | CB-WP-0009-T01 | done | — | workplans/CB-WP-0009-adaptive-gates.md |
+| task | CB-WP-0009-T02 | done | — | workplans/CB-WP-0009-adaptive-gates.md |
+| task | CB-WP-0009-T03 | done | — | workplans/CB-WP-0009-adaptive-gates.md |
+| task | CB-WP-0009-T04 | done | — | workplans/CB-WP-0009-adaptive-gates.md |

workplans/CB-WP-0010-consolidation.md

@@ -0,0 +1,84 @@
+---
+id: CB-WP-0010
+kind: product
+title: "Close the open ends before stage 1"
+status: proposed
+state_hub_workstream_id: ""
+---
+
+# Purpose
+
+Tier **S** (structural S — fixes and one scenario, no capability port, no
+canonical interface, no dependency; chaos d4=1, no override; declaration
+5 of 12). One provenance paragraph per commit, no survey, no ADR.
+
+Four items were carried out of CB-WP-0008 and CB-WP-0009 as open. Three
+are cheap and closing them costs less than carrying them into a tier-L
+stage-1 pass, where they would compete for attention with new work.
+[CB-EV-0008](../evidence/CB-EV-0008-adaptive-gates.md) §4 also says the
+next pass should be `product` — the meta budget reads 45% of the trailing
+three against a soft 25%, and this pass is how it comes back down.
+
+## Task: close CB-WP-0007
+
+```task
+id: CB-WP-0010-T01
+status: todo
+priority: high
+state_hub_task_id: ""
+```
+
+CB-WP-0007 sits at 2/6 with T05 and T06 `todo`. Both were overtaken:
+
+- **T05** (control loop for the session-shape pass) was answered by
+  CB-EV-0008 §1 and §4, which measured the windowed metric and the budget
+  firing on real passes.
+- **T06** asked whether there is a *fourth* way a number can fail to bind.
+  There is, and it is on record: CB-EV-0007 §3 found one **aggregated over
+  a window that cannot move it** — reintroduced two tasks after the same
+  defect was fixed for session shape.
+
+Cancel both with pointers and mark the workplan `done`. A workplan left
+`in_progress` forever makes `make status` name a stale next task, which
+is what it has been doing for two passes.
+
+## Task: GR-E03 gets a scenario
+
+```task
+id: CB-WP-0010-T02
+status: todo
+priority: high
+state_hub_task_id: ""
+```
+
+CB-EV-0007 §1: **COMMON PROBLEM (GR-E03) is implemented, referenced by no
+test, and would not fail if deleted.** GR-E02 and GR-E04 both have
+scenarios; this is the only scoring mode with none.
+
+Deliver `scenarios/ground/gr-e03-common-problem.yaml`: the group meets the
+threshold, personal scores are claimed value −1 per Blame held, and the
+highest personal score wins. Use the 5-player preset, where the threshold
+is actually reachable (10 available against 9).
+
+**Finding a defect here is the likely outcome and is the point** — this
+is the first execution of that code path.
+
+## Task: record CommitWindow's second failed use
+
+```task
+id: CB-WP-0010-T03
+status: todo
+priority: medium
+state_hub_task_id: ""
+```
+
+`CommitWindow` is PROVISIONAL with a delete-by of 2026-12-31, on the
+condition *"delete it if no second game uses it"*. CB-WP-0008 was its
+best chance at a second consumer and did not take it — the bots and the
+CLI drive GROUND's inline implementation.
+
+**Do not delete it early.** The stated condition is a second *game*, and
+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.