jschoubben 3f9acf0223 A check composes only after the candidate's builds it waits on have ended (issue 1921) ...

The indexer writes a pull request's candidate first from its pull message alone, every module's
fingerprint "no merge preview is computed", and the fingerprints only with the preview, on the same
heads. A check that began on that first write kept its case: it waited on no build, said nothing,
and the engines, reading the previewed candidate, refused the module as not yet built (mesh-catalog
#624, mesh-delivery #163). Such a check now takes the previewed candidate before it judges the
manifests, waits on the builds and composes, as a whole try already does.

A build not ended within the build-wait-bound is named and the change is not composed, never an
engine's refusal of a fingerprint it has no done build of read as the change's.

Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

2026-11-07 12:48:11 +01:00

..

mesh-checking-program

The checking program judges the module graph's cycles from the edges the running checker gathers (issue 1921, B0 review round 1)

2026-11-06 23:28:20 +01:00

mesh-delivery-checker

A check composes only after the candidate's builds it waits on have ended (issue 1921)

2026-11-07 12:48:11 +01:00

mesh-delivery-checker-tools

The checker serves a checking program's input on its seat's verb input, and the build module asks it (issue 1921, B0 review round 1)

2026-11-06 23:39:39 +01:00