Renumber the records 1 to 23

The consolidation left a sparse sequence -- 1, 4, 6, 7, 9, 10, 12, 15, 16, 18,
19, 25, 34, 35, 36, 37, 40, 42, 44, 45, 48, 49, 58 -- where the gaps were only
the archaeology of what used to be there.

Renumbered contiguously. Renames run in ascending order, so every target number
is already free and no two files ever collide.

The reference rewrite is one simultaneous pass rather than a sequence of
replacements. Numbers moved into slots other numbers were vacating -- the node
host went 37 to 16 while the lab went 16 to 9 -- so replacing one at a time
would have cascaded and silently pointed things at the wrong record.

Seven plain-text references survived the merges as prose rather than links,
naming records that no longer existed: the enrolment token, the link boundary,
what a declaration is, reachability, the repository structure. Each mapped to
the consolidated record that now holds it.

Verified rather than assumed: every [ADR NNNN](path) link now has matching text
and target, checked across the whole repository, and the checker passes.

Frontmatter `consolidates:` lists dropped -- they named records that are gone,
and each consolidated record already says in prose what it absorbed.

01-RESEARCH/010-lab-inner-loop-cost/00-overview.md

@@ -3,8 +3,8 @@ status: active
 initiated: 2026-08-24
 touches:
   - 03-DESIGN/01-to-be/03-scenario-lifecycle.md
-  - 02-DECISIONS/0016-the-lab.md
-  - 02-DECISIONS/0016-the-lab.md
+  - 02-DECISIONS/0009-the-lab.md
+  - 02-DECISIONS/0009-the-lab.md
 became: []
 ---
 
@@ -23,7 +23,7 @@ Measured on a workstation, 2026-08-24. Numbers in [`measurements.md`](measuremen
 
 ## Why it matters
 
-[ADR 0016](../../02-DECISIONS/0016-the-lab.md) makes the
+[ADR 0009](../../02-DECISIONS/0009-the-lab.md) makes the
 bootstrap scenario the inner development loop for tiers 0 and 1 — the argument being that
 raising a node from nothing stops being the least-exercised path and becomes the most-exercised
 one. **That argument is only true if raising and resetting are cheap.** A loop that costs

01-RESEARCH/010-lab-inner-loop-cost/measurements.md

@@ -13,7 +13,7 @@ image.
 
 | Fact | Value | Consequence |
 |---|---|---|
-| Hardware virtualisation | present | virtual machines run at native speed; the choice in [ADR 0016](../../02-DECISIONS/0016-the-lab.md) is not paying an emulation penalty |
+| Hardware virtualisation | present | virtual machines run at native speed; the choice in [ADR 0009](../../02-DECISIONS/0009-the-lab.md) is not paying an emulation penalty |
 | Storage drivers the daemon offers | **`dir` only** | no copy-on-write, therefore no cheap snapshot |
 | Host filesystems | ext4 throughout | nothing copy-on-write to put a pool on |
 | btrfs kernel module | **available** | the kernel can do it |
@@ -72,7 +72,7 @@ worst, before any of the mesh's own work begins.
 
 **This is too slow for an inner loop**, and the reason is not the design.
 
-[ADR 0016](../../02-DECISIONS/0016-the-lab.md) argues that
+[ADR 0009](../../02-DECISIONS/0009-the-lab.md) argues that
 making the bootstrap path the inner development loop turns the least-exercised code in the
 system into the most-exercised. That argument holds only while resetting is cheap. At a minute
 and a half a cycle, with occasional multi-minute stalls, the loop is one a person works around
@@ -120,7 +120,7 @@ A four-machine reset-and-rerun cycle, the operation the inner loop repeats most:
 | **cycle** | **~90 s, unbounded at worst** | **~15 s, dominated by boot** |
 
 At fifteen seconds, dominated by a boot that cannot be avoided, the inner loop is viable and
-[ADR 0016](../../02-DECISIONS/0016-the-lab.md)'s argument holds.
+[ADR 0009](../../02-DECISIONS/0009-the-lab.md)'s argument holds.
 At ninety it did not.
 
 ### One honest counter-observation