The bus is the mesh's centre, not a transport that replaced one

Two things. A paragraph from the superseded 0117 survived beside the 0119
correction that reversed it, so §5 said both that the amqp interface
retires and that it does not. The stale one is gone.

And the framing. §1 opened with "the bus carries five kinds of traffic
today, and this design keeps the five", with a column mapping each to the
queue it used to be — which describes the mesh's nervous system as a port
of something that did a fraction of this. It now says what the bus is: a
role addressable without knowing its holder, the mesh's own state, work
that queues until somebody can do it, and permissions derived from what a
module declared. Conditions, observation and a person's client land there
too as they are built.

Glossary gains `bus` and `the deprecated broker`, with a note on why not to
say "compatibility broker" or name it after a protocol — the second invites
exactly the backwards framing this commit removes.

03-DESIGN/01-to-be/29-what-a-module-declares.md

@@ -302,7 +302,7 @@ The mesh's own bus is **`mesh-bus`**, delivered by the `mesh-broker` seat and an
 controller — because the bus's accounts are configuration rather than something a provisioner
 creates, so there is no provisioner process in the path and nothing waiting on a bus account in
 order to make bus accounts. A module that runs a NATS server of its own and offers it as a
-backing service provides **`nats`**, exactly as the AMQP broker provides `amqp`
+backing service provides **`nats`**, exactly as the deprecated broker provides `amqp`
 ([ADR 0119](../../02-DECISIONS/0119-amqp-is-a-provision-not-the-bus.md)).
 
 They are never the same name. A manifest saying `nats` could otherwise mean either the mesh's