R4g+R5 (mesh-catalog): the build modules pull asks, scripts become tests, build-agent references go (design 47) #464

Merged

jschoubben merged 45 commits from feat/r4g into main 2026-10-23 17:49:44 +00:00

Conversation 1 Commits 45 Files Changed 149

+3065 -3920

mesh-tools commented 2026-10-23 15:00:55 +00:00

Member

Copy Link

Copy Source

Design 47's last milestone, R4g+R5, one delivery group on feat/r4g.

• mesh-build-go, -node, -image claim the node-build seats and pull asks with a capacity setting; they require node-tools; gofmt and vet before the unit level; the digest answered in the call (issue 1887, issue 1911, issue 1917; ADR 0525, 0529).
• merge-check.sh and checks/ as Go tests, compared with the trunk's copy when the checker places it (issue 1293, issue 1295; ADR 0529).
• mesh-issues' core pattern and owners (issue 1041); the gate's port without the controller's checks (issue 1318).
• gitea: the forge requires no status on any repository; the repositories program removes existing required statuses once (with keep-main-rules false) and writes none; new repositories get no merge-check.sh; seat names of the old build agent gone (ADR 0534).
• nats keeps main's mesh-sdk pin (only test subjects change), so the bus does not move.
• mesh-build-go's ask-order integration test runs on a bus of its own (mesh-sdk testbus) and judges the order from the recorded start and end, not from when it looked (issue 1887).

Reviewed-by: review-r4g-2@shanks at c32474ee40
Pushed-by: lead-47@shanks

Design 47's last milestone, R4g+R5, one delivery group on feat/r4g. - mesh-build-go, -node, -image claim the node-build seats and pull asks with a capacity setting; they require node-tools; gofmt and vet before the unit level; the digest answered in the call (issue 1887, issue 1911, issue 1917; ADR 0525, 0529). - merge-check.sh and checks/ as Go tests, compared with the trunk's copy when the checker places it (issue 1293, issue 1295; ADR 0529). - mesh-issues' core pattern and owners (issue 1041); the gate's port without the controller's checks (issue 1318). - gitea: the forge requires no status on any repository; the repositories program removes existing required statuses once (with keep-main-rules false) and writes none; new repositories get no merge-check.sh; seat names of the old build agent gone (ADR 0534). - nats keeps main's mesh-sdk pin (only test subjects change), so the bus does not move. - mesh-build-go's ask-order integration test runs on a bus of its own (mesh-sdk testbus) and judges the order from the recorded start and end, not from when it looked (issue 1887). Reviewed-by: review-r4g-2@shanks at c32474ee40f44eaf7cd7179140b9492c4d32d76c Pushed-by: lead-47@shanks

mesh-tools added 32 commits 2026-10-23 15:00:55 +00:00

Swap hq's repo-check-alone rule to mesh/check like every main: nothing writes repo-check once build-agent goes (issue 1296, E1a) e4ec060ac7

Write no merge-check.sh in a new repository's first commit and announce none: tests run by convention (issue 1296, E1b) 2038943c3e

Make the build modules and the delivery parts core issue owners and drop build-agent (issue 1041, E3) a252aae862

Make the delivery gate ask the controller nothing of checks: no Check or Queue on the port, no checked event, no lost-check sweep, only mesh/check and the checker's verdict (issue 1318, E4a and E4b) 643de08882

Run each checks/<x> over the real tree as a Go test, the shrink-only lists against the trunk's copy; the words check within the unit bound (issue 1293, E5a) df9e3bd7e2

Count the long-running resources without health in a Go test over the real catalogue, through mesh-sdk's catalogue package (issue 1295, E5b) 20ea65f0ac

Delete merge-check.sh and merge-check-typescript.sh: every step they ran is a Go test or the build module's; a test refuses their return (issues 1295 and 1293, E5c) 2c32728395

Pull the Go build seat's asks beside the tools, delivery first and at most the node's capacity, so no part chooses a node for a Go build or check (issue 1887 A3go, ADR 0525 §2-§6) db937546ae

Read the trunk's copy only from MESH_CHECK_BESIDE/mesh-catalog: unset skips the comparison saying NOT COMPARED, set without the copy fails (issue 1293, E5a) c4fc565180

Take the build agent and the toolchain images out of the catalogue's prose, and refuse the word where it comes back outside the one module still naming it (issue 1295, E6) 6bfdbc5758

Stop hearing the retired build seats' events in gitea and the catalogue module, so no manifest consumes a seat nothing claims once node-build-agent goes (issue 1887 E2 with A9) d0ba022d20

Serve the Go build seat's verbs from the SDK's one form (issue 1887 A3go) 6e823d1f9b

Pull the Node build seat's asks beside the tools, delivery first and at most the node's capacity (issue 1887 A3node, ADR 0525 §2-§6) 8356d30e1b

