mesh-host

477 Commits 5 Branches 0 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
jochen	5e189c2fca	Say a tool check's errors once and as they stand, and test the link on a real bus mesh/merge-gate pass: builds mesh-host → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of 4 compose) Details mesh/repo-check pass: THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; it… Details mesh/delivery delivered Details The evidence read "asking it: asking <subject>": the words are now the link's own. A deadline is said as the time the check gave it. A refusal is said only when the bus refused this question, not an earlier one under a grant since widened. merge-check.sh runs the tests that need a bus against a throwaway nats-server when the toolchain has one, and says so when it does not (hq issue 331).	2026-10-08 17:01:15 +02:00
jochen	f823ade868	Leave the gate to the build seat; check the node-engine's own code here (hq ADR 0237) The build seat now runs the gate itself, judging a node-engine change with the change's validator in the running controller because the module graph builds mesh-host from here. This script is the repository's own layer (mesh/repo-check): format, vet, and the suite under the race detector when the toolchain can.	2026-10-06 21:51:49 +02:00
jochen	2fb7c91eaf	Check the node-engine's changes against every machine before they merge (hq ADR 0237) merge-check.sh runs the suite, then builds the controller the mesh runs with this change's validator in place of the one it vendors and runs the merge gate: a change to the node-engine that would refuse what the mesh sends today fails its pull request, naming the machine. The installer's first user list lets the controller say a check's verdict and hear a pull request's head, as the controller now composes it.	2026-10-06 21:16:33 +02:00

Author

SHA1

Message

Date

jochen

5e189c2fca

Say a tool check's errors once and as they stand, and test the link on a real bus

mesh/merge-gate pass: builds mesh-host → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of 4 compose)

Details

mesh/repo-check pass: THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; it…

Details

mesh/delivery delivered

Details

The evidence read "asking it: asking <subject>": the words are now the link's own.
A deadline is said as the time the check gave it. A refusal is said only when the bus
refused this question, not an earlier one under a grant since widened. merge-check.sh
runs the tests that need a bus against a throwaway nats-server when the toolchain has
one, and says so when it does not (hq issue 331).

2026-10-08 17:01:15 +02:00

jochen

f823ade868

Leave the gate to the build seat; check the node-engine's own code here (hq ADR 0237)

The build seat now runs the gate itself, judging a node-engine change with the change's
validator in the running controller because the module graph builds mesh-host from here.
This script is the repository's own layer (mesh/repo-check): format, vet, and the suite
under the race detector when the toolchain can.

2026-10-06 21:51:49 +02:00

jochen

2fb7c91eaf

Check the node-engine's changes against every machine before they merge (hq ADR 0237)

merge-check.sh runs the suite, then builds the controller the mesh runs with this change's
validator in place of the one it vendors and runs the merge gate: a change to the node-engine
that would refuse what the mesh sends today fails its pull request, naming the machine. The
installer's first user list lets the controller say a check's verdict and hear a pull request's
head, as the controller now composes it.

2026-10-06 21:16:33 +02:00