mesh-delivery

Files

T

jschoubben d15d66fc47 DLV-I20 (builder): a build's end names the generated files its build module found out of step

The builder reads out-of-step from each lane's step result, a failed step's too, and writes it on the build's end
entry (BuildLogEntry.OutOfStep, J3's mesh-sdk field), where the indexer raises generated-types-out-of-step for a trunk
(the lead's ruling on A2i's finding 2). BuildAnswer names no such field yet, so it is read by name and shape.

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

2026-11-04 14:35:59 +01:00

mesh-delivery-assigner

DLV-F5r: the assigner answers its readers' first views before any new-form state, with no binding of the bus module

2026-11-04 14:29:10 +01:00

mesh-delivery-builder

DLV-I20 (builder): a build's end names the generated files its build module found out of step

2026-11-04 14:35:59 +01:00

mesh-delivery-checker

DLV-C3r1: a group's Go package version is keyed by the module path go-package-registry's published names

2026-11-04 13:39:08 +01:00

mesh-delivery-forge-bridge

Pin mesh-sdk 85ba0a9a70d8, the group's head of feat/l3-final (issue 774)