jschoubben 122f4dd727 Read a done build once, and work out the data items in the scope the pass composed in (ADR 0577) ...

The data items after a pass re-read each placed module's build over the bus (about 55 per pass on
ace, g14 and shanks); a done build never changes, so the composer keeps it. The items are now
worked out with the pass's own kept builds and modules run inside the node's own, as composed.

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

2026-11-01 00:18:30 +01:00

..

testdata

Pin mesh-sdk 754edfae, so a manifest the mesh refuses holds that module alone and the node composes the rest (issue 774)

2026-10-30 19:25:37 +01:00

data_test.go

Read a done build once, and work out the data items in the scope the pass composed in (ADR 0577)

2026-11-01 00:18:30 +01:00

data.go

Read a done build once, and work out the data items in the scope the pass composed in (ADR 0577)

2026-11-01 00:18:30 +01:00

selfcompose_test.go

Keep a have held by an interrupted backup and naming nothing out of the node's own

2026-10-31 20:19:21 +01:00

selfcompose.go

Read a done build once, and work out the data items in the scope the pass composed in (ADR 0577)

2026-11-01 00:18:30 +01:00

shadow.go

The node composes again only when what it composes from changed, so a want, placement, module or value written again asks the vault nothing (issue 774)

2026-10-31 01:59:58 +01:00