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.

02-DECISIONS/0060-the-host-is-built-per-operating-system.md

@@ -54,8 +54,15 @@ arrive together, as one decision somebody made when they installed the operating
 ### Almost all of it is shared
 
 Not a rewrite per operating system. The declaration vocabulary, the store, the apply loop, the
-read-back discipline, the refusal model, the bundle and the link are all portable. **What differs
-is two appliers**, and the rest is compiled around them.
+read-back discipline, the refusal model and the link are all portable. **What differs is two
+appliers**, and the rest is compiled around them.
+
+**The bundle is the exception, and an earlier version of this record wrongly listed it as
+portable.** Its *mechanism* is — one embedded declaration, applied with no mesh present. Its
+*contents* are not: package names, unit names and service names all differ, so an Arch host
+embeds an Arch bundle and an Alpine host an Alpine one. That is the same thing this record says
+about package names one section down, and missing it here is what made the distinction hard to
+see.
 
 ### The control plane names the package, because the host does not decide