Tools pipeline: issues 214, 215, 216, Go tools bundles served, and the runtime consumes for its modules (ADR 0193, 0198) #246

2026-10-03T21:16:08Z

mesh-admin commented

2026-10-03 21:16:08 +00:00

One integration of the branches built today (each commit kept), merged and tested together:

214 — a plan settles an asked build from the build records (on start and every 30 s), so the controller rebuilding itself no longer leaves its plan waiting for ever.
215 — a build at a commit never becomes the branch a module follows; a recorded commit is read as the default branch (heals existing records); a merge's plan names the modules it leaves out.
216 — registration refuses a bundle nothing loads, runs or unpacks, naming the field that would deliver it.
Go tools bundles served (ADR 0193) — loads may name a Go bundle's binary, defaulting to it when the module lists tools; the runtime is pointed at <bundle>/<binary>.
ADR 0198 — the node-tools principal is granted, for each carried module that consumes, that module's own consumer grants (EVENTS.<node>_<module>).
Tests follow the grants: a person may ask $SRV (ADR 0197); the resolver test mints dnsmasq's credential (issue 203's check).

211 is already on main (it rode in with #242); #243 and #244 are superseded by this.

Full suite passes against the current catalogue and mesh-host, and with a throwaway PostgreSQL — except TestTheResolverIsToldEveryMachineOnTheNetworkAndToldAgainWhenOneLeaves ("the resolver was not handed the machines"), which concerns the resolver records merged today by another session, not this change.

One integration of the branches built today (each commit kept), merged and tested together: - **214** — a plan settles an `asked` build from the build records (on start and every 30 s), so the controller rebuilding itself no longer leaves its plan waiting for ever. - **215** — a build at a commit never becomes the branch a module follows; a recorded commit is read as the default branch (heals existing records); a merge's plan names the modules it leaves out. - **216** — registration refuses a bundle nothing loads, runs or unpacks, naming the field that would deliver it. - **Go tools bundles served** (ADR 0193) — `loads` may name a Go bundle's binary, defaulting to it when the module lists tools; the runtime is pointed at `<bundle>/<binary>`. - **ADR 0198** — the node-tools principal is granted, for each carried module that consumes, that module's own consumer grants (`EVENTS.<node>_<module>`). - Tests follow the grants: a person may ask `$SRV` (ADR 0197); the resolver test mints dnsmasq's credential (issue 203's check). 211 is already on main (it rode in with #242); #243 and #244 are superseded by this. Full suite passes against the current catalogue and mesh-host, and with a throwaway PostgreSQL — except `TestTheResolverIsToldEveryMachineOnTheNetworkAndToldAgainWhenOneLeaves` ("the resolver was not handed the machines"), which concerns the resolver records merged today by another session, not this change.

mesh-admin added 11 commits 2026-10-03 21:16:08 +00:00

A plan settles an asked build from the build records (hq issue 214) d86baebe9a

A merge to the controller's own repository replaces the controller in its first tier; the build
that produced the new one was recorded, the plan never heard it, and it waited for ever with every
later plan behind it. The record is the fact: a build recorded after the ask is the tier's outcome,
whoever was listening when it came.

A commit is never a branch to follow (hq issue 215) 6784efae75

A build asked at a commit recorded that commit as the module's ref. Every merge after it failed to
match the module and its plan left it out without a word, and every plan that rebuilt it asked for
the same old commit again. Registration now keeps the branch the module followed (the default
branch for a new one); matching and re-asking read a recorded commit as the default branch, which
heals records already pinned this way; and a merge says which modules of its repository it leaves
out because they follow another branch.

A bundle nothing would deliver is refused at registration (hq issue 216) cf2bb3b87d

The composer delivers a bundle when the runtime loads from it, a resource names it, or it is the
runtime; one reached by none of them was built, recorded and pushed as success and was simply
absent. Seven modules' tools went missing that way. Refused at registration, naming the field that
would deliver it.

A Go tools bundle is served by its binary (hq ADR 0193) 8b016cc62b

A bundle compiled to a binary has no entrypoints, and loads had to name one, so a Go bundle could
not be served. Its binary is what the runtime starts: loads names the binary, derived when the
module lists tools, and the runtime is told the binary's path, delivered like any tools bundle.

The node's runtime reads the consumers of the modules it carries (hq ADR 0198) ac9c2d57be

A module's long-running code is a bundle the runtime launches, and the runtime is its bus: it binds
the module's own durable consumer — EVENTS, <node>_<module>, still the controller's to make from the
module's principal — and acknowledges what the module's code took. So the runtime principal is
granted, for each carried module that consumes, exactly what that module's own principal has for
its consumer: its info, its next message, its ack subject. Nothing is pushed to it; it pulls. ADR
0175's "consumes nothing" no longer holds. Memberships need nothing new: the consumer's name is
derived, as the module's own runtime derived it.

integrate: 214 980a0dee93

Merge remote-tracking branch 'origin/fix/issue-215-a-commit-is-never-a-branch-to-follow' into integrate 50cf253a43

Merge remote-tracking branch 'origin/fix/issue-216-a-bundle-nothing-delivers-is-refused' into integrate bf2da878a0

integrate: go served 518eeb7941

Merge remote-tracking branch 'origin/feat/0198-the-runtime-consumes-for-its-modules' into integrate 68af9eff44

Tests follow the grants and issue 203: a person may ask what answers; the resolver test mints its credential 74efe8e2e7

mesh-admin merged commit cadf74a176 into main

2026-10-03 21:16:14 +00:00

mesh-admin deleted branch fix/tools-pipeline-issues-214-216-and-0198

2026-10-03 21:16:14 +00:00

mesh-admin referenced this pull request

2026-10-03 21:30:37 +00:00