jschoubben
7f53665beb
builder_build_again's answer (BuildAgainResult.Asks: "the ask ids put") was settled when the ask's id was noted in the key, before its put: the answer could come back naming an ask not yet on its stream (the check's flake in TestAnAskTheKeyNamesAndNobodyPutIsPutAtStart, "after 0 asks", about 4 runs in 100 under load), and a put the stream refused after the note was answered as asked, the key's failure unsaid. The watch is now told after the put; a refused put ends the look and the answer says the key's failure. Builds: lead answer A-148 (hq G-20, 3ce1dcf: the fix rides the release), issue 1126 note 72 (builder_build_again answers the asks put), ADR 0668 §1 (the note and the put are one act) 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.