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/00-as-is/02-modules-and-manifests.md

@@ -4,9 +4,9 @@ status: implemented
 code: [hal]
 updated: 2026-08-23
 decisions:
-  - 02-DECISIONS/0044-modules-and-the-graph.md
-  - 02-DECISIONS/0006-schema-changes-are-numbered-migrations.md
-  - 02-DECISIONS/0007-no-npm-workspace.md
+  - 02-DECISIONS/0019-modules-and-the-graph.md
+  - 02-DECISIONS/0003-schema-changes-are-numbered-migrations.md
+  - 02-DECISIONS/0004-no-npm-workspace.md
 ---
 
 # Modules, manifests and features
@@ -81,7 +81,7 @@ recorded in the knowledge base; both presented as "the change did not apply" wit
 ## Dependencies between modules
 
 Modules depend on each other, above all on the shared library they all build against. There is
-**no workspace** ([ADR 0007](../../02-DECISIONS/0007-no-npm-workspace.md)): each module is a standalone
+**no workspace** ([ADR 0004](../../02-DECISIONS/0004-no-npm-workspace.md)): each module is a standalone
 package consuming published dependencies, including the mesh's own.
 
 The pipeline resolves modules into dependency **levels** and completes a level before starting
@@ -96,7 +96,7 @@ since (see
 
 A module that owns state owns its migrations: numbered, written in the module's own language,
 compiled with it, frozen once they have run anywhere, and idempotent so that re-running is safe
-([ADR 0006](../../02-DECISIONS/0006-schema-changes-are-numbered-migrations.md)).
+([ADR 0003](../../02-DECISIONS/0003-schema-changes-are-numbered-migrations.md)).
 
 Two kinds exist and the distinction matters: migrations against the module's **own** local
 state, and migrations against a **provisioned** resource, which run on the node that consumes