jschoubben
efca168c55
mesh/repo-check head efca168c5522 merged into trunk 0e372c87f1df beside mesh-catalog#457@896bd883 +1 more — pass: its merge-check.sh passed
mesh/merge-gate head efca168c5522 merged into trunk 0e372c87f1df — pass: group feat/r4e composed: every machine composes with the change as it did without …
mesh/delivery-group group feat/r4e delivering: 0 of 4 delivered
mesh/delivery delivering: 0 machine step(s) passed
mesh/check failed: unit: ..test: node:internal/modules/esm/resolve:989 | efca168c5522 on b714eab995a5 | unit 2092 run, 0 kept, 3 skipped | integration…
R4e round 2 finding R2-1, ADR 0521: nothing in the delivery plan orders the forge module before the bridge, and the forge module's durable consumer keeps its deliver policy when its filters change, so a check.status emitted before it consumed the event was lost. The forge module now watches the checker's owed state and writes mesh/check itself, once per revision. The bridge emits no check.status, declares no emits, and neither reads the checker's owed nor hears its stream; OwedAct still refuses mesh/check. The integration test shows the bridge calls no tool and publishes nothing of its own when the checker owes mesh/check.
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.