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.

03-DESIGN/01-to-be/03-scenario-lifecycle.md

@@ -4,16 +4,16 @@ status: in-progress
 code: [mesh-lab]
 updated: 2026-08-25
 decisions:
-  - 02-DECISIONS/0016-the-lab.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
+  - 02-DECISIONS/0009-the-lab.md
 ---
 
 # Scenario lifecycle
 
 The first thing the lab must do, and the only thing it must do before anything else can be
 written: **materialise a mesh, return it to a known state, and destroy it**
-([ADR 0016](../../02-DECISIONS/0016-the-lab.md)).
+([ADR 0009](../../02-DECISIONS/0009-the-lab.md)).
 
 A [declaration](02-scenario-declaration.md) describes a scenario. This describes what happens
 to one.
@@ -39,7 +39,7 @@ The order is not arbitrary — each step needs the one before it to exist:
 
 1. **Segments.** Isolated links, one per declared segment, belonging to this instance and
    joined to nothing outside it
-   ([ADR 0016](../../02-DECISIONS/0016-the-lab.md)).
+   ([ADR 0009](../../02-DECISIONS/0009-the-lab.md)).
 2. **Gateways.** Derived, never declared as machines: a gateway is materialised for each
    distinct `gateway:` declaration, sitting on both its segment and its parent, carrying the
    translation, forwarding and mapping-expiry the declaration asked for.
@@ -60,7 +60,7 @@ habit.
 ## A failed raise leaves the wreckage
 
 A step that fails stops the raise
-([ADR 0058](../../02-DECISIONS/0058-delivery.md)) — and **does not tear
+([ADR 0023](../../02-DECISIONS/0023-delivery.md)) — and **does not tear
 down**.
 
 Tearing down on failure destroys the only evidence of what went wrong, which is precisely
@@ -100,7 +100,7 @@ made after it, and returning undoes it like any other change.
 ## Reaching in
 
 Everything the lab does to a machine goes through the virtualisation layer, never over IP
-([ADR 0016](../../02-DECISIONS/0016-the-lab.md)). `exec` runs a
+([ADR 0009](../../02-DECISIONS/0009-the-lab.md)). `exec` runs a
 command on a machine and returns its output.
 
 This has one consequence worth stating plainly: **a reachability question is asked from inside**.