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/cases.md

@@ -13,7 +13,7 @@ it is simply up. *A relational store, a message broker, an object store, a dashb
 
 **2 — A system package with configuration.** Not a container. Installed into the machine,
 configured through files, run by the service manager. *A firewall, a resolver, an overlay.*
-Note: [ADR 0037](../../02-DECISIONS/0037-the-node-host.md) says applying
+Note: [ADR 0016](../../02-DECISIONS/0016-the-node-host.md) says applying
 these is the host's job — so what the module contributes is the *deciding*, not the doing.
 
 **3 — An application a person launches.** Installed on a node, started by a human, running only
@@ -35,7 +35,7 @@ provider behind an assistant interface.*
 
 **9 — A standalone application in its own repository.** Same shape as any of the above; the
 difference is only where its source lives
-([ADR 0010](../../02-DECISIONS/0010-applications-live-in-their-own-repository.md)). Worth
+([ADR 0006](../../02-DECISIONS/0006-applications-live-in-their-own-repository.md)). Worth
 listing because a schema that assumes a monorepo path would exclude it.
 
 ## The cases that break a naive schema