T09: InnerLoop v1.0 — corrected from the first full pass

The loop has now survived CB-WP-0001 end to end and is revised from what
that pass actually taught, recorded in
history/260731-inner-loop-retrospective.md.

Held up: the adversarial review (one blocking and three significant
findings on its single use, resolved with new measurements rather than
argument), the parity-cap rule, the provisional U-item mechanism, and
the ADR gate.

The gap: both serious errors in the pass were measurement errors, and
the loop caught neither. Review reads prose; these were claims about
numbers. In both cases a harness ran successfully while doing no work —
a JS harness timing rejected no-ops, and a Rust benchmark computing
throughput for rounds that never completed.

v1.0 adds:
- Measurement validity: a harness must assert it performed the work it
  reports. A number from a run that cannot prove it did the work is void.
- Metric feasibility: every metric names its instrument and is checked
  reachable against the contracts in its own spec.
- No silently-ignored input; decisions get commands, not defaults;
  scaffolds are exercised or marked; coverage gates that count tags say
  so.
- Evidence must state what a comparison does not support.
- The chaos roll is recorded even when it changes nothing, so a
  mechanism that never fires is visible rather than assumed.

CB-WP-0001 is complete: 9/9 tasks done.

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

workplans/CB-WP-0001-inner-loop.md

@@ -1,7 +1,7 @@
 ---
 id: CB-WP-0001
 title: "Establish the assimilate-and-surpass inner loop via the GROUND game kernel"
-status: active
+status: done
 state_hub_workstream_id: "a1b434dc-b1c6-46b5-bbd9-80a4e6b7620f"
 ---
 
@@ -183,7 +183,7 @@ per-task token counts were never instrumented — also a T09 input.
 
 ```task
 id: CB-WP-0001-T09
-status: todo
+status: done
 priority: low
 state_hub_task_id: "e99b107e-087e-49e1-96b5-67805deb242f"
 ```
@@ -193,3 +193,11 @@ heavy or too thin, what the survey template missed, what metrics turned out
 to matter. Output is InnerLoop v1.0 — the process the next capability
 workplan starts from. The loop is only "established" once it has survived
 its first full pass and been corrected.
+
+**Outcome:** specs/InnerLoop.md v1.0 and
+history/260731-inner-loop-retrospective.md. The adversarial review, the
+parity cap, the provisional mechanism and the ADR gate held. The gap the
+pass exposed: both serious errors were *measurement* errors and review
+caught neither, because review reads prose and these were claims about
+numbers. v1.0 adds the positive-control rule, metric feasibility and
+instrument naming, and four implementation rules.