chore(docs): record JSON-RPC over NATS binding decision (ADR 0011) (#396)

Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>

Author: yordis

docs/adr/0002-rust-crate-boundaries.md

@@ -80,7 +80,7 @@ Use role suffixes only when they describe a real boundary:
   macros.
 - `-derive` for a procedural macro package whose public role is derive macros.
 - `-server` only for a package whose public role is serving a protocol; if it is
-  production-operated, place it according to the service rules in ADR 0001.
+  production-operated, place it according to the service rules in [ADR 0001](./0001-workspace-runtime-taxonomy.md).
 
 Avoid vague names such as `common`, `utils`, `helpers`, `core`, and `shared`.
 Those names usually mean the actual boundary has not been found yet. Prefer a

docs/adr/0004-protocol-and-transport-layering.md

@@ -111,7 +111,7 @@ Runtime configuration decides which transports start. Cargo features may make
 optional adapters available at compile time, but configuration decides what runs.
 
 Combining multiple transports in one binary is valid only when the binary is one
-operated workload, as defined in ADR 0003.
+operated workload, as defined in [ADR 0003](./0003-ai-protocol-transport-taxonomy.md).
 
 ## Package Boundary Rules
 
@@ -177,6 +177,6 @@ currently used to reach it.
 
 ## References
 
-- [ADR 0001: Workspace Runtime Taxonomy](/adr/0001-workspace-runtime-taxonomy)
-- [ADR 0002: Rust Crate Boundaries](/adr/0002-rust-crate-boundaries)
-- [ADR 0003: AI Protocol Transport Taxonomy](/adr/0003-ai-protocol-transport-taxonomy)
+- [ADR 0001: Workspace Runtime Taxonomy](./0001-workspace-runtime-taxonomy.md)
+- [ADR 0002: Rust Crate Boundaries](./0002-rust-crate-boundaries.md)
+- [ADR 0003: AI Protocol Transport Taxonomy](./0003-ai-protocol-transport-taxonomy.md)

docs/adr/0005-polyglot-workspace-layout.md

@@ -15,7 +15,7 @@ expected. Go or Python may be added later.
 
 The workspace layout should feel consistent across ecosystems without erasing
 important language-specific conventions. In particular, Rust should keep its
-Cargo-specific crate rules from ADR 0002.
+Cargo-specific crate rules from [ADR 0002](./0002-rust-crate-boundaries.md).
 
 ## Decision
 
@@ -84,7 +84,7 @@ rsworkspace/
   xtask/        Rust workspace automation, if a dedicated automation crate exists
 ```
 
-Rust reusable packages use `crates/`, not `packages/`. ADR 0002 remains the
+Rust reusable packages use `crates/`, not `packages/`. [ADR 0002](./0002-rust-crate-boundaries.md) remains the
 source of truth for Rust crate naming, crate granularity, feature flags,
 transport adapter packages, SDK names, and procedural macro packages.
 
@@ -261,7 +261,7 @@ Use protocol/client/SDK packages instead.
 
 The monorepo gets consistent concepts across languages:
 
-- Rust uses `crates/` because Cargo and ADR 0002 are Rust-specific.
+- Rust uses `crates/` because Cargo and [ADR 0002](./0002-rust-crate-boundaries.md) are Rust-specific.
 - TypeScript, Go, and Python use `packages/` for reusable libraries.
 - `apps/`, `services/`, `cli/`, `sdks/`, and `examples/` mean the same thing in
   every language workspace.
@@ -271,7 +271,7 @@ The monorepo gets consistent concepts across languages:
 
 ## References
 
-- [ADR 0001: Workspace Runtime Taxonomy](/adr/0001-workspace-runtime-taxonomy)
-- [ADR 0002: Rust Crate Boundaries](/adr/0002-rust-crate-boundaries)
-- [ADR 0003: AI Protocol Transport Taxonomy](/adr/0003-ai-protocol-transport-taxonomy)
-- [ADR 0004: Protocol and Transport Layering](/adr/0004-protocol-and-transport-layering)
+- [ADR 0001: Workspace Runtime Taxonomy](./0001-workspace-runtime-taxonomy.md)
+- [ADR 0002: Rust Crate Boundaries](./0002-rust-crate-boundaries.md)
+- [ADR 0003: AI Protocol Transport Taxonomy](./0003-ai-protocol-transport-taxonomy.md)
+- [ADR 0004: Protocol and Transport Layering](./0004-protocol-and-transport-layering.md)

docs/adr/0006-helpers-naming.md

@@ -44,4 +44,4 @@ decision to justify vague package, module, file, type, or function names.
 ## References
 
 - [Straw Hat ADR 1146361044: Helper vs Util](https://straw-hat-team.github.io/adr/adrs/1146361044/README.html)
-- [ADR 0002: Rust Crate Boundaries](/adr/0002-rust-crate-boundaries)
+- [ADR 0002: Rust Crate Boundaries](./0002-rust-crate-boundaries.md)

docs/adr/0008-opentelemetry-observability.md

@@ -14,8 +14,8 @@ services, apps, CLIs, SDKs, and workspace automation. Without one default, logs,
 metrics, and traces can drift into vendor-specific libraries, incompatible
 attribute names, and uncorrelated runtime views.
 
-ADR 0001 already treats OpenTelemetry service identity as part of a service
-boundary. ADR 0002 names shared observability setup as the responsibility of a
+[ADR 0001](./0001-workspace-runtime-taxonomy.md) already treats OpenTelemetry service identity as part of a service
+boundary. [ADR 0002](./0002-rust-crate-boundaries.md) names shared observability setup as the responsibility of a
 dedicated reusable package such as `trogon-telemetry`.
 
 OpenTelemetry is the standard observability vocabulary that covers traces,
@@ -96,8 +96,8 @@ package, service, or deployment boundary that owns it.
 
 ## References
 
-- [ADR 0001: Workspace Runtime Taxonomy](/adr/0001-workspace-runtime-taxonomy)
-- [ADR 0002: Rust Crate Boundaries](/adr/0002-rust-crate-boundaries)
+- [ADR 0001: Workspace Runtime Taxonomy](./0001-workspace-runtime-taxonomy.md)
+- [ADR 0002: Rust Crate Boundaries](./0002-rust-crate-boundaries.md)
 - [OpenTelemetry Signals](https://opentelemetry.io/docs/concepts/signals/)
 - [OpenTelemetry Logs](https://opentelemetry.io/docs/concepts/signals/logs/)
 - [OpenTelemetry Metrics](https://opentelemetry.io/docs/concepts/signals/metrics/)

docs/adr/0009-protocol-buffers-wire-contracts.md

@@ -10,9 +10,9 @@ date: 2026-06-08
 ## Context
 
 The repository already uses Protocol Buffers for generated protocol packages and
-scheduler message contracts. ADR 0003 prefers NATS-backed internal boundaries
+scheduler message contracts. [ADR 0003](./0003-ai-protocol-transport-taxonomy.md) prefers NATS-backed internal boundaries
 when both sides are first-party runtime components, and prefers ConnectRPC over
-direct gRPC after a first-party service API surface is necessary. ADR 0005 names
+direct gRPC after a first-party service API surface is necessary. [ADR 0005](./0005-polyglot-workspace-layout.md) names
 Protocol Buffers as the preferred cross-language contract, with NATS-backed
 messages for internal paths and ConnectRPC for service APIs.
 
@@ -48,7 +48,7 @@ Use Protocol Buffers by default for:
 
 NATS-backed internal messages can use the same Protocol Buffers schema governance
 without becoming ConnectRPC or gRPC services. Choose ConnectRPC or direct gRPC for
-the API surface only after ADR 0003 rules out the internal backbone as the right
+the API surface only after [ADR 0003](./0003-ai-protocol-transport-taxonomy.md) rules out the internal backbone as the right
 boundary.
 
 Schemaless storage does not remove the need for a schema. When a KV store,
@@ -101,9 +101,9 @@ Valid exceptions include:
 
 - MCP, ACP, JSON-RPC, webhook, or third-party API surfaces with protocol-defined
   JSON contracts.
-- Human-edited configuration files, which follow ADR 0007.
-- OpenAPI or REST-like HTTP contracts allowed by ADR 0003.
-- Logs, metrics, traces, and telemetry export paths governed by ADR 0008 or by a
+- Human-edited configuration files, which follow [ADR 0007](./0007-configuration-sources.md).
+- OpenAPI or REST-like HTTP contracts allowed by [ADR 0003](./0003-ai-protocol-transport-taxonomy.md).
+- Logs, metrics, traces, and telemetry export paths governed by [ADR 0008](./0008-opentelemetry-observability.md) or by a
   deployment system.
 - Plain text, Markdown, HTML, or binary file content where the payload format is
   the product data rather than the envelope contract.
@@ -128,7 +128,7 @@ the reason near the boundary that owns the format.
 
 ## References
 
-- [ADR 0003: AI Protocol Transport Taxonomy](/adr/0003-ai-protocol-transport-taxonomy)
-- [ADR 0005: Polyglot Workspace Layout](/adr/0005-polyglot-workspace-layout)
-- [ADR 0007: Configuration Sources](/adr/0007-configuration-sources)
-- [ADR 0008: OpenTelemetry Observability](/adr/0008-opentelemetry-observability)
+- [ADR 0003: AI Protocol Transport Taxonomy](./0003-ai-protocol-transport-taxonomy.md)
+- [ADR 0005: Polyglot Workspace Layout](./0005-polyglot-workspace-layout.md)
+- [ADR 0007: Configuration Sources](./0007-configuration-sources.md)
+- [ADR 0008: OpenTelemetry Observability](./0008-opentelemetry-observability.md)

docs/adr/0010-testcontainers-for-infrastructure-tests.md

@@ -106,7 +106,7 @@ reason near the test or package boundary that owns the decision.
 
 ## References
 
-- [ADR 0003: AI Protocol Transport Taxonomy](/adr/0003-ai-protocol-transport-taxonomy)
-- [ADR 0004: Protocol and Transport Layering](/adr/0004-protocol-and-transport-layering)
-- [ADR 0009: Protocol Buffers Wire Contracts](/adr/0009-protocol-buffers-wire-contracts)
+- [ADR 0003: AI Protocol Transport Taxonomy](./0003-ai-protocol-transport-taxonomy.md)
+- [ADR 0004: Protocol and Transport Layering](./0004-protocol-and-transport-layering.md)
+- [ADR 0009: Protocol Buffers Wire Contracts](./0009-protocol-buffers-wire-contracts.md)
 - [Testcontainers](https://testcontainers.com/)