mesh-delivery

Files

T

jschoubben 2e23b0b736 Prove against the bus that a mesh-sdk merge moves only importers of a changed package

The indexer whole: two catalogue modules report their imports at their builds'
end, mesh-sdk merges a change of buildstep alone, the packages key names the
merge with a digest per package, the buildstep importer moves and the other
keeps its fingerprint though the version line would have moved it (ADR 0593
§2-§4; D11).

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

2026-11-02 18:37:37 +01:00

mesh-delivery-assigner

Builder owns the step runner; a build's imports reach its done key and log

2026-11-02 18:29:56 +01:00

mesh-delivery-builder

Builder's integration test pulls asks with mesh-build-go's runner

2026-11-02 18:33:31 +01:00

mesh-delivery-checker

Builder owns the step runner; a build's imports reach its done key and log

2026-11-02 18:29:56 +01:00

mesh-delivery-forge-bridge

Bridge reads no mesh package from a go.sum