Accept ADR 0038; close issue 091

The decision (the mesh assigns a container's machine-side port; a module
says only what it needs) was proposed 2026-09-01, and the machinery
already implements it in full -- internal/inventory/ports.go's PortFor,
declaration.go's publishedOn. What was missing was the catalogue actually
complying: 14 of 46 modules baked a machine-side number into their own
manifest anyway. mesh-catalog PR fixes 11 of them (the two defensible
kinds -- foundation, protocol-fixed -- are left alone, per the issue's own
categories). Accepting the decision now that it's actually enforced, and
closing the issue it was blocking.

Checks pass.

02-DECISIONS/README.md

@@ -132,7 +132,7 @@ python3 00-META/checks/index.py            fail if stale
 - **0026** — [The mesh has a session of its own, and it is the node session's mechanism](0026-the-mesh-has-a-session-of-its-own.md)
 - **0027** — [A provision names what the consumer is coupled to, not the role it plays](0027-a-provision-names-what-the-consumer-is-coupled-to.md)
 - **0035** — [One implementation, several surfaces, and what that costs](0035-one-implementation-several-surfaces.md)
-- **0038** — [The mesh assigns the port, and a module does not care](0038-the-mesh-assigns-the-port.md)  *(proposed)*
+- **0038** — [The mesh assigns the port, and a module does not care](0038-the-mesh-assigns-the-port.md)
 - **0040** — [What a module is](0040-what-a-module-is.md)
 - **0041** — [Events are a relationship, the lighter sibling of provisioning](0041-events-are-a-relationship.md)
 - **0042** — [The shape of an event on the wire](0042-the-shape-of-an-event-on-the-wire.md)