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/003-service-supervision/00-overview.md

@@ -3,8 +3,8 @@ status: graduated
 initiated: 2026-08-22
 touches: [03-DESIGN/00-as-is/05-runtime-and-installation.md]
 became:
-  - 02-DECISIONS/0037-the-node-host.md
-  - 02-DECISIONS/0037-the-node-host.md
+  - 02-DECISIONS/0016-the-node-host.md
+  - 02-DECISIONS/0016-the-node-host.md
   - 03-DESIGN/01-to-be/05-the-node-host.md
 ---
 
@@ -43,7 +43,7 @@ This effort answers the cost half. It does not choose.
 - **There is a third option neither of us named**, and it is the one that also solves Phase 0:
   run HAL's own daemons as containers, making Docker the supervisor for everything. Local and
   production then have the same shape rather than a translation layer between them.
-- **It cannot be all-or-nothing**, and ADR 0015 already says why: a human agent acts through a
+- **It cannot be all-or-nothing**, and ADR 0008 already says why: a human agent acts through a
   shell and a desktop. Those parts are on the host by definition.
 - One incidental finding: the automatic node rescue that documentation describes **does not
   exist**. No unit declares `OnFailure=`, and nothing calls `hal-rescue.sh` on a timer.
@@ -57,14 +57,14 @@ which is why the effort sat `active` for five days after being answered. Recorde
 finding that is the point of a sweep.
 
 **The third option is what the mesh adopted.** `Docker is the supervisor for everything` is
-[ADR 0037](../../02-DECISIONS/0037-the-node-host.md): the
+[ADR 0016](../../02-DECISIONS/0016-the-node-host.md): the
 host is a plain process on the machine and everything above tier 0 is a container. The substrate
 bootstrap declares no service at all — it is package, container, action, container — so the
 44-of-44 restart policies this effort counted are the supervision, exactly as it argued.
 
 **Fate-sharing was the hard part, and it is solved the way this effort predicted.** It said any
 mesh-native supervisor inherits the problem *unless it sits outside the mesh's own process
-tree*. [ADR 0037](../../02-DECISIONS/0037-the-node-host.md) puts
+tree*. [ADR 0016](../../02-DECISIONS/0016-the-node-host.md) puts
 the launcher there: it supervises the host as a child and shares no code with it, so a host that
 cannot start is still recovered.
 

01-RESEARCH/003-service-supervision/analysis.md

@@ -128,10 +128,10 @@ What it costs, honestly:
 
 ---
 
-## 5. Why it cannot be all-or-nothing — and ADR 0015 already says so
+## 5. Why it cannot be all-or-nothing — and ADR 0008 already says so
 
 Some of what runs under systemd today **cannot** be containerised, and the reason is
-already in the domain model. ADR 0015:
+already in the domain model. ADR 0008:
 
 > a non-human agent acts through a spawned session — a human agent acts through a shell or
 > desktop
@@ -223,7 +223,7 @@ fate-sharing reason in §3.
 ## References
 
 - [`002-local-mesh`](../002-local-mesh/analysis.md) — the effort this came out of
-- [`02-DECISIONS/0001`](../../02-DECISIONS/0015-mesh-brokers-nodes-host-agents-think.md) — agent modality, which
+- [`02-DECISIONS/0001`](../../02-DECISIONS/0008-mesh-brokers-nodes-host-agents-think.md) — agent modality, which
   decides what cannot leave the host
 - `modules/hal/meshware/daemon/src/cerebellum.ts:815-828` — the self-restart workaround
 - `modules/hal/meshware/systemd/hal-module@.service` — the per-module Docker lifecycle