jschoubben 5053e96d4e Route a recheck's pending through the gitea module's one writer of mesh/merge-gate ...

The recheck's pending was written from the tools' bundle, its own process, past the
writer's per-head chain: the first run's verdict mark stayed set, so a rechecked head
never said where its new run builds, and an old run's verdict in flight or redelivered
could land over the pending. The status tool is now served from the watcher's bundle
and writes the merge check's pending through the writer, and a verdict whose ask
(checked.id) predates the check now pending is dropped, weighed after a restart against
the forge's own history of the gate (novox/hq issue 456).

2026-10-12 12:20:23 +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

Route a recheck's pending through the gitea module's one writer of mesh/merge-gate

2026-10-12 12:20:23 +02:00

guard.test.ts

Route a recheck's pending through the gitea module's one writer of mesh/merge-gate

2026-10-12 12:20:23 +02:00

pages.test.ts

Name the package each controller-repository image compiles, and say a renamed file under both names (hq ADR 0267, issue 363)

2026-10-10 02:58:31 +02:00

protection.test.ts

gitea: give the controller what it maps a pull request onto the graph with; set both check statuses; protect a branch by tool (hq ADR 0237)

2026-10-06 21:56:04 +02:00

pulls.test.ts

Say where a pending merge check is: queued since when, then building on which machine (hq issue 446)

2026-10-11 03:14:06 +02:00

token.test.ts

Route a recheck's pending through the gitea module's one writer of mesh/merge-gate

2026-10-12 12:20:23 +02:00