mesh-catalog

Files

T

jschoubben 1cf56688c1

mesh/merge-gate pass: builds gitea → novox; no bus step; every machine composes with the change as it did without (4 of 4 compose)

Details

mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)

Details

mesh/delivery failed: its walk failed, carrying its own commit: a gate on a first machine (what it carried put back), a build, a machine

Details

Make the gitea module the one writer of mesh/merge-gate, so a verdict always lands last (hq issue 446)

mesh-delivery read the gate as pending and then wrote "building on", and the gitea module could write the verdict in
between: the forge keeps the newest status, so a pass read pending and a failure hid under "building". The gitea
module now hears the build seat's started itself and puts every write of a head's gate on one chain, marking a
verdict the moment it is heard; a start from before the pending words were last set is not the current check's.

2026-10-11 03:23:52 +02:00

announcing.test.ts

mesh-delivery: say a head whose merge check started and never answered (issue 438)

2026-10-11 02:16:34 +02:00

checks.test.ts

Cover a held merge only when the forge says a later delivered merge contains it (review of #150 )

2026-10-09 02:57:18 +02:00

delivery.test.ts

Put the merge check back to pending before a recheck asks it (hq issue 305)

2026-10-08 10:11:26 +02:00

gate.test.ts

Make the gitea module the one writer of mesh/merge-gate, so a verdict always lands last (hq issue 446)