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/25-the-bus-on-nats.md

@@ -10,7 +10,7 @@ code:
 updated: 2026-09-26
 decisions:
   - 02-DECISIONS/0106-the-bus-is-nats.md
-  - 02-DECISIONS/0115-the-bus-is-built-in-five-steps.md
+  - 02-DECISIONS/0116-the-bus-is-built-in-five-steps.md
   - 02-DECISIONS/0074-the-wire-is-specified-not-the-types.md
   - 02-DECISIONS/0079-the-foundation-seats-are-named-after-their-servers.md
   - 02-DECISIONS/0100-a-node-in-use-is-adopted-before-it-is-converged.md
@@ -237,7 +237,7 @@ message body. A module built today runs on the new runtime without a rebuild —
 ADR 0039, and it is in §10.
 
 **The wire underneath it changes completely, and that is a specification, not an implementation
-detail.** Revision, second review ([ADR 0115](../../02-DECISIONS/0115-the-bus-is-built-in-five-steps.md)):
+detail.** Revision, second review ([ADR 0116](../../02-DECISIONS/0116-the-bus-is-built-in-five-steps.md)):
 an earlier draft of this section said "nothing new" and stopped there, which read as though the
 change were contained inside the runtime. It is not.
 [ADR 0074](../../02-DECISIONS/0074-the-wire-is-specified-not-the-types.md) settled that an SDK is an
@@ -258,7 +258,7 @@ nothing is added to it here.
 ## 9. Moving from the bus the mesh has: five steps
 
 Per ADR 0106 the bus moves once. Per
-[ADR 0115](../../02-DECISIONS/0115-the-bus-is-built-in-five-steps.md) the *build* is five steps,
+[ADR 0116](../../02-DECISIONS/0116-the-bus-is-built-in-five-steps.md) the *build* is five steps,
 each ending at something §10 proves, so that no part of this waits on the whole of it. Dividing the
 build does not divide the bus: steps 1 to 4 leave every node on AMQP, and step 5 is still one
 rollout.
@@ -382,7 +382,7 @@ to mapping the sdk contract onto subjects exactly as §8 says.
 
 ## 11. Open, for the review
 
-**Closed by the second revision** (2026-09-26, [ADR 0115](../../02-DECISIONS/0115-the-bus-is-built-in-five-steps.md)):
+**Closed by the second revision** (2026-09-26, [ADR 0116](../../02-DECISIONS/0116-the-bus-is-built-in-five-steps.md)):
 the build was one undivided item (§9 is now five steps, each with its own bed in §10); there was no
 adoption path for a mesh already running (§9 step 2); and §8 said a module sees "nothing new"
 without distinguishing the sdk's contract, which does not change, from the specified wire, which