jschoubben
ef142bb8c0
The finding pipeline-waits was raised at the wait's bound and nothing cleared it. It now names the awaited runner fingerprint in one evidence entry, `awaited <fp>`, written when it is raised (A-276), and the runner's hearing of the node-engine seat's running clears exactly the findings whose entry names the fingerprint said healthy (A-218), through its held writer, which holds what its state findings held at its start: a finding raised before a restart is cleared too, and one awaiting another fingerprint stands. The summary is never read for it. A clear that fails has the running heard again. Builds: design 47 G lead answers A-218, A-276 (join 11 area 3) Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
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.