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/01-end-to-end-testing.md

@@ -4,9 +4,9 @@ status: in-progress
 code: [mesh-lab]
 updated: 2026-08-23
 decisions:
-  - 02-DECISIONS/0016-the-lab.md
-  - 02-DECISIONS/0016-the-lab.md
-  - 02-DECISIONS/0019-how-this-repository-works.md
+  - 02-DECISIONS/0009-the-lab.md
+  - 02-DECISIONS/0009-the-lab.md
+  - 02-DECISIONS/0011-how-this-repository-works.md
 ---
 
 # End-to-end testing
@@ -37,7 +37,7 @@ today, that is a gap in the vocabulary rather than a reason to privilege that sh
 
 The design below describes a scenario as a complete mesh — forge (Gitea), coordinator,
 delivery cascade — because what it tests is a module. **That is the larger of two classes, and
-not the first one built** ([ADR 0016](../../02-DECISIONS/0016-the-lab.md)).
+not the first one built** ([ADR 0009](../../02-DECISIONS/0009-the-lab.md)).
 
 | | **Bootstrap scenario** | **Full scenario** |
 |---|---|---|
@@ -127,7 +127,7 @@ drifts.
   a mesh named by the request instead.
 - **Scenarios must be concurrent and cheap.** Several agents working means several scenarios
   at once, each needing its own network and nodes. A lab node is a virtual machine
-  ([ADR 0016](../../02-DECISIONS/0016-the-lab.md)), and snapshots are
+  ([ADR 0009](../../02-DECISIONS/0009-the-lab.md)), and snapshots are
   what make repetition cheap — restoring a scenario costs far less than building one. The
   earlier argument here, that only system containers made this affordable, was superseded: the
   scale it assumed was invented rather than required.