Refs name the registry; lavinmq's runtime runs its provisioner (042/048/061) #26

Merged
jschoubben merged 2 commits from feat/refs-name-the-registry into main 2026-09-17 23:00:43 +00:00
2 Commits
Author SHA1 Message Date
jschoubben 1891b09c65 lavinmq's runtime container runs its provisioner
The runtime container named no command, so it ran the image default —
the tool host — and the provisioner entrypoint compiled beside it never
ran anywhere: no vhost was ever minted, while the grants sat applied in
its mounted directory. postgres already names its provisioner in args;
lavinmq now does the same. Surfaced by the built-store-cross-node bed,
run 9 — the first bed to reach the vhost assertion honestly.
2026-09-17 23:54:56 +02:00
jschoubben 2dab3069d2 The builder names the registry by the binding again (ADR 0082)
The one-line change e0c9219 parked "until there is a certificate" returns — with the
overlay recorded as the registry's transport security and every node's runtime told the
store speaks plain HTTP, a reference under the provider's internal name is one every
machine can pull. References minted at genesis stay loopback and are valid where they
matter, on the machine that made them.

https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx
2026-09-17 23:05:25 +02:00