jschoubben 03eaf332ad Say the composition's time and the machines it composed in a check's line, once the assigner reports them (issue 1300, C10) ...

The line said only that the composition passed with an SDK commit, and its time sat among the parts that are dropped
first, so a forge status never said how long the composition took or which machines it covered.

2026-10-22 18:06:07 +02:00

..

mesh-delivery-builder

Write a failed publish of a merged image to the key; read mesh-build-image's captured steps (review r2)

2026-10-22 10:37:21 +02:00

mesh-delivery-checker

Say the composition's time and the machines it composed in a check's line, once the assigner reports them (issue 1300, C10)

2026-10-22 18:06:07 +02:00

mesh-delivery-forge-bridge

Set the owed mesh/check through gitea_check_status, the one tool that writes it (issue 1301's delivery part, option A)

2026-10-22 17:59:30 +02:00

mesh-delivery-indexer

Write a preview of the conflicts for a head that does not merge, and give the candidate's modules the reason; pin mesh-sdk to the R4c-5a head (issue 1445)

2026-10-21 21:25:45 +02:00

mesh-delivery-teller

Ask again at start a merge ask whose refusal the teller did not hear, since the router keeps no record of a refused ask (issue 1610, review round 1)

2026-10-21 16:45:31 +02:00

mesh-delivery-view

Bound builder_builds by key prefix, limit and read budget, list unreadable keys, refuse fp2 with commit, add candidate reads (issue 1827 V1-V3, 1818, 1681)

2026-10-22 17:23:46 +02:00

mesh-delivery-watchman

Commit no module's dependencies: fetch them in the check, the pinned SDK from beside it (issue 1235)

2026-10-19 15:27:37 +02:00