Pull the image build seat's asks beside the tools, at most the node's capacity (issue 1887 A3image, ADR 0525 §2-§6) c304d3fb97

Ask the Node build seat a check with its levels, as the SDK's check job now carries them (issue 1887 A3node) 3111546ff1

Merge branch 'feat/r4g-catalog' into feat/r4g 17e9efa101

Pin mesh-sdk at feat/r4g's head c3915ffb, the merge of lane B's layouts, so every r4g module builds against one SDK ... 3c5ff051de

go.sum gains its lines from go mod tidy once mesh-sdk feat/r4g is pushed.

Remove the committed compiled test binary checks/words/words.test and ignore *.test (review round 1) 612486be18

Revert "Swap hq's repo-check-alone rule to mesh/check like every main: nothing writes repo-check once build-agent goes (issue 1296, E1a)" ... fa39738981

This reverts commit e4ec060ac7.

Restore the doc wording of the repositories program after dropping E1a (review round 1) dd74d4adee

Run gofmt and go vet with every build tag in each directory the Go unit level runs, so what the repositories' scripts checked is every repository's check (issue 1887 D7-go, ADR 0529 §1) ecd60fe074

Merge branch 'feat/r4g-catalog' into feat/r4g 78499235b6

Merge branch 'feat/r4g-asks' into feat/r4g 93f4f67a8f

Pin mesh-sdk at feat/r4g's head 9205222a, the merge of lanes A, B, S8 and F1, so every module r4g touches builds against one SDK ... 2246ccc492

go.sum gains its lines from go mod tidy once mesh-sdk feat/r4g is pushed.

Record the checksums of mesh-sdk feat/r4g 9205222a for the group's modules (R4g) d0a3a8ebc6

Keep nats on main's mesh-sdk pin: only its test subjects change in R4g, so the bus does not move (R4g) 281909e83d

Merge remote-tracking branch 'origin/main' into feat/r4g 0066b702f4

Run gofmt and go vet before the Go unit level's tests and give their time in its result, so a lint failure ends the level at once and the check's line can say what it cost (issue 1887 D7-go, review round 2 item 5; ADR 0529 §1) 14b7158fc0

Say in gitea's comments that no controller status is written since R4g, so the merge waits on mesh/check alone (issue 1887, review round 2 item 6) a1febd3ad8

Require node-tools in the three build modules, so the delivery plan puts the tool runner they pull asks through before them on every node (issue 1911) a493c90c0d

Pin the build modules to the mesh-sdk head whose puller says a poisoned ask and bounds a step from its start (issues 1907, 1887 review round 2) f08abb90d4

Pin checks/health to the mesh-sdk that knows the seat node-build-go, so its real-tree test reads every manifest 90ff4c485a

mesh-tools commented 2026-10-23 15:01:00 +00:00

Author

Member

Copy Link

Copy Source

Delivery novox/mesh-catalog@454fb8a918ad — failed since 2026-10-23T17:59:26Z

Covered: covered after its failure: a later walk that contains it was delivered: plan-1792777718506798022 (novox/mesh-catalog at e8300455 into main, done, contains its merge e8300455)

Delivery plan — builds claude-code, gitea, lab, mesh-build-go, mesh-build-image, mesh-build-node, mesh-catalog, mesh-delivery-gate, mesh-issues → ace, g14, novox, shanks; no bus step

• tier 0: claude-code, gitea, lab, mesh-build-go, mesh-build-image, mesh-build-node, mesh-catalog, mesh-delivery-gate, mesh-issues
• ace: receives claude-code
• g14: receives claude-code, mesh-build-go, mesh-build-node
• novox: receives claude-code, gitea, mesh-build-go, mesh-build-node, mesh-catalog, mesh-delivery-gate, mesh-issues
• shanks: receives claude-code, lab, mesh-build-go, mesh-build-image, mesh-build-node
• claude-code keeps data (ADR 0233): what it holds is backed up before it moves
• gitea provides npm-package-registry, git, gitea-read, forge-account: its consumers are sent again after it
• gitea keeps data (ADR 0233): what it holds is backed up before it moves
• lab keeps data (ADR 0233): what it holds is backed up before it moves
• grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before claude-code, lab, mesh-build-go, mesh-build-image, mesh-build-node is judged on its first machine

Group feat/r4g: novox/hq@e8bd9171cd, novox/mesh-catalog@454fb8a918, novox/mesh-controller@c9a7102bc5, novox/mesh-delivery@b2c545c40a, novox/mesh-host@4b4bb09a05, novox/mesh-lab@4653b17e18, novox/mesh-media-catalog@f4f0bbcfe5, novox/mesh-sdk@a2c813a6b4, novox/mesh-tools-go@5023de36fd, novox/mesh-tools@860043fd7f, novox/okioki@e67d21e8b4

Machines

