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/011-the-module-graph/analysis.md

@@ -36,7 +36,7 @@ another module's provision is treated as an implicit edge to that module**, so a
 not have to declare the same relationship twice.
 
 So *ordering by the graph* — which
-[ADR 0037](../../02-DECISIONS/0037-the-node-host.md) says
+[ADR 0016](../../02-DECISIONS/0016-the-node-host.md) says
 the control plane will do — is not a thing to build. It is a thing to call.
 
 ## Finding 3 — the most important edges in the mesh are invisible
@@ -82,7 +82,7 @@ means.
 ## Finding 4 — the resolver continues past faults it should stop on
 
 Two behaviours, both contrary to
-[ADR 0058](../../02-DECISIONS/0058-delivery.md):
+[ADR 0023](../../02-DECISIONS/0023-delivery.md):
 
 - **A cycle warns and falls back to input order.** A cycle means no correct order exists; the
   resolver proceeds with an arbitrary one and logs a line.
@@ -91,7 +91,7 @@ Two behaviours, both contrary to
 
 Neither has fired in the current catalogue — there are no cycles and nothing dangling — which
 is why nobody has noticed. They are latent, and they are in the component that
-[ADR 0037](../../02-DECISIONS/0037-the-node-host.md) makes
+[ADR 0016](../../02-DECISIONS/0016-the-node-host.md) makes
 responsible for the ordering a host will apply without question.
 
 ## Finding 5 — placement is decided in the catalogue