jschoubben 76c7ddfc52 Keep main's rule for which haves run inside the node's own composition ...

Review round 1: a have naming no build in a phase but running is also written for a
module that runs inside the node's own (waiting for a yes), so taking it out would
drop its resources before the yes. The fp the held have now keeps already fixes
postgres (issue 1289); a test drives an interrupted backup end to end.

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

2026-10-31 16:38:05 +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

selfcompose_test.go

Keep main's rule for which haves run inside the node's own composition

2026-10-31 16:38:05 +01:00

selfcompose.go

Keep main's rule for which haves run inside the node's own composition

2026-10-31 16:38:05 +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