• claude-code on every machine running it: sent
• mesh-controller on every machine running it: sent
• mesh-delivery-indexer on every machine running it: sent
• mesh-sdk on every machine running it: sent
• node-tools on every machine running it: sent
• mesh-build-go on every machine running it: sent
• mesh-build-image on every machine running it: sent
• mesh-build-node on every machine running it: sent
• mesh-delivery-builder on every machine running it: sent
• mesh-delivery-checker on every machine running it: sent
• mesh-delivery-gate on every machine running it: sent
• mesh-delivery-teller on every machine running it: sent
• mesh-delivery-view on every machine running it: sent
• mesh-delivery-watchman on every machine running it: sent
• mesh-issues on every machine running it: sent
• audit-logger on every machine running it: sent
• bazarr on every machine running it: sent
• bookshelf on every machine running it: sent
• confluence on every machine running it: sent
• gitea on every machine running it: sent
• gitlab on every machine running it: sent
• grafana on every machine running it: sent
• home-assistant on every machine running it: sent
• icecast on every machine running it: sent
• influxdb on every machine running it: sent
• jira on every machine running it: sent
• lidarr on every machine running it: sent
• mesh-catalog on every machine running it: sent
• model-usage on every machine running it: sent
• mosquitto on every machine running it: sent
• netcheck on every machine running it: sent
• nextcloud on every machine running it: sent
• nodered on every machine running it: sent
• ombi on every machine running it: sent
• openai-consumer on every machine running it: sent
• radarr on every machine running it: sent
• redis on every machine running it: sent
• route-adapter on every machine running it: sent
• showcase on every machine running it: sent
• sonarr on every machine running it: sent
• tautulli on every machine running it: sent
• umami on every machine running it: sent

Transitions

