jschoubben
3e7f852472
mesh/delivery held for a person: merged without a passing check: only a person decides what follows
mesh/check failed: integration: mesh-delivery-indexer/cmd/mesh-delivery-indexer.TestIndexerCountsOnlyTheAssignedBuildNodesToolchains: within 5 s of n2…
On 2026-10-25 20:56 assigning mesh-build-node to ace again brought ace's report of 2026-10-23 (v26.12.0) back into the agreement before the module ran there; the indexer blanked every module's fingerprint to "builders disagree" and the controller's take-in refused modules already computed and built. - The toolchain gate (indexer, builder, checker; still one file in three) leaves a report out, said once, until its node writes it since its current assignment: the assignment's own time, or the revision that opened it. - The indexer keeps a module's held fingerprint while a language has no agreed toolchain, when its kept inputs with the toolchains it was computed with give it again; only a new fingerprint (a merge, a base, an agreed toolchain moved) needs the agreement.
mesh-delivery
Novox Mesh — delivery: the parts that build, check and deliver a change by watching and writing keys on the bus (ADR 0429).
Made by the mesh from the gitea module's config value repositories (novox/hq ADR 0428). Main takes no push: a change reaches it by a pull request whose mesh/repo-check (this repository's merge-check.sh) and mesh/merge-gate passed.