Registry milestone: mesh-delivery (issue 1966) #151
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#151
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: the checker seat serves input and its verdict names its program (D1); the domain SDK carries the run ask (D2); the trunk merge carries the registry's steps as facts and rules (D3-D11); one composition path and the check's own verdicts in every composition (D12-D13); the seat list by digest, within its bound.
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: mesh-catalog requires the module of meshdeliverycheckerclient, and a new check checks/requiredmodules refuses an import whose module the go.mod does not require; mesh-delivery's assigner test flushes after its subscriptions (a race), and the checking program's seat answer carries no verb or message schemas (the tool runner's state refuses a schema property named credentials).
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
4735fc0b5fhttps://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i
indexer_config_readers {module} answers {readers: [{module, key, kind, readers}]} for every value key and own secret any kept manifest of the module ever declared: the module where its trunk's manifest declares it, each open pull request whose head declares it, none for a key no longer read (design 32 *A value no longer read*). It reads one watched copy of the modules, manifests and config-candidates states. Nodes is left out: the indexer cannot say which nodes' builds read a key. The indexer's findings are said on its views family and read by indexer_read_findings, for the condition keeper (the lead's ruling). Issue 1966. Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrigAnswers {revision, modules:[{module, digest, revision, bus-state}]} from the indexer's own states, at the verdicts state's mark, as A5's keeper reads it. Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrigFilled at each merge from the go.sum the indexer reads (the lead's ruling on I7), read once per consumer per process even where its hash is unchanged; the builder's floor asks {package} and reads {requirements: [...]}, highest last. Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig710c4032into the registry builder 5c8d59b6c7The checker's family asks (stream asks, seven days, in the old streams section) carries tag-wanted {repository, branch, head, module, package, pull}; the tag is left to the builder, which makes it from the branch. Each package's published is heard from the two package registry seats on the checker's durable consumer of the shared events stream; none within the ten-minute bound fails the check naming the package, before any member is built. A lone pull request and a try ask nothing (design 51 *Tagged versions*). Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrigDesign 51 *Tagged versions* and ADR 0607 §3, §5: once each package's published is heard, a Go member's ask names the group's tagged version of each package another member publishes (Go's form, v0.1.15-feat-x.2), a package new in the group included, and a TypeScript member's Node fetch takes {name, version} from the registry instead of a packed head. The published is matched by seat, head and name, so one head with several Go packages (mesh-contracts) gets each its own version. With no preview of the merge, a member's manifest is read at its head on the forge, so a package new in the group is asked for on the first check too (the lead's ruling 4 on A2c's finding 4). Needs mesh-sdk's PackageVersions.Check to take a Go semantic version (a2d-sdk-tagged-version.patch, for A1). Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrigaafd90b) d266a4c839d53986f) 84a509468488a9d19) 1cd0d83f41mesh-delivery's sdk/firstview moved whole into mesh-sdk go/views (J3): the builder, checker, watchman, teller and view follow each owner's state with views.ProcessReader.Follow(owner, state, tool, stream), naming the owner's read tool as their invokes name it and its views family as the owner's manifest's `streams` names it ("indexer-views", "assigner-views"); a refused Follow stops the start. Their beds serve the owners with viewstest.Serve and grant with viewstest.Grants by the same names. The view's tools ask the owners' read tools by their literal names. The assigner names its own views family and the indexer's itself (views.AssignerStream and IndexerStream are gone). Every views.StatusTools call takes handacts.Recorder{Ask: stdio.Ask}: a first view asked again by hand is a hand act, recorded through seat:mesh-hand-acts.hand-act, which the builder's, checker's, watchman's, teller's and view's manifests now invoke (a row in each manifest test, each failed first). Row (A2j's written-time switch): TestRunNeedsItsCredential "a want stood since the assigner's bus wrote it": the watchman's want time (createdOr) is the time the owner's bus wrote the key, through ProcessReader's first view (failed with createdOr ignoring the entry's time). sdk/go.mod: nats.go is indirect now. Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrigHistory (A2j finding 1, J4): the indexer's and the assigner's read tools are views.ReadTool over views.KeptSource, which answers `{key, history: true}` now; modules (20), heard (64) and wants (20) keep more than one revision. Rows in the view's "each tool answers through the owners' read tools as before": indexer_module_history and indexer_heard answer the owner's kept history, and a want's history (view_tiers' Since) is read through assigner_read_wants (the row it replaces held that the owner answered no history). Series (A2j finding 2, J4): the checker keeps each series change as a delivery.SeriesChange {module, artifact, from, to} and renders the status line from it; delivery.Verdict.Series holds the case's changes (each module's artifact once), and the verdict event's series the pull request's (meshdeliverychecker.VerdictHolderEventSeriesItem). An artifact new on the head is no series change (the lead's ruling). Rows: TestTheIndexersJudgeJudgesTheChangesManifests (the verdict's series; failed first, empty) and TestTheStatusIsPendingWhileTheCheckRunsAndEndsSuccessOrFailure (the event's; failed with the fill cut). Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrigDelivery
novox/mesh-delivery@4735fc0b5fdb— merged since 2026-11-07T14:19:44ZSource — source.main moved to novox/mesh-delivery@8ad2bf6951. 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
83b962cc6dwas declined: the operator, via telegram (user id verified), chose Decline. A new head asks the operator again.2fcd61binto the registry join: take-in size fix; the forge message keeps the join's needs field (D-0; issue 1966) 8668e3e538f2c61815) into b7/registry 84df3db4adb5a75693) into b7/registry cad6dc40b595fabbfc), the indexer needs it to build; identical bytes, so the join takes it once (ADR 0634 §1; issue 1966) 5125365189The end a run writes comes back on the key's watch, where Put stops the run's context and leaves the saying to the run, so the end was never said and the indexer kept the try's candidate. And the bed's stream checks lacked try.**, so every whole try's say waited out ten retries (10 s each), which on a loaded check ran the test past its 20 s bound ("the held try's ask was never taken"). The bed now makes the streams from module.json, and the test reads both events on the stream. 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: 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
918d21b7dawas declined: the operator, via telegram (user id verified), chose Decline. A new head asks the operator again.