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.

README.md

@@ -100,7 +100,7 @@ Answered separately, a repository of its own is the better home:
   changes. Tying documents to a code branch means they merge on the code's schedule.
 - **The reviewers are different.** A design argument is not reviewed the way an
   implementation is, and it should not queue behind a build.
-- **The scope is wider than one repository.** [ADR 0015](02-DECISIONS/0015-mesh-brokers-nodes-host-agents-think.md) sends most modules out of the
+- **The scope is wider than one repository.** [ADR 0008](02-DECISIONS/0008-mesh-brokers-nodes-host-agents-think.md) sends most modules out of the
   monorepo entirely. Documentation that governs several repositories cannot live inside one
   of them.
 
@@ -110,4 +110,4 @@ than a mechanism — which is why every decision is recorded in
 [`02-DECISIONS`](02-DECISIONS/) as it is taken, and why a document that states a rule should
 say how the rule is checked.
 
-Recorded as [ADR 0019](02-DECISIONS/0019-how-this-repository-works.md).
+Recorded as [ADR 0011](02-DECISIONS/0011-how-this-repository-works.md).