mesh-controller

Files

T

jschoubben ad3b4f185b

mesh/merge-gate pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without …

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 superseded: a newer head of the same pull request

Details

Judge a leaf module on one healthy reading, a core module on three (hq issue 524)

ADR 0282 decided readings by class and ADR 0304 took a leaf module to
one, but the gate never learned it: every build, leaf or core, needed
three readings over at least two minutes, so a container module that
was healthy at once still waited about two and a half minutes on its
first machine. The number of readings and the settle time now follow
the module's class: three after two minutes for the controller's own
path and the resolver, one for every other module. Tests that judge a
gate's other rules keep leaf modules on three readings.

2026-10-12 01:08:14 +02:00

artifacts

Leave an eligible index for a confirmed collect instead of letting it go alone

2026-10-08 15:47:42 +02:00

beside

Judge the SDK conformance fixtures against the SDK the controller pins, never a desktop's checkout (issue 449)

2026-10-11 04:19:01 +02:00

broker

broker: grant each credential the tool calls that name it as the caller, and no other (hq issue 365)

2026-10-11 05:25:29 +02:00

builder

Merge pull request 'A check never sees the forge credential, and what it publishes is redacted (issue 462)' (#226 ) from fix/462-a-check-never-sees-the-forge-credential into main