Research 014: fix the reference to ADR 0039

01-RESEARCH/014-the-bus-on-nats/00-overview.md

@@ -4,7 +4,7 @@ initiated: 2026-09-23
 touches:
   - 02-DECISIONS/0002-nodes-communicate-over-a-broker.md
   - 02-DECISIONS/0033-the-substrate-is-a-store-and-a-broker.md
-  - 02-DECISIONS/0039-the-broker-client-lives-in-the-runtime-not-the-sdk.md
+  - 02-DECISIONS/0039-what-the-sdk-holds-and-refuses.md
   - 02-DECISIONS/0041-events-are-a-relationship.md
   - 02-DECISIONS/0042-the-shape-of-an-event-on-the-wire.md
   - 02-DECISIONS/0043-a-module-broker-account-is-scoped-by-emits-and-consumes.md
@@ -30,7 +30,7 @@ places, and it is swapped once.
 **Where AMQP is spoken** (non-test files): the controller's `internal/link` (5 files, ~2.4k lines
 with tests) and the builder's main; the host's `internal/link` (~1.5k); the tool runtime's
 `broker-amqp.ts` (~600 with its main). **The sdk speaks none** — its `Broker` is `request`,
-`handle`, `publish`, `subscribe`, `close` ([ADR 0039](../../02-DECISIONS/0039-the-broker-client-lives-in-the-runtime-not-the-sdk.md)
+`handle`, `publish`, `subscribe`, `close` ([ADR 0039](../../02-DECISIONS/0039-what-the-sdk-holds-and-refuses.md)
 put the client in the runtime for exactly this). **Every module's tools and events go through the
 sdk**; one module (`amqp-ping`, a probe) talks AMQP on purpose.