Review: three ADRs no longer said what we had concluded

A sweep for claims overtaken by the last few days. Annotated rather than
rewritten, following the pattern already in 0049 -- what changed and why is the
useful part, and an accepted record should not quietly become something else.

0057's init section was wrong on all three of its claims. It said the host
needs FOUR things from an init; 0061 reduced that to one. It said every machine
the mesh targets already has systemd; Alpine does not, and it is the intended
first node. It said there is no second init to abstract over; there is now, and
the answer is still not an abstraction -- it is a four-line file per system.
What survives is the part that was always right: an init is not a dependency in
0041's sense, because it is not installed, it is what the machine already is.

0048 named Docker as the container runtime. It is now docker or podman,
detected rather than chosen -- because adoption keeps what a machine already
has, so naming one contradicted a rule already decided. That row is the only
one of the five that names two, and the record now says why.

0060 claimed the bundle is portable across operating systems. Its mechanism is;
its contents are not -- package names, unit names, service names all differ, so
an Arch host embeds an Arch bundle. That was my error, and it is the exact
confusion behind the question that found it.

The design layer had the same drift: 07 and 09 said "Docker" where they meant a
container runtime, 09 said systemd restarts the host after an upgrade when the
launcher does, and both install snippets assumed Arch. They now show Alpine and
Arch side by side, which makes the point better than prose did -- step 1
differs per system, step 2 never does.

Checked and NOT changed: 0047's "the vocabulary grows by one shape" is a claim
about the rate, not the count, and is still true. 0037 lists docker among tools
the host manages, which it does. 0041 says nothing about either.

03-DESIGN/01-to-be/09-the-node-lifecycle.md

@@ -12,6 +12,7 @@ decisions:
   - 02-DECISIONS/0051-the-enrolment-token-carries-the-mesh.md
   - 02-DECISIONS/0057-the-host-is-a-root-service-installed-as-a-package.md
   - 02-DECISIONS/0058-delivery-ends-in-a-declaration.md
+  - 02-DECISIONS/0060-the-host-is-built-per-operating-system.md
   - 02-DECISIONS/0061-the-host-asks-an-init-for-start-and-restart.md
 ---
 
@@ -51,17 +52,32 @@ same path, in an unusual order.
 
 ## unmanaged → hosted: installing
 
+In the machine's own idiom, because the package manager and the init file are the system's
+([ADR 0060](../../02-DECISIONS/0060-the-host-is-built-per-operating-system.md)):
+
 ```
+# Alpine — the intended first node
+apk add nox-mesh-host
+rc-update add nox-mesh-host && rc-service nox-mesh-host start
+
+# Arch
 pacman -S nox-mesh-host
 systemctl enable --now nox-mesh-host
 ```
 
+Two lines each, and the init file behind them is four
+([ADR 0061](../../02-DECISIONS/0061-the-host-asks-an-init-for-start-and-restart.md)) — it says
+*run the launcher at boot* and nothing else, so a third system is transcription rather than a
+port.
+
 Or, where there is no repository to install from:
 
 ```
-curl -fsSL https://<release>/mesh-host-<version>-x86_64.tar.gz | tar -xz -C /usr/local/bin
+curl -fsSL https://<release>/mesh-host-<system>-<version>-x86_64.tar.gz | tar -xz -C /usr/local/bin
 ```
 
+**The binary is per system as well as per architecture**, because two of its appliers are.
+
 **The tarball must never acquire a dependency**, because the mesh's own package repository is
 hosted on the mesh. Any route that needs the mesh in order to install the thing that joins the
 mesh is a circle — unusable on a first node, and unusable by whoever is repairing a mesh that is
@@ -159,8 +175,8 @@ mesh-control token issue
 nox-mesh-host enrol --token <token>
 ```
 
-Step 1 is the bootstrap from [`07-the-substrate.md`](07-the-substrate.md): Docker, then
-PostgreSQL, then the database, then the schema, then the control plane. It needs no identity
+Step 1 is the bootstrap from [`07-the-substrate.md`](07-the-substrate.md): a container runtime,
+then PostgreSQL, then the database, then the schema, then the control plane. It needs no identity
 because nothing is being asked of anyone — the host is applying a declaration it already
 carries, to the machine it is already on.
 
@@ -377,7 +393,9 @@ the test of whether this is really uniform.
 2  the host verifies the new binary runs   `nox-mesh-host version`, as a subprocess
 3  it finishes the apply and reports       never mid-way
 4  it exits 0                              having finished, not having been stopped
-5  systemd restarts it                     on the new binary
+5  the launcher starts it again            on the new binary — it supervises the host
+                                           rather than exec'ing it (ADR 0061), so this
+                                           needs nothing from the init
 6  the new host reconciles on start        trigger 1, confirming the machine still matches
 ```