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.
2026-09-24 15:52:45 +02:00
parent f10dce4f9e
commit 402b798ab6
3 changed files with 5 additions and 5 deletions
@@ -1,8 +1,8 @@
 ---
-status: open
+status: resolved
 opened: 2026-09-22
-located-in: []
-fixed-by:
+located-in: [mesh-catalog]
+fixed-by: mesh-catalog — the 11 not-defensible modules (de-spiegel, gitea, hello-web, mailu, mssql, n8n, novox.be, only-office, photos, photos-eef, photos-filip) had their hardcoded machine-side port mapping stripped to the bare software port, letting ADR 0038's existing assignment machinery (internal/inventory/ports.go's PortFor, declaration.go's publishedOn) assign it as designed. postgres, lavinmq, distribution (foundation, genesis-rewritten) and unifi (protocol-fixed) were left as-is — the two defensible kinds this report names.
 amended-design:
 ---