4 Commits

Include renames

Author	SHA1	Message	Date
jochen	ed43d65bf3	Lay out the publishing test's return as every gofmt agrees, so the build seat's check passes ... The toolchain the build seat runs merge-check.sh in (Go 1.26) and a newer local Go format a return of several multi-line composite literals differently; the seat's is the one that judges, and it failed every pull request on this file (novox/hq issue 283).	2026-10-07 01:29:06 +02:00
jschoubben	5dd439df50	inspect by kind, not the ambiguous bare form — a same-named network stops a container from ever being found ... docker inspect <name> resolves across every object kind, not just containers. A module regularly names a network the same as the container that joins it (keycloak does this today, ordinarily) — so when the container does not exist yet but the same-named network already does, the bare form answers with the network's JSON instead of reporting the container absent, and the template these callers use (.State.Running) fails to execute against it entirely. Live on novox tonight: minio's LB container, named the same as its network ("minio"), could never be created — every apply crashed on "the container runtime could not say whether minio is here", stuck since first push, because the check itself never got a clean answer. Fixed at every call site asking a container's state by name (containerState, inspectFound, NamesFree, raiseGiteaServer, containerRunning) by scoping to `docker container inspect`, matching the type-scoped form this codebase already uses correctly for networks, volumes and images elsewhere. Also scoped the one image inspect that was still bare (publish.go), for the same reason. mesh-host runs as a host-level service (nox-mesh-host.service), not a Docker module — merging this does not redeploy it. The live novox failure persists until the service itself is rebuilt and updated.	2026-09-24 19:50:16 +02:00
jschoubben	121367319d	Rename mesh-control -> mesh-controller, substrate -> foundation ... One name per thing, per the HQ glossary: the module/container/image/binary/repo becomes mesh-controller, the seat the-controller, and the store+broker pair the foundation (embedded base bundles, default template and example lock renamed with their go:embed directives). No behaviour change — a pure vocabulary rename. Claude-Session: https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx	2026-09-16 18:40:40 +02:00
jschoubben	f534cf8b42	bootstrap: the rest of the pivot — enrol, registry, publish, reinstall, retire ... Steps 6 to 10, which turn a substrate into a mesh that can maintain itself (novox/hq ADR 0067). 6 enrol a node record, a token, `mesh-host enrol`, and the host agent running. Proved by the mesh having HEARD from the node, not by a process existing: a host that cannot reach the broker looks exactly like a successful install until the first push applies nothing. 7 registry the module that gives this mesh an image store, registered from a --catalog checkout, assigned and pushed. Its image is upstream and never built (04-ISSUES/029) — a placeholder digest there is refused. Verified by asking `/v2/`, because a container that is up is not a registry that serves. 8 publish the carried image pushed into that registry, which assigns it the first manifest digest it has ever had. This is the hinge: without it the mesh works and can never upgrade itself. 9 control the control plane registered as an ordinary module pinned to that digest, with the substrate's own store connections delivered through `secret accept` — read out of the bundle that made them, because the mesh cannot invent a credential that predates it. 10 retire the temporary control plane dropped from the bundle and removed by the host's ordinary removal pass. Every step asks before it acts and reports "already done". No step leaves the machine without a control plane: steps 9 and 10 overlap deliberately, and two stateless control planes are untidy rather than broken. mesh-control's `internal/builder`.PublishImage is mirrored rather than imported — tier 0 depends on nothing that must be installed first — with one correction: the digest is chosen from RepoDigests by repository instead of taken as element zero, so an image pushed to two registries cannot silently pin this mesh to the wrong one. Claude-Session: https://claude.ai/code/session_01LrgweAeERJYBg88c5cKDzF	2026-09-10 23:59:57 +02:00