jschoubben e031758e4a Forget a kept build when its key is written again, and retry data items on the composer's bound (review round 1) ...

The builder claims a done key again as a new revision, so a build kept as done is dropped on any
write of its key. Data items that could not be worked out or written stay due and owe a pass after
the growing bound, so a first write refused before the state or grant exists is tried again
without waiting for an unrelated composition.

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

2026-11-01 00:27:29 +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

Forget a kept build when its key is written again, and retry data items on the composer's bound (review round 1)

2026-11-01 00:27:29 +01:00

data.go

Forget a kept build when its key is written again, and retry data items on the composer's bound (review round 1)

2026-11-01 00:27:29 +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

Forget a kept build when its key is written again, and retry data items on the composer's bound (review round 1)

2026-11-01 00:27:29 +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