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/005-domain-grouping/00-overview.md

@@ -2,17 +2,17 @@
 status: graduated
 initiated: 2026-08-23
 touches:
-  - 02-DECISIONS/0044-modules-and-the-graph.md
+  - 02-DECISIONS/0019-modules-and-the-graph.md
   - 03-DESIGN/00-as-is/10-module-catalogue.md
   - 03-DESIGN/00-as-is/02-modules-and-manifests.md
 became:
-  - 02-DECISIONS/0044-modules-and-the-graph.md
-  - 02-DECISIONS/0044-modules-and-the-graph.md
+  - 02-DECISIONS/0019-modules-and-the-graph.md
+  - 02-DECISIONS/0019-modules-and-the-graph.md
 ---
 
 # 005 — Which domains the catalogue groups into
 
-[ADR 0044](../../02-DECISIONS/0044-modules-and-the-graph.md) settles
+[ADR 0019](../../02-DECISIONS/0019-modules-and-the-graph.md) settles
 that modules outside the platform core are grouped by domain rather than by single function,
 and deliberately does not settle the list. This effort settles the list — and, first, tests
 whether the premise survives measurement.
@@ -59,12 +59,12 @@ open questions below.
 this effort — which is why it stayed open after being resolved.
 
 **Whether provider modules group at all** — *no.*
-[ADR 0044](../../02-DECISIONS/0044-modules-and-the-graph.md):
+[ADR 0019](../../02-DECISIONS/0019-modules-and-the-graph.md):
 there is no `networking` thing to install, there are concrete modules named individually. Folders
 assert relationships; edges record them. *Provider* stops being a category at the same time.
 
 **Whether "group or leave" is even the right pair of options** — *it was not*, and that is the
-useful finding. [ADR 0044](../../02-DECISIONS/0044-modules-and-the-graph.md)
+useful finding. [ADR 0019](../../02-DECISIONS/0019-modules-and-the-graph.md)
 reframes it: things that change together share an **authority**, not a package. This effort's own
 measurement is what that record rests on — reachability being the *only* place modules genuinely
 co-change is why connectivity is a context and why nothing else needed one.

01-RESEARCH/005-domain-grouping/analysis.md

@@ -10,7 +10,7 @@ updated: 2026-08-23
 Every commit in the code repository's main branch that touches the module catalogue, reduced
 to the set of modules it touched. Platform-namespace modules are excluded — their
 decomposition is settled by
-[ADR 0015](../../02-DECISIONS/0015-mesh-brokers-nodes-host-agents-think.md). Modules that no
+[ADR 0008](../../02-DECISIONS/0008-mesh-brokers-nodes-host-agents-think.md). Modules that no
 longer exist are excluded, because pre-rename names dominate the raw signal and describe a
 catalogue nobody works in.