Renumber to 0116: another record took 0115 on main

PR #133 landed a different 0115 while this branch was open. The bus record
is now 0116, with every citation in designs 19, 25, 28 and the index
following it.

Note: cycle.py and records.py both fail on main as merged, on that record —
nothing cites it, and it rests on 0112, which is still proposed. Both
pre-date this branch and are left for their own change.

03-DESIGN/01-to-be/28-building-the-bus.md

@@ -4,7 +4,7 @@ status: proposed
 code: []
 updated: 2026-09-26
 decisions:
-  - 02-DECISIONS/0115-the-bus-is-built-in-five-steps.md
+  - 02-DECISIONS/0116-the-bus-is-built-in-five-steps.md
   - 02-DECISIONS/0106-the-bus-is-nats.md
   - 02-DECISIONS/0074-the-wire-is-specified-not-the-types.md
   - 02-DECISIONS/0079-the-foundation-seats-are-named-after-their-servers.md
@@ -14,7 +14,7 @@ decisions:
 
 # 28. Building the bus
 
-**The work of [ADR 0115](../../02-DECISIONS/0115-the-bus-is-built-in-five-steps.md)'s five steps,
+**The work of [ADR 0116](../../02-DECISIONS/0116-the-bus-is-built-in-five-steps.md)'s five steps,
 in the order its dependencies allow, with what each ends at.**
 [Design 25](25-the-bus-on-nats.md) is the architecture and stays the authority on *what is built*;
 this document holds only the order, the sizes and the proofs, and it is wrong the moment it
@@ -65,11 +65,11 @@ mirror rather than share (the host imports nothing, by
 host's link, and the runtime's client. And a search for conformance fixtures finds none anywhere in
 the four repositories: design 22's Phase 1.2 — the suite — has not been built.
 
-> **This corrected the record.** ADR 0115 said step 3's fixtures were *recaptured* on NATS. There
+> **This corrected the record.** ADR 0116 said step 3's fixtures were *recaptured* on NATS. There
 > is nothing to recapture, so step 3 **builds** the suite, and its first job is to pin the wire the
 > mesh has before changing it — a suite written only against the new bus certifies whatever the new
 > bus happens to do. A fact went stale while the decision stood, which is a **progressive insight**
-> ([`02-DECISIONS/README.md`](../../02-DECISIONS/README.md)): it is marked and dated in ADR 0115
+> ([`02-DECISIONS/README.md`](../../02-DECISIONS/README.md)): it is marked and dated in ADR 0116
 > itself rather than left to be discovered here.
 
 ## The order the work actually allows
@@ -91,12 +91,12 @@ otherwise would put two beds where they cannot run.** Three edges decide it:
 So step 1's bed proves *the server, from genesis, configured* — not a mesh living on it. The full
 genesis bed is step 4's, where it can first run.
 
-> **This corrected the record too.** ADR 0115 first attributed "a mesh raised on NATS from genesis"
+> **This corrected the record too.** ADR 0116 first attributed "a mesh raised on NATS from genesis"
 > to step 1. That bed cannot run until the links exist, and a step whose proof cannot run is the
 > exact failure the record was written to prevent — so step 1 now ends at the server standing,
 > correctly configured and carrying nothing, and the full bed is named under step 4. The five
 > steps, their names, their order and the single rollout are unchanged; only where two beds run has
-> moved. Marked and dated in ADR 0115 as a progressive insight, with what the record said before.
+> moved. Marked and dated in ADR 0116 as a progressive insight, with what the record said before.
 
 ```
 step 1  module, genesis places it        ──┐