Milestone 47 G: mesh-host's part of the one release #228

2026-11-13T13:01:37Z

mesh-tools commented

2026-11-13 13:01:37 +00:00

Design 47 milestone G, one release in seven repositories: the delivery group feat/47-G-join12 (issue 1966; ADR 0666, ADR 0667). It replaces #226 of group feat/47-G-join11, which the delivery gate closed after merging only 3 of its members this morning. Same head as #226. This is the node-engine. G's base branches are all main, so the gate can merge the whole group on one Approve.

The check cannot judge G on today's checker (issue 1373). Local evidence: go vet over 224 modules clean except the intentionally broken fixture; the touched modules' tests pass; G's manifest validator accepts 193 of 193; the second dry run against what is live finds no refusal caused by G.

Reviewed-by: mesh-code-reviewer@shanks at 8656e57eb9 (its one finding fixed in a12417fc, a sleep removed, read by lead-47@shanks); main merged in since (the zfs group, 5caa760f), looked at by the reviewer 2026-11-13 09:36 CET

https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

Design 47 milestone G, one release in seven repositories: the delivery group feat/47-G-join12 (issue 1966; ADR 0666, ADR 0667). It replaces #226 of group feat/47-G-join11, which the delivery gate closed after merging only 3 of its members this morning. Same head as #226. This is the node-engine. G's base branches are all main, so the gate can merge the whole group on one Approve. The check cannot judge G on today's checker (issue 1373). Local evidence: go vet over 224 modules clean except the intentionally broken fixture; the touched modules' tests pass; G's manifest validator accepts 193 of 193; the second dry run against what is live finds no refusal caused by G. Reviewed-by: mesh-code-reviewer@shanks at 8656e57eb96e859a75b287e345c2ae576f9c5173 (its one finding fixed in a12417fc, a sleep removed, read by lead-47@shanks); main merged in since (the zfs group, 5caa760f), looked at by the reviewer 2026-11-13 09:36 CET https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

mesh-tools added 65 commits 2026-11-13 13:01:37 +00:00

H-1: the node-engine claims its seat, says its findings on its own stream and hears running decbce4c54

Builds: design 47 G §364, §387, §199, §368, §411, §438

Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ

H-2: every service and container is started with MESH_FINGERPRINT, the fingerprint of the want it applies 730860b274

Builds: design 47 G §201, §205, §239

Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ

H-3: the node-engine says composed, running and capabilities-changed on the seat's subjects 26581d87ed

Builds: design 47 G §260, §227, §226, §177, §309, §404

Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ

H-4: running says stopped, with no fingerprint, once the have no longer holds the module 420087ab14

Builds: design 47 G §365, §404

Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ

H-6: the seat verb process-builds reads the build each process was started with; the engine keeps no callers table f3813a279e

Builds: design 47 G §262, §245, §440, §447

Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ

H-14: a module held for its claim is the finding module-held until it is composed or no longer wanted b41a0d59b6

Builds: design 47 main file (A claim problem holds its module), test 55

Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ

H-5: the seats a node passes on are decided from what every node said it runs, by SeatsToPassOn's new input 45e2b946c7

The node follows the node-engine seat's running events (an ordered read of the last message of each subject, then a durable
consumer), keeps what each node runs by `at`, acts on none until the first read ended, and hands the composer each node's
heard build with the manifest read by the event's digest; compose resolves the passes through catalogue.SeatsToPassOn
(heard, entries) with the trunk's entry for a node that said nothing.

Builds: design 47 G §199, §249, §459, §536, §556

Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ

H-7: the node record states the capability want-parts a073a001c5

Builds: design 47 G §525, §94, §192

Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ

H-15: the apply guard and the yields read the node-engine's module from the entry claiming its seat 602ed830e9

The module is the one whose catalog entry claims node-engine, else the one this node heard run the build its own
fingerprint names; no name is fixed in the guard or in the compose.

Builds: design 47 G §364, §527, §428

Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ

H-13: the node-engine's findings are written and said by mesh-sdk's finding writer ce01ec1f68

