mesh-delivery

Files

T

jschoubben fb96216e46 Read a sibling the checker does not place beside mesh-delivery from its captured copy, said (issue 1585)

The judge's tests moved from mesh-sdk, where mesh-host was beside them; the checker places only mesh-sdk and the
catalogue beside mesh-delivery (besideRules), so the node-engine's path rules failed as not beside. A sibling the run
holds beside is read there; one it does not is read from testdata/beside and the log says which; only a sibling
with neither fails.

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

2026-11-01 04:47:22 +01:00

mesh-delivery-assigner

Pin the group's mesh-sdk head after the gofmt fix

2026-11-01 03:26:58 +01:00

mesh-delivery-builder

Pin the group's mesh-sdk head after the gofmt fix

2026-11-01 03:26:58 +01:00

mesh-delivery-checker

Pin the group's mesh-sdk head after the gofmt fix

2026-11-01 03:26:58 +01:00

mesh-delivery-forge-bridge

Expect the mesh packages a merged message carries in the forge bridge's whole test (ADR 0573 §2)