109: a package registry seat is one per ecosystem, not one for all of them

Extends ADR 0075. Surfaced fixing builder's hand-faked package-registry
binding tonight: gitea's manifest declares the provision once with a single
npm-path, conflating what should be independently assignable per ecosystem
(npm/cargo/docker/...) the same way artifact-store and package-registry
were themselves split. Cited in 22-the-work-ahead.md's Phase 2, where the
target state this decision points at was already described a week ago.

Numbered 109, not 108: route-proxy's policy feature (mesh-controller PR
#58, merged today) already cites 'novox/hq ADR 0108' six times for its own
still-unwritten decision record — reserved but never committed. Renumbered
around it rather than colliding.

03-DESIGN/01-to-be/22-the-work-ahead.md

@@ -12,6 +12,7 @@ decisions:
   - 02-DECISIONS/0074-the-wire-is-specified-not-the-types.md
   - 02-DECISIONS/0075-two-stores-and-which-provides-what.md
   - 02-DECISIONS/0014-no-npm-workspace.md
+  - 02-DECISIONS/0109-a-package-registry-seat-is-one-per-ecosystem.md
 ---
 
 # The work ahead