• 2026-10-23 17:47 (new) → proposed (announced): novox/mesh-catalog#464's head announced
• 2026-10-23 17:49 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on
• 2026-10-23 17:55 held → delivering (go): its walk started on a word that was not this owner's: the controller's own path, which waits for nobody, or a person's plans go
• 2026-10-23 17:59 delivering → failed (failed): its walk failed, carrying its own commit: a gate on a first machine (what it carried put back), a build, a machine

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-catalog@454fb8a918ad` — **failed** since 2026-10-23T17:59:26Z **Covered**: covered after its failure: a later walk that contains it was delivered: plan-1792777718506798022 (novox/mesh-catalog at e8300455 into main, done, contains its merge e8300455) **Delivery plan** — builds claude-code, gitea, lab, mesh-build-go, mesh-build-image, mesh-build-node, mesh-catalog, mesh-delivery-gate, mesh-issues → ace, g14, novox, shanks; no bus step - tier 0: claude-code, gitea, lab, mesh-build-go, mesh-build-image, mesh-build-node, mesh-catalog, mesh-delivery-gate, mesh-issues - ace: receives claude-code - g14: receives claude-code, mesh-build-go, mesh-build-node - novox: receives claude-code, gitea, mesh-build-go, mesh-build-node, mesh-catalog, mesh-delivery-gate, mesh-issues - shanks: receives claude-code, lab, mesh-build-go, mesh-build-image, mesh-build-node - claude-code keeps data (ADR 0233): what it holds is backed up before it moves - gitea provides npm-package-registry, git, gitea-read, forge-account: its consumers are sent again after it - gitea keeps data (ADR 0233): what it holds is backed up before it moves - lab keeps data (ADR 0233): what it holds is backed up before it moves - grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before claude-code, lab, mesh-build-go, mesh-build-image, mesh-build-node is judged on its first machine **Group** `feat/r4g`: novox/hq@e8bd9171cdbc, novox/mesh-catalog@454fb8a918ad, novox/mesh-controller@c9a7102bc53b, novox/mesh-delivery@b2c545c40aec, novox/mesh-host@4b4bb09a05a0, novox/mesh-lab@4653b17e18a7, novox/mesh-media-catalog@f4f0bbcfe59c, novox/mesh-sdk@a2c813a6b468, novox/mesh-tools-go@5023de36fded, novox/mesh-tools@860043fd7fa0, novox/okioki@e67d21e8b448 **Machines** - claude-code on every machine running it: sent - mesh-controller on every machine running it: sent - mesh-delivery-indexer on every machine running it: sent - mesh-sdk on every machine running it: sent - node-tools on every machine running it: sent - mesh-build-go on every machine running it: sent - mesh-build-image on every machine running it: sent - mesh-build-node on every machine running it: sent - mesh-delivery-builder on every machine running it: sent - mesh-delivery-checker on every machine running it: sent - mesh-delivery-gate on every machine running it: sent - mesh-delivery-teller on every machine running it: sent - mesh-delivery-view on every machine running it: sent - mesh-delivery-watchman on every machine running it: sent - mesh-issues on every machine running it: sent - audit-logger on every machine running it: sent - bazarr on every machine running it: sent - bookshelf on every machine running it: sent - confluence on every machine running it: sent - gitea on every machine running it: sent - gitlab on every machine running it: sent - grafana on every machine running it: sent - home-assistant on every machine running it: sent - icecast on every machine running it: sent - influxdb on every machine running it: sent - jira on every machine running it: sent - lidarr on every machine running it: sent - mesh-catalog on every machine running it: sent - model-usage on every machine running it: sent - mosquitto on every machine running it: sent - netcheck on every machine running it: sent - nextcloud on every machine running it: sent - nodered on every machine running it: sent - ombi on every machine running it: sent - openai-consumer on every machine running it: sent - radarr on every machine running it: sent - redis on every machine running it: sent - route-adapter on every machine running it: sent - showcase on every machine running it: sent - sonarr on every machine running it: sent - tautulli on every machine running it: sent - umami on every machine running it: sent **Transitions** - 2026-10-23 17:47 (new) → proposed (announced): novox/mesh-catalog#464's head announced - 2026-10-23 17:49 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on - 2026-10-23 17:55 held → delivering (go): its walk started on a word that was not this owner's: the controller's own path, which waits for nobody, or a person's `plans go` - 2026-10-23 17:59 delivering → failed (failed): its walk failed, carrying its own commit: a gate on a first machine (what it carried put back), a build, a machine The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

jschoubben added 1 commit 2026-10-23 15:04:11 +00:00

Give checks/trunk a full module path, so go mod verify in the checks that use it treats it as the local module it is (R4g group check) a00962871c

jschoubben added 1 commit 2026-10-23 15:06:13 +00:00

Pin mesh-sdk at feat/r4g's head a2c813a6, its test fixture fix, with go.sum tidied b60077850d

jschoubben added 1 commit 2026-10-23 15:19:04 +00:00

Merge remote-tracking branch 'origin/main' into feat/r4g b85d65b53f

jschoubben added 1 commit 2026-10-23 15:19:41 +00:00

Prove a check ask's digest is the digest tool's answer in the call, so the checker keys kept verdicts by it (issue 1917) d6b9cef9d0

jschoubben added 4 commits 2026-10-23 15:20:33 +00:00

gitea: require no status on main, judge mesh/check in the merge tool instead (ADR 0534) ... d2036f2a63

The forge's required status was a second copy of the gate mesh-delivery and
the merge tool already keep; a stuck status writer held it too (issues 1886,
1891) and only a hand change at the forge let a fix merge. Main keeps no push,
the tools' merge whitelist and no administrator override. The merge tool
judges mesh/check whether or not the branch requires it, and on a branch that
requires none merges only a head the operator's Approve names. The protection
tool loses its status argument.

gitea: keep the operator's own login on main's merge whitelist beside mesh-tools (ADR 0534 §2) ... 79777d0f78

The operator merges by hand at the forge when the mesh's own path is stuck,
without changing a rule. The logins come from the trusted config value
main-mergers, merged into the runtime config both programs read.

Merge origin/main (keep-main-rules) and fix/forge-requires-no-status (ADR 0534): no required status anywhere, and with keep-main-rules false the program takes away a required status once and changes nothing else 70b16dc594

Merge remote-tracking branch 'origin/feat/r4g' into feat/r4g 1fc7b84ad2

jschoubben added 1 commit 2026-10-23 15:22:25 +00:00

Take the committed 10 MB repositories binary back out of the gitea module and ignore it (R4g review) 721db20887

jschoubben added 1 commit 2026-10-23 15:38:32 +00:00

Skip the trunk comparison, saying NOT COMPARED, when the catalogue's own copy is not beside: the checker before R4g places none, so R4g's own check could never pass (issue 1295) 0f768bc97b

jschoubben added 2 commits 2026-10-23 17:20:47 +00:00

Give the delivery-ask integration test a bus of its own: the level shares one bus across directories, so a named stream there could be taken by another test (R4g, issue 1887) f95f3f430e

Judge the delivery-before-check order from the step records, not a poll: at capacity 1 the check starts the instant the delivery ends (R4g, issue 1887) c32474ee40

jschoubben added 1 commit 2026-10-23 17:47:23 +00:00

Write a pull request's check verdict into its key after the key is created: the status event can be taken first (R4g, issue 1887) 454fb8a918

jschoubben merged commit e830045545 into main 2026-10-23 17:49:44 +00:00

jschoubben deleted branch feat/r4g 2026-10-23 17:49:44 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

mesh/ready

Reviewed and ready: mesh-delivery merges at the marked head once its checks pass (hq ADR 0364)

No labels

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

agent-ace agent-g14 agent-novox agent-shanks jschoubben mesh-tools miel.truyen nox-agent

No Assignees

2 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#464