jschoubben
f73b0bf6f6
The check of 2026-11-02 22:35 on a loaded shanks failed two buildrun tests on wall-clock bounds of 60 ms, the second failure of this kind tonight (the first: mesh-sdk's busretry tests, f02f142). Quick fix: give the two buildrun asker tests bounds of seconds. Thorough fix (chosen, because the kind recurs across every module of the repository): every test that raced a wall clock now waits on an event, steps a clock it is given, or has a bound only a failing test reaches. - buildrun asker tests: the steps' own times stand for the clock (bound an hour, starts and phases written in the past), no goroutine paces phases with sleeps. - builder: the decline bound reads Builder.Now; the decline test steps it; the stream-wait test waits for five check reads instead of 100 ms. - checker: the lost-ask try bounds an untaken ask at 200 ms only where that is what ends it; the program says when a merge turn changes, and the integration test waits on that line instead of 300 ms. - teller: the bed makes the teller's own ends bucket (a 10 s stall at start the tests raced by 0.5 s), waits for its warrant subscription instead of 500 ms pauses, and the package-level now is restored with t.Cleanup. - watchman: the recount, run in its own goroutine, is waited for instead of 10 ms. - polls of 2-5 s become 10 s (unit) and 20 s (integration). Under a throttled cgroup (half a core shared with two busy loops) beside the node-engine's suite, the buildrun tests failed 5 of 20 runs before and passed 30 of 30 after; no test added. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL
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.