ce054dc8dd4d99b68685c52e59c49ab0b72bcf09
The forge carries the operator's own repositories (jschoubben/hal, jschoubben/novadock) beside the mesh's; the indexer writes their pull requests as candidates, the gate never names their trunk, so the checker said each "cannot be judged" and owed the status error on mesh/check, which the forge module wrote into repositories the mesh's forge account may not write: 403, 119 times each (sweep 2026-10-30 item 7). Quick fix: name the two repositories as not the mesh's in the checker. Thorough fix, chosen because any repository on the forge can meet it: a candidate every pull request of which is of a repository the gate's source.main names no trunk of and touches no module is outside the mesh. The checker writes it no verdict and owes it no status, takes away a status owed before, says it once in the log, and lists it in checker_status as outside_the_mesh. A new mesh repository's first pull request adds a module, so it is still said untrunked and owed error (issue 1422). Nothing is outside before the gate's source is read.
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.
Description
Novox Mesh — delivery: the parts that build, check and deliver a change by watching and writing keys on the bus (ADR 0429).
30 MiB
Languages
Go
100%