Milestone 47 G: mesh-delivery's part of the one release #214
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-delivery#214
Reference in New Issue
Block a user
Design 47 milestone G, one release in seven repositories: the delivery group feat/47-G-join12 (issue 1966; ADR 0666, ADR 0667). It replaces group feat/47-G-join11, which the delivery gate closed after merging only 3 of its members this morning. The app manifests G needs went first as group feat/47-G-apps (merged 13:56 CET). G's base branches are all main, so the gate can merge the whole group on one Approve. After the merge the delivery is ordered from the graph.
This branch: G
8899b62cwith main merged in (reader release 3,ff9f089d), §372 with A-350 and A-351 (8d40d909: the catalog's version fill starts above every number the builder gave), and A-352 with ADR 0614 §5 (bc8126ef: the bus-state rule counts a bus module's running build while its newer build waits for the operator's yes).The check cannot judge G on today's checker, because it asks for tagged versions of the contracts' packages that only its own build can number (issue 1373). Local evidence at these heads instead: go vet, with and without the integration tag, over 224 modules (clean except mesh-build-go's intentionally broken test fixture); the tests and integration tests of the indexer and the grants part pass; G's manifest validator accepts 193 of 193 manifests; the second dry run against what is live finds no refusal caused by G.
Reviewed-by: mesh-code-reviewer@shanks (for lead-47@shanks) at
bc8126efefhttps://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
Design 47 at b229f5c4, *A module's registration*, lines 482-485 ("No part fixes a name": every module name a part needs is read from the catalog graph; ADR 0666 §5): the validator kept the build modules' toolchain streams (toolchains-go, toolchains-node) until they move by the modules' names. It now keeps them for the module that claims node-build-go or node-build-node, whichever module that is. The other entries of the list, the node-engine's module (engineModule) and the indexer's own toolchain watch are not in this commit. Rows in TestRulesBus/TwoModulesCannotDeclareOneStream (fail without it). Issue 1966. Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ Builds: design 47 G §364, §428, §535The entry's artifact gains package {ecosystem, name} (the seat mesh-catalog's definition, regenerated), read at take-in from the revision's own files (go.mod, package.json) through the forge; the validator's PackageNameProblems refuses every module sharing one name in one ecosystem, naming them, in the trunk's judge pass. An image's name is not written: the design does not say what it is. Builds: design 47 G §676, §491, §478, §504, §412 Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZEach item of dependencies is {kind, part, version, digest}: kind 1 a resolved package's artifact reference, kind 3 the toolchain's part. Its field artifact is part. Builds: design 47 G §673, §466, §374 Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZThe seat list's build seat per artifact (language or kind), a kept call <seat>.steps with {module, artifact, fingerprint, fetch}, and the finding call-unanswered (scope call, id <seat>.steps) after five minutes, cleared on an answer. Builds: design 47 G §704 Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4hThe manifest gains the file resource toolchain-wait (content ${config:toolchain-wait-minutes}) and names its path in MESH_BUILDER_TOOLCHAIN_WAIT_FILE; main.go's toolchainWaitOf reads it. Builds: design 47 G §672, A-71 (G-20) Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4hThe indexer asks the seat mesh-module-assigner's verb placement (input {module}, answer {placements: [{branch, nodes}]}, A-62) before an unwatch is proposed and refuses one whose branch a placement names, with the reason placed (new in the seat mesh-catalog's contract) naming the placement; its manifest invokes the verb. Builds: design 47 G §704 (unwatch), A-62 Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4hThe validator refused the manifest: a process's env is not filled from config. As A-112 says, a process reads each setting from a file with the content ${config:<key>}, read at its start (the builder's form); a missing or empty file is the default, a content that is no positive whole number stops the start, naming the file. Builds: design 47 G §633, §706, A-112 Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4hPins.catalog is a list of {branch, revision} in the mesh-delivery seat's definition (revisions are numbered per watched branch), the Go and TypeScript contracts regenerated, the fixtures follow. Builds: design 47 G §579, A-169, A-171 Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4hrunningalone cbfea2f961ongains the valuerunner version9fd2066711The entry's manifest is read by the second reader release (RR2-4), and an invoked verb given as {verb, fields} puts the fields in its edge's `why`. Builds: design 47 G §558 (A-208) Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4hThe seat whose definition delivers a requirement, among those the entry's catalog graph revision names, is resolved first: its holder from the placements' holds, as seat-holders keeps them; a delivering seat no placement holds holds the entry, naming the seat. A hold now names the requirement, the seat and each candidate {node, module}; an optional requirement nothing provides is left absent. The catalog entry gains contributes, filled by the indexer, and requires names every requirement as Wants lists them, optional ones included (the module graph and the assigner's halves leave the optional ones out by the entry's manifest). A contributed requirement gives a contribution edge to the same provider. Builds: design 47 G §708, §709, §357; lead answers A-167, A-229 Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4hThe view's process hears wait-held and wait-ended of every part (seats and modules; waits.go, manifest consumes) and keeps them in its state waits under owner.step.node.module (viewstate/waits.go); view_tiers reads them through the tools bundle and names each module's waits in the sayer's own words, {owner, step, node, on, bound, since, words} (tiers.go waitsHeld), beside the indexer's pending revisions as the seat mesh-catalog's step take-in. No state of another module is read for a tier's waits. Builds: design 47 G §512, §376, §498, A-242The take-in puts the validation's run ask and ends there; the revision's newest pending value keeps validation {ask, asked, input, seq, try, failed, accepted}. The build seat's step-ended of that ask resumes it: accepted takes it in as before and is never asked again, refused keeps it pending with refused, and an end that could not validate keeps it pending with failed, said in take-in.pending, never a refusal and never passed. An end of a replaced ask is dropped, written in the journal. The answer is read from the event's own output or output object. The wiring in the indexer's program comes with the whole-module case (IX5). Builds: design 47 G §713, A-232, A-247, §712 Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4hThe tool records its hand act, writes the ask {module, version, by, why} into the state delivered-again and answers that it is asked; the process's watch of that state wakes a pass at once, which says version-delivered again when every present machine placing the module runs that version healthy and takes the ask away, else keeps it with why, which assigner_waits lists. Builds: design 47 G §376, A-250 Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4horder.cd51fec81aThe five §298 order-wait tests of b2l (A-245, A-258, A-259, A-260) held no wait and said none after the merge with b2f: b2l's fixture put ace's presence as online (presenceValue(true)), and the merge rewrote it as b2f's heardPresence("ace", true, ...), whose flag says away. With every node away no module had a canary, so no want moved and no order edge was held (an order wait starts only on an online node, §268). The fixture now hears ace back; the order waits are built as those answers have them, unchanged. Builds: design 47 G lead answers A-245, A-258, A-259, A-260 (join 11 area 2) Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4hFor a module that requires finding-events and is bound, the membership lists the stream its binding names, the subject mesh.bus.<module>.finding-events.{event}.<node> and the finding events, so the tool runner carrying a stdio module (the enrolment) says an emitted finding event there; the test holds the enrolment's membership. Builds: design 47 G A-280, A-274, §529 Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4hThe readers' invokes are read with mesh-sdk's catalogue.InvokedVerbs, so a long-form {verb, fields} entry (the assigner's) is read rather than refused by the test's own decode. Builds: design 47 G A-275, §558 Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4hThe SDK's DeclareAskWorkers now declares each queue's two workers, main's and the named asks' (accept.<queue>.<asker>), and the puller takes from both; the bed declared main's worker again filtering both forms, which overlaps the named worker and the work queue refused ("filtered consumer not unique", 15 tests). The kind is a bed declaring by hand what the SDK declares: the builder's bed was the only one whose own consumer overlaps the SDK's, and now declares none. Behind it, the builder's seat server admits no caller of mesh-builds.reserved until the seat list holds mesh-builds' definition (A-278); the bed's seat-definitions answers it from the contracts module's own file. Builds: design 47 G §544, §600, A-115, A-278 Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4hCause: the bed reports go1.27.1 for both nodes at its start, and the test then reports go1.27.2. The builder's new durable on EVENTS hears the old reports first, so for a moment it agrees on go1.27.1 (said as toolchain-agreed go1.27.1 by n1, seen in a run's EVENTS); a netcheck entry heard in that moment is built at its old fingerprint ("the old fingerprint, naming go1.27.1, was built with go1.27.2", integration_test.go:767, twice on 2026-11-12). The builder acts as ADR 0465 says on what it heard; the bed told it a story the test does not mean. The test now purges the bed's go reports before its own, and asserts that no toolchain-agreed of go1.27.1 is ever said. Builds: design 47 G §492, §604, A-282 Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4hsayHeld stays in G's judgeOverHeld, after the written-verdict branch, for a fresh trunk manifest whose verdict the pass did not write. The test's merged manifest is written as the candidate's own text ("2.0"): the join's manifest digest is of the raw bytes (meshcatalogclient ManifestDigest), so "2" was another manifest and the test stopped before the case it adds. Builds: design 25 bus-state §1 (merged from main) Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4hbranches_test.go named nats.ErrNoResponders for a call that reached no holder, so the generator's check refused the contracts module ("a client uses only its seat's contract and mesh-sdk's runtime", ADR 0625 §3), met twice at join 11. The test now gives the words a runtime passes that refusal on with, which busretry.Undelivered reads the same way. Builds: design 47 G A-170 (the regenerated contracts, checked in place) Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4hcomposer.Manifest gains Fingerprint (wire {"digest","fingerprint"}) and Fill's get takes the Manifest. The checker fills it from a pull's fingerprint, else from the trunk revision's entry of the module (repoModules keeps each entry's fingerprint). Builds: design 47 G A-310 Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4hPlace named an image's build seat by "kind: image", a form no seat definition writes, so every image artifact's lint, unit and integration steps ended could not run. It now uses the seat definition's own form, seatdef.OnKindImage ("kind:image"). No other kind constant has the space. Builds: design 47 G §324, §397 Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4hDelivery
novox/mesh-delivery@bc8126efefa9— merged since 2026-11-13T13:09:27ZSource — source.main moved to novox/mesh-delivery@93e222a8a8. Whether it reached the machines is
mesh-delivery-view's, derived fromsource.main, the wants and the haves.Group
feat/47-G-join12: novox/mesh-catalog@53351dd30d, novox/mesh-contracts@ef1fe33a9d, novox/mesh-delivery@bc8126efef, novox/mesh-host@5caa760f5e, novox/mesh-networking@ccfdaec5ed, novox/mesh-sdk@627bee35c8, novox/mesh-tools@6be5679a0dTransitions
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: 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: 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.