Registry milestone: mesh-host (issue 1966) #209
Assignees
agent-ace
agent-g14
agent-novox
agent-shanks
jschoubben
mesh-tools
miel.truyen
nox-agent
Clear assignees
agent-ace
agent-g14
agent-novox
agent-shanks
jschoubben
mesh-tools
miel.truyen
nox-agent
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: novox/mesh-host#209
Reference in New Issue
Block a user
The registry milestone (issue 1966; ADR 0605-0636 as hq's designs name them), taken in onto its trunks after milestone 47/B0 as milestone 47/G's first step (design 47; issue 1921 notes 54-61).
One delivery group, branch feat/registry-milestone in mesh-sdk, mesh-contracts, mesh-delivery, mesh-host, mesh-tools, mesh-catalog and mesh-networking: one check, one Approve. No member names another's version (ADR 0573); every mesh package is required at the zero version.
This member: eight dead copies of seats' verb lists removed, with a guard; the node-engine's input says why each module is held; the composer overrules a hold the case's own verdict accepts, naming a build still awaited; the composition verb says why a module is held.
The registry's reviewed heads (three rounds, 2026-11-04 to 11-06) were never pushed until now; the check of 068b7d23cf1a judged the heads of 2026-11-04. The trunk step was prepared and reviewed in three rounds (2026-11-07): the merge resolutions keep B0's facts and checking-program rules and the registry's generated types; every check composes with the composer at the node-engine member's head, else its trunk; a module the running indexer refuses but the check's own validator accepts is composed and named in the verdict with its build awaited, never passed silently; the checking program answers only new or changed seat definitions when given the reader's digests, and without them (the running B0 checker) only each seat's own description, 171 KB under the 256 KiB bound.
Rules bent, said here: mesh-delivery stays over its test budget (662 unit, 68 integration; was 675 and 68) and mesh-host over unit (1745; was 1746), falling. Out of this step, noted on issue 1921: three asks carry the whole seat list (~430 KB) bounded only by the bus's 1 MiB; the trunk case of the manifest validator is given the heads' seats.
After check 616c42434ac2 (issue 1921 notes 63-64), reviewed again: no change in this member.
After check 8a80e8e86858 (issue 1921 notes 66-67), reviewed again: mesh-catalog ignores the new check's program and mesh-build-go's test workspace lays what the composer requires; mesh-host composes from the change's manifest wherever a node's build was made of another (by its manifest digest, or by its contract where the running node-engine names none), naming each such module as not judged, and a consumer beside a held provider is not served the provider's own names raw; mesh-delivery's checker keeps each composition request it sends (state compositions, 3 days) with the read tool checker_composition_requests.
After check c5d32074c945 (issue 1921 notes 69-75), reviewed again: mesh-catalog marks lab moved (lead-47@shanks) and takes in main's mesh-catalog #624 (the fetch downloads each placed sibling's module graph, delivered ahead); mesh-delivery's checker test expects its eleventh state, and it takes in main's #163 (the indexer's take-in waits end, lead-47@shanks) and #164 (a pull request's check composes only after the change's own builds end), both delivered ahead; mesh-host gives the held try's words when it is refused too. Rule bent, said here: mesh-build-go has 52 integration tests, over its budget of 50 (the trunk 49).
Reviewed-by: mesh-code-reviewer@shanks at
cb7a444a56https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i
Delivery
novox/mesh-host@cb7a444a5634— merged since 2026-11-07T14:19:53ZSource — source.main moved to novox/mesh-host@70e70eda5a. Whether it reached the machines is
mesh-delivery-view's, derived fromsource.main, the wants and the haves.Group
feat/registry-milestone: novox/mesh-catalog@67d9ccb1d4, novox/mesh-contracts@b77560786a, novox/mesh-delivery@4735fc0b5f, novox/mesh-host@cb7a444a56, novox/mesh-networking@9ee0ffe3c0, novox/mesh-sdk@d932546703, novox/mesh-tools@6c05e42626Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition of this change up to its merge:git log --notes=mesh-plan.mesh-delivery: the operator's Approve of this pull request's merge into main is ended: a head it covers moved on: the heads it covers are no longer the group's heads. Nothing is merged on it. The operator is asked again once the checks pass at the new head.
mesh-delivery: not merged. The merge of this pull request into main at
32c5df952cwas declined: the operator, via telegram (user id verified), chose Decline. A new head asks the operator again.A case's verdicts are the checker's account of the indexer's modules values, not the indexer's kept values: the trunk's checker writes them with version 0 and no judge, so the kept value's strict reader refused every one and the group try failed composition on all four nodes ("the verdict of f1-circuits is not one: ... version 0"). The composer now takes version 0 (or none) and keys.Version, its judge optional, and still refuses a later version, a value that does not decode and an unknown state. The bus reader of kept verdicts stays strict. Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7imesh-delivery: the operator's Approve of this pull request's merge into main is ended: a head it covers moved on: the heads it covers are no longer the group's heads. Nothing is merged on it. The operator is asked again once the checks pass at the new head.
The provider held on its machine is composed apart, so no module of the composed set serves the provision; its manifest's served values reached the consumer's binding raw and the binding refused the consumer for a ${bound:route:name-web} it does not require (the group check of 8a80e8e86858 on novox, mesh-build-node beside a held gitea). Each such key is now left out and said on the need, as a provider elsewhere leaves it out (ADR 0346). Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7imesh-delivery: the operator's Approve of this pull request's merge into main is ended: a head it covers moved on: the heads it covers are no longer the group's heads. Nothing is merged on it. The operator is asked again once the checks pass at the new head.
mesh-delivery: not merged. The merge of this pull request into main at
53addd73c3was declined: the operator, via telegram (user id verified), chose Decline. A new head asks the operator again.