A finding is written in the node's state findings and followed by finding-written or finding-cleared on the engine's own
stream mesh-host-findings; the engine states every finding it observes at its start (the seat list's finding only while the
reader waits for the list, else not) and when the keeper asks, and answers an ask by a new statement. The node's grant in
the golden file gains the stream's publish, the ask stream's consumer, and the whole of its state findings.

Builds: design 47 G §383, §384, §390, §461, §485, §503

Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ

H-8: a want's parts are checked by the digests the composition fetches 5d3b446988

A want with parts is applied only when every fetched archive, process and container
digest is among the parts and every part is a fetched digest; otherwise the module
keeps running what it has and its have is held with detail parts-differ naming the
digests. A want with no parts is applied as before.

Builds: design 47 G §524, §379

Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ

The node-engine says no capabilities-changed: manifest-reads-changed alone says a node's capabilities, as the contracts' K6 has the seat 75f5c64646

The join with mesh-contracts' K6 (7d730a4a) removes the event and its body; H-3's second source of the same fact goes (haveState.capsSaid, capabilitiesToSay, sayCapabilities), the test asserts none is said.

Builds: design 47 G §590

Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ

The node-engine's compositions use the catalog key's codec meshcatalogkey, as meshcatalogclient's wrappers go 189ed10c36

Builds: design 47 G §670

Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ

H-13: the node-engine's seat-list and held-module findings go through mesh-sdk's held writer 38e13ef030

The seat list's five-minute finding and the finding of a held module are raised as they happen, so they use the held
writer (seeded at Start, Held() answers what stands) over the contract of the seat mesh-conditions; the keepers keep no
set or sweep of their own, and the writer is started before the seat list reader writes or clears any. The engine's own
finding stream stays its foundation stream mesh-host-findings.

Builds: design 47 G §529, A-29, A-30, A-37, A-38, A-40
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

G §421, §683: the node-engine reads the entry its want names by fingerprint and keeps its entries and wants 7703162c95

The node's own composer reads the catalog half through meshcatalogclient's Entries cache over its own calls of
mesh-catalog's verb entry, and no longer watches or reads the indexer's modules, manifests and verdicts or the
builder's builds: a module's manifest is its entry's, each artifact's reference is made from the digest its want's
part names (artifact-store://<module>/<artifact>/blobs/<digest>, A-50). A want whose entry is asked or not found is
held, its have the phase held with a detail opening entry-asked: or entry-missing: naming the fingerprint. The
entries and wants it composes from are kept in composed-<node> (entry.<digits> and want.<module>), written before
the composition that uses them, read at start before anything is asked, a kept want standing until the wants'
live read answers, and dropped when nothing names them. The shadow keeps its reads (G §628).

The node grant gains the verb entry and the running stream's consumer calls; OverNATS hears the running stream
as the link's session does.

Builds: design 47 G §421, §683, §614, §628, A-47, A-50

G §422, §698: the node-engine serves first-views, first-view-again and entry-again, and its manifest names the verbs it serves 97d3df3e59

first-views answers {first-views, entries, wants}, entry-again asks one entry again as a recorded hand act and
answers {asked, read}; first-view-again names no view the engine follows (it follows no branch) and refuses in
words. module.json's claim of node-engine lists every verb the engine serves.

Builds: design 47 G §422, §698

W13.8: the node-engine fetches a kept build through the build node's kept-artifact, the node taken from the want's kept-on 5173f2a31c

A want that names a node in kept-on, for an artifact its parts name, is fetched through kept-artifact of that node's build seat and
read as an object on the bus, checked against the digest; with no kept-on it is fetched from the store, and the builder's builds
are read no more (the apply hook, the fetch and the object read from bc8fbc7, its node and fingerprint from the want).

Builds: design 47 G §271, §526, §421 (A-50)
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

G A-92: the node-engine's manifest declares the state bounds, a lifetime per key, in its old section 7c7b5e2d68

Builds: design 47 G §560, §557, §627, A-77, A-92
(the seat definition: mesh-contracts 2ae0c679304b828a3973dd23ecd19861577d141d)

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

G A-98: the node agent gains Env.Stop, which stops a module's units and containers and removes nothing 2b916ac043

Builds: design 47 G §297, A-98

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

G §421, §683: the node-engine reads the entry its want names by fingerprint and keeps its entries and wants cf378f9a25

The node's own composer reads the catalog half through meshcatalogclient's Entries cache over its own calls of
mesh-catalog's verb entry, and no longer watches or reads the indexer's modules, manifests and verdicts or the
builder's builds: a module's manifest is its entry's, each artifact's reference is made from the digest its want's
part names (artifact-store://<module>/<artifact>/blobs/<digest>, A-50). A want whose entry is asked or not found is
held, its have the phase held with a detail opening entry-asked: or entry-missing: naming the fingerprint. The
entries and wants it composes from are kept in composed-<node> (entry.<digits> and want.<module>), written before
the composition that uses them, read at start before anything is asked, a kept want standing until the wants'
live read answers, and dropped when nothing names them. The shadow keeps its reads (G §628).

The node grant gains the verb entry and the running stream's consumer calls; OverNATS hears the running stream
as the link's session does.

Builds: design 47 G §421, §683, §614, §628, A-47, A-50

W13.5: the node agent asks mesh-recovery for a restore point before a form change and restores it at a revert dc1aee51d9

Before a move across a kept data's form change the node agent asks snapshot-kept and waits for the ended of its own act; at a revert it stops the newer build (Env.Stop), asks kept-points, asks restore-kept with the snapshot of the point of the form and fingerprint it reverts from, waits for restored, applies the reverted build, and calls the point's catch-up as the module's tool through the tool runner. The wait is in the have (ask-at, act), bounded by a bounds key of the state bounds (recovery-wait-minutes, 90), and each ending is read as the table of 560 says. The manifest consumes mesh-recovery's ended and restored and invokes its three verbs.

Builds: design 47 G §296, §297, §554, §555, §560, §630, §631, §632, §633, A-77, A-92, A-98, A-108
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

A-112: the node-engine reads recovery-wait-minutes from a file its manifest declares, 90 when missing ece79788a3

The manifest declares the file recovery-wait (content ${config:recovery-wait-minutes}); the node-engine reads it at its start and
does not call stdio.Config, which needs the runtime that launches a bundle.

Builds: design 47 G §633, A-112
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

Merge branch 'feat/47-G-recover-host' into feat/47-G-join8 5694f6c39b

# Conflicts:
#	internal/selfcompose/entries.go
#	module.json

gofmt cmd/mesh-host/keptartifact_test.go 6441ae7e96

Builds: design 47 G A-95 (the owed gofmt)
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

A-113: a revert whose restore fails starts the newer build again; a form change not known waits; holds say wait-held 31697e696d

Builds: design 47 G A-113, §297, §560, §541, §629
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

A-101: the node-engine reads the router's record through mesh-sdk's operatorask, the bucket from the seat list 0dd32d9722

Builds: design 47 G A-101, §700, A-74
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

internal/apply: a test of the places a module is placed in follows no link on the machine it runs on 0f108fd8ac

Builds: design 47 G A-95 (the owed hang of TestAModulesOwnPlacesAreStillPlaced on real mounts)
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

G §560: a cancelled recovery act holds the move with the hand act's why b3b13f2ae1

Builds: design 47 G A-117, §560
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

G §614: the node-engine writes the finding entry-not-found for a fingerprint the catalog half holds none of 054ca5a6b3

Builds: design 47 G A-117, §614, A-15, A-95
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

G §683: a start composes the modules whose kept want and entry it holds before its other inputs are read c6df8fa20f

The node's own record comes from the node-engine's statement of itself, taken in memory with no bus.

Builds: design 47 G A-117, A-120, §683, A-95
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

Join 9: the node-engine's link names no seat list verb in its operatorask contract (A-126) e8bff57b55

Builds: design 47 G A-126

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

Fix 10: the compositions read the catalog key codec from mesh-delivery's sdk efee30e243

Builds: design 47 G §614, §670 (ADR 0625 §4; lead answer A-144)

Join 10: the composer command may import the catalog key codec where A-144 moved it 7d06ef7997

The codec moved from the mesh-delivery contracts into mesh-delivery's domain SDK (sdk/catalogkey), still a pure package
of the standard library and mesh-sdk; the command's import rule named the old place only.

Builds: design 47 G A-144

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

H-18: running carries healthy and is said again when it changes 94f6c3dba4

Builds: design 47 G §520

H-20: a tools bundle's words hold its module's want fingerprint 4d656fe4e1

Builds: design 47 G §519, §618

H-17: the node-engine's own name is read from its applied record or first composing ac3422f914

Discovery, the finding writer and the vault login names read it; no fixed name.

Builds: design 47 G §527, §634 (A-149)

H-21: the manifest invokes revision (none-yet) and withheld, and config view-waits-minutes 732def66b0

The long-form invokes entry is read by mesh-sdk's second reader release (09d6070e): packaging's manifest
tests pass with it placed and fail before it is joined.

Builds: design 47 G §558, §617, §633, §635

H-24: the node-engine's hold tests are one test of cases, below main's count a3b646b3c9

1,726 test functions against main's 1,751.

Builds: design 47 G §419

MV1: move contracts and sdk under modules/, importers follow c2710f52dd

The delivery repository's contracts and SDK live under modules/ as
mesh-delivery-contracts and mesh-delivery-sdk, their Go module paths
renamed to match the folders (the TypeScript names already did), and
every importer in mesh-delivery, mesh-catalog, mesh-host, mesh-tools
and mesh-sdk follows in the same group: a design as it should be, one
path per module, checked by the group's check building every importer.

Builds: design 47 G §427, §88

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

Merge branch 'feat/47-G-fix11-a1' into feat/47-G-fix11-hrun 9afb287b9d

HRUN: mesh-compose reads its pipeline input from MESH_RUN_INPUT 4021de1d42

The composer answers the assigner's composition step: the request is read from the file
named by MESH_RUN_INPUT and the verdict is the last line of standard output, exit 0; the
compose-job path stays.

Builds: design 47 G §354, §63, §22; lead answer A-167

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

H-find: the node-engine raises what only it knows of itself as its own findings 4b215ba6ae

The have's failed phase (apply-failing), unhealthy health (module-unhealthy) and kept words (kept-as-it-runs), and each part of
its health report (machine-network, network-rewritten, network-unreachable, machine-units, relogin-needed,
directory-used-as-found, node-account-fallback), raised and cleared by the held writer where the engine knows the fact.

Builds: design 47 G A-197 (ADR 0596, A-192, A-149)

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

H-find: the findings keep the keys the watchman raised them under a3fea9106a

Each finding's id carries its token as a ref (A-14), so machine.<node>.network, .rewritten, .unreachable, .units and module.<module>.<node>.unhealthy and .kept
read as before.

Builds: design 47 G A-197

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

AM-D3 path: the node-engine takes the runner's reading and fingerprint into the node's record 8734d5ee1a

The grants part decides a node's withheld subjects from the runner's own
reading tied to the runner that stated it; the merge into capabilities stays
for placement.

Builds: design 46 7 §6 (its node's node-engine takes both into the node's record), lead answer A-203 (runner-capabilities, runner-fingerprint)

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

AM-H1: the node-engine's composition names the withheld subjects, read through mesh-grants' withheld 77e6e48ecd

The node-engine never reads the grants part's state: it asks the seat's verb
withheld in its own name, and says withheld unknown when nothing answers.

Builds: design 46 7 §6 (the composition reads them through the verb withheld; the node-engine's manifest gains mesh-grants in uses; "withheld unknown: the grants part does not answer"), lead answer A-239

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

Merge commit 'a3fea910' into feat/47-G-fix11-hrevert a1a328c43e

H-revert: the node agent starts a held revert on the live data when its want says revert live bef467febe

A want with `revert` `live` starts the reverted build with no restore, no aside taken and no catch-up, and
applies as any want; without the field a revert with no restore point stays held.

Builds: design 47 G §710 (G-21-provider-and-revert-ask.md, "On the answer"), §300, §567

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

The node-engine's seat reader reads invokes in both forms and refuses a form it cannot read d18bf8b3fd

Builds: design 47 G A-275, §558

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

Join 11: the node seat's discovery test names the engine's own module, not a fixed one 0c37ac378c

H-17 made discovery read the node-engine's own name (§527) instead of the constant mesh-host,
but the integration test still gave its link no own name and expected mesh-host, so every
endpoint announced an empty module. It now gives the link an own name and expects that one.

Builds: design 47 G §634, A-149

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

J23 A-292: a node seat event the bus did not take is said again on the same link a9b9709911

After a restart, g14's engine restated its reads three seconds after its
first, bootstrapped statement, and the assigner never heard that event: a
say that failed past the bus's retry bound waited for the next link. Now a
say the bus did not take (no responders, a deadline) is said again on the
link until the bus takes it, off the caller, each failed attempt written to
the engine's journal with the event's name; only a lost link, or a refusal
the bus answered, keeps it for the next link.

Builds: design 47 G §590, A-292
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

Merge origin/main into the join: a placed module's failed build said as refused 4ef07521eb

Brings mesh-host #224 (issue 1966): newestFPs returns a placed module whose
newest build failed, composedValues writes its refused key at that fingerprint,
takeBuildDone starts the pass on a failed build. Conflict in newestFPs settled
by keeping G's by-entries branch first (design 47 G §421, §628: the node reads
neither the indexer's modules nor the builder's builds; it returns no failed),
and main's failed-build path in the other.

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

J25 A-293: a placed module's failed newest build said as refused in by-entries mode, on the builder's build-ended event 905265a56b

Reading the catalog half by fingerprint, the node-engine no longer reads the builder's builds, so #224's refused key was
never written there and a reader waited on a build that will never be done. The engine now hears the builder's
build.ended stream, read whole at start then followed (as the assigner hears it); the last trunk end of a placed module
that ended failed is written as the refused key with the event's words, a later done end deletes it, an end naming a
branch moves nothing. The manifest consumes mesh-delivery-builder.build.ended.**.

Builds: design 47 G A-293 (with §421, §628), ADR 0593 §6, issue 1966 U1/U8

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

H1 (review r2): the foundation host is the entry that claims the seat node-engine, not a module named mesh-host 3167f0104f

Builds: design 47 G §527, §634

H4 (review r2, A-307): the node-engine's manifest names no uses; its invoke of seat:mesh-grants.withheld is the edge 302dcc098f

Builds: design 47 G §635

H3 (review r2): the entries test waits on the refusal the composer says until the ghost's reason is entry-missing 1d409cd852

Builds: design 47 G §421, §614 (test only)

H5 (review r2, A-308, A-312): the shadow watches no indexer modules; it reads the entries its wants name and asks the verb module for a module a candidate adds e558510a54

Builds: design 47 G §421, §628

R3-1, R3-2, R3-3: the node-engine reads no build of the builder; the shadow builds from the entry it holds 23799a30ed

The composer's Build is made from the catalog half's entry it holds and the parts of the want that names it (buildOf); the
inputs of the indexer's modules and the builder's builds, takeBuildDone, takeModule and the builder read are gone, and mesh-host
names no BuilderBuildsBucket. The shadow takes the entries of the builds it composes from (askBuildsEntries), builds a module a
candidate adds from its entry and the candidate's `added` parts (A-316), and holds, with the reason, a module whose entry
has no part given, whose fingerprint the verb module does not give, or for which it errors (A-312). Its composer is given the
entry call as the node's own is. Rows: a built module added with and without parts, the verb module answering no fingerprint
and erroring.

Builds: design 47 G §421, §628, A-308, A-312, A-316

H9: an entry asked again by hand is asked again in the shadow's cache too, so a candidate waits no longer on a not-found it holds 860ccd7e30

Builds: design 47 G §698 (entry-again), §421 (A-308: the shadow reads the entries its wants name)

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

H9 test: entry-again takes a shadow's not-found entry in 321a0744d8

Builds: design 47 G §698; lead answer A-319

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

R3-3: the node's own composer has no path without an entry call; its tests compose from the catalog half 650910dc9e

Builds: design 47 G §628, §421, A-312, A-317

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

Test 36: the recovery wiring is driven through the node agent by a revert want of db 8656e57eb9

Builds: design 47 G §296, §297, §554, §560, A-113, A-320

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

Remove the real sleep from the recovery integration test

mesh/delivery-group group feat/47-G-join11 checking: 7 of 7 member(s) ready

Details

mesh/delivery closed: a newer head of the same pull request

Details

mesh/check checking a12417fc13c7 on 0193949efe9f | novox/mesh-host#226 in group feat/47-G-join11

a12417fc13

Builds: design 47 G (playbook 07 step 2: no real sleeping in a test)

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

Merge main into feat/47-G-join11 (G takes in main before its push)

mesh/delivery-group group feat/47-G-join11 checking: 17 of 17 member(s) ready

Details

mesh/delivery closed: a newer head of the same pull request

Details

mesh/check checking 0a9d1efe8918 on f8acfaeed79d | novox/mesh-host#226 in group feat/47-G-join11

0a9d1efe89

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

Merge main into feat/47-G-join11: the node-engine's if-config, config-lines, config-json and stop at a failure (issue 1979) d63aae1d55

The whole test's web manifest keeps G's entry form (no build artifact, the entry read by fingerprint) and takes main's resources under if-config and config-lines.

Builds: design 47 G §421; design 42 zfs-owns-zfs H1-H5

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

A-342 engine-node-env: every process runs with its node's name as MESH_NODE

mesh/delivery merged: source.main moved to novox/mesh-host@fd023f7473bc

Details

mesh/delivery-group group feat/47-G-join12 merged: every member is merged

Details

mesh/check checking 5caa760f5eaa on fd023f7473bc | novox/mesh-host#228 in group feat/47-G-join12

5caa760f5e

The apply gives each process the declaration's For as MESH_NODE beside its own env, so a process that reads MESH_NODE (mesh-sdk, the zfs follower's writer and its node-service-manager calls) names its node.

Builds: design 47 G A-342

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

mesh-tools commented

2026-11-13 13:02:43 +00:00

Delivery novox/mesh-host@5caa760f5eaa — merged since 2026-11-13T13:09:32Z

Source — source.main moved to novox/mesh-host@fd023f7473. Whether it reached the machines is mesh-delivery-view's, derived from source.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@6be5679a0d

Transitions

2026-11-13 13:02 (new) → proposed (announced): novox/mesh-host#228's head announced; #226 with the same head closed unmerged
2026-11-13 13:02 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
2026-11-13 13:09 ready → merged (merged): on the trunk its modules follow: merged there

The commit's note under refs/notes/mesh-plan keeps every transition of this change up to its merge: git log --notes=mesh-plan.

**Delivery** `novox/mesh-host@5caa760f5eaa` — **merged** since 2026-11-13T13:09:32Z **Source** — source.main moved to novox/mesh-host@fd023f7473bc. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Group** `feat/47-G-join12`: novox/mesh-catalog@53351dd30df2, novox/mesh-contracts@ef1fe33a9da5, novox/mesh-delivery@bc8126efefa9, novox/mesh-host@5caa760f5eaa, novox/mesh-networking@ccfdaec5ed2d, novox/mesh-sdk@627bee35c811, novox/mesh-tools@6be5679a0d58 **Transitions** - 2026-11-13 13:02 (new) → proposed (announced): novox/mesh-host#228's head announced; #226 with the same head closed unmerged - 2026-11-13 13:02 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false) - 2026-11-13 13:09 ready → merged (merged): on the trunk its modules follow: merged there The commit's note under `refs/notes/mesh-plan` keeps every transition of this change up to its merge: `git log --notes=mesh-plan`.

mesh-tools commented

2026-11-13 13:03:04 +00:00

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-tools merged commit fd023f7473 into main

2026-11-13 13:09:30 +00:00

mesh-tools deleted branch feat/47-G-join12

2026-11-13 13:09:30 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-host#228