Order the records the way the system is learned

Jochen asked whether the order made sense. It did not -- it followed when
things happened to be decided, which after consolidation is fictional anyway
since record 5 alone folds decisions taken across a week.

Concretely wrong before: the domain statement sat at 8, after five engineering
rules; the constitution was scattered across 5, 12 and 17; the tiers landed at
15, 16, 21 and 22 with process records in between.

Now it walks: what the mesh is (1-3), its tiers from the bottom up (4-8), what
runs on them and how it gets there (9-10), how it is built (11-16), how it is
checked (17-18), how we work (19-23).

Two things made this safe rather than free. It is a permutation, not a
compaction, so the renames go through temporary names -- otherwise two files
want one slot and one is lost. And the reference rewrite is a single
simultaneous pass, because almost every number moved into a slot another number
was vacating; replacing one at a time would have cascaded and pointed things at
the wrong record while still resolving.

Verified: 284 [ADR NNNN](path) links across the repository, all with matching
text and target.

The ordering principle is now stated in 19 rather than left implicit -- the
repository already said "the numbering is the flow" about its folders, and
there was no reason for the records to be the exception.

03-DESIGN/00-as-is/11-the-lab.md

@@ -4,11 +4,11 @@ status: implemented
 code: [mesh-lab]
 updated: 2026-08-25
 decisions:
-  - 02-DECISIONS/0009-the-lab.md
-  - 02-DECISIONS/0009-the-lab.md
-  - 02-DECISIONS/0009-the-lab.md
-  - 02-DECISIONS/0009-the-lab.md
-  - 02-DECISIONS/0009-the-lab.md
+  - 02-DECISIONS/0016-the-lab.md
+  - 02-DECISIONS/0016-the-lab.md
+  - 02-DECISIONS/0016-the-lab.md
+  - 02-DECISIONS/0016-the-lab.md
+  - 02-DECISIONS/0016-the-lab.md
 ---
 
 # The lab, as it stands
@@ -63,7 +63,7 @@ is built.
 
 **The drawing was never designed.** `diagram` renders a scenario as draw.io, from the
 declaration or from the running instance, and it exists because it was asked for during the
-build. It has tests and a decision record ([ADR 0014](../../02-DECISIONS/0014-a-picture-is-read-from-what-runs.md),
+build. It has tests and a decision record ([ADR 0018](../../02-DECISIONS/0018-a-picture-is-read-from-what-runs.md),
 proposed) but no document in the to-be layer. It is recorded here because it runs, not because
 it was planned.
 
@@ -117,7 +117,7 @@ and snapshots roughly 76× slower, which does not make the lab slow, it makes it
 
 `npm run check` — typecheck over source *and* tests, then the offline suite, then integration
 against a real hypervisor. Mocking the hypervisor is forbidden
-([ADR 0013](../../02-DECISIONS/0013-a-test-defends-a-decision.md), proposed): a test that fakes
+([ADR 0017](../../02-DECISIONS/0017-a-test-defends-a-decision.md), proposed): a test that fakes
 the system under integration asserts that the fake behaves as expected.
 
 Integration tests **skip with a reason** on a machine that cannot raise scenarios, rather than