mesh-delivery

Files

T

jschoubben 8f43d0ecdf AS23: build.ended says a failed end too; a hold under rule 1 says how the build stands

The builder's build.ended is said for a failed build as well (outcome, error whole);
the assigner's rule-1 hold reads "the build of M at F failed: <error>" from it and
"is being built" while none is heard. The assigner's reads of the builder's builds
bucket stay (see the report: a restarted assigner holds no ends heard).

Builds: design 47 G §575, §568, A-162 (survey AS23)
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

2026-11-12 05:43:15 +01:00

forms

MV1: move contracts and sdk under modules/, importers follow

2026-11-12 05:09:56 +01:00

builds_test.go

MV1: move contracts and sdk under modules/, importers follow

2026-11-12 05:09:56 +01:00

builds.go

gofmt: the six files the delivery review named, and three import blocks

2026-11-12 05:21:48 +01:00

busfree_test.go

mesh-delivery-sdk: the runner's stale-step part moves to package buildrun, so buildstep (layouts, keys, codecs) and the builder's published builds package reach no bus; a test each refuses it (B6e finding 5; ADR 0634 §1; issue 1966)