Consolidate: 65 decision records to 52

Jochen: a normal application has 3-5 ADRs, maybe 10 for a large one, and we are
at 65. Fair, and the cause is mine -- I recorded every FINDING as a decision
rather than every fork in the road.

Two merges, both cases where one decision had been split across many records
because it was taken over several days rather than at once.

0019 absorbs ten records about how this repository works: what it is and that
it is public, the folder flow, the two design layers, the issue front door,
status in frontmatter, playbooks, the naming rule, the product name. Those were
never ten decisions -- they were one, seen from ten angles as the repository
took shape.

0016 absorbs the five about the lab: a node is a virtual machine, a router is
scenery, a scenario declares the underlay, a scenario is a closed address
space, and the two scenario classes. Same pattern -- one design, split by the
order it was worked out in.

The consolidated 0019 also raises the bar for what earns a record, since that
is what produced 65: a record is warranted when there is a genuine fork -- a
direction reversed, an alternative that will be proposed again, something
contested. A finding is not a decision, and a bug is certainly not. Everything
else belongs in the design document where the reasoning is actually read.

The checker earned its place here. Deleting nine records left 13 dangling links
across the repository and it named every one, including in AGENTS.md. Nothing
was found by reading.

Remaining clusters worth the same treatment: the host (8 records), delivery
(5), modules (6), connectivity (4), substrate and control plane (4). That would
be 52 down to roughly 30.

03-DESIGN/01-to-be/03-scenario-lifecycle.md

@@ -4,16 +4,16 @@ status: in-progress
 code: [mesh-lab]
 updated: 2026-08-25
 decisions:
-  - 02-DECISIONS/0029-the-labs-first-scenario-has-no-pipeline.md
-  - 02-DECISIONS/0031-the-lab-provides-the-underlay.md
-  - 02-DECISIONS/0032-a-scenario-is-an-isolated-address-space.md
+  - 02-DECISIONS/0016-the-lab.md
+  - 02-DECISIONS/0016-the-lab.md
+  - 02-DECISIONS/0016-the-lab.md
 ---
 
 # Scenario lifecycle
 
 The first thing the lab must do, and the only thing it must do before anything else can be
 written: **materialise a mesh, return it to a known state, and destroy it**
-([ADR 0029](../../02-DECISIONS/0029-the-labs-first-scenario-has-no-pipeline.md)).
+([ADR 0016](../../02-DECISIONS/0016-the-lab.md)).
 
 A [declaration](02-scenario-declaration.md) describes a scenario. This describes what happens
 to one.
@@ -39,7 +39,7 @@ The order is not arbitrary — each step needs the one before it to exist:
 
 1. **Segments.** Isolated links, one per declared segment, belonging to this instance and
    joined to nothing outside it
-   ([ADR 0032](../../02-DECISIONS/0032-a-scenario-is-an-isolated-address-space.md)).
+   ([ADR 0016](../../02-DECISIONS/0016-the-lab.md)).
 2. **Gateways.** Derived, never declared as machines: a gateway is materialised for each
    distinct `gateway:` declaration, sitting on both its segment and its parent, carrying the
    translation, forwarding and mapping-expiry the declaration asked for.
@@ -100,7 +100,7 @@ made after it, and returning undoes it like any other change.
 ## Reaching in
 
 Everything the lab does to a machine goes through the virtualisation layer, never over IP
-([ADR 0032](../../02-DECISIONS/0032-a-scenario-is-an-isolated-address-space.md)). `exec` runs a
+([ADR 0016](../../02-DECISIONS/0016-the-lab.md)). `exec` runs a
 command on a machine and returns its output.
 
 This has one consequence worth stating plainly: **a reachability question is asked from inside**.