jschoubben 19d06163de Announce the checker's states, owed readable, so the forge module may read it (R2-1) ...

R4e round 2 finding R2-1, ADR 0521: the forge module writes mesh/check from
the checker's owed state, read by a watch, because no event order between the
forge bridge and the forge module is kept by the delivery plan. A reader is
granted from the owner's announcement (ADR 0495 §2-§3), and the checker
announced nothing. It now says every state it keeps, with owed, previews and
verdicts readable: the forge module and the bridge read owed, the indexer
previews, the gate verdicts.

2026-10-22 21:38:53 +02:00

..

mesh-delivery-builder

Pin every R4e member module to mesh-sdk's final R4e head 104533e8, which holds review fixes S1 and S2, so the group pins one SDK

2026-10-22 21:29:20 +02:00

mesh-delivery-checker

Announce the checker's states, owed readable, so the forge module may read it (R2-1)

2026-10-22 21:38:53 +02:00

mesh-delivery-forge-bridge

Pin every R4e member module to mesh-sdk's final R4e head 104533e8, which holds review fixes S1 and S2, so the group pins one SDK

2026-10-22 21:29:20 +02:00

mesh-delivery-indexer

Pin every R4e member module to mesh-sdk's final R4e head 104533e8, which holds review fixes S1 and S2, so the group pins one SDK

2026-10-22 21:29:20 +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

Pin every R4e member module to mesh-sdk's final R4e head 104533e8, which holds review fixes S1 and S2, so the group pins one SDK

2026-10-22 21:29:20 +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