jschoubben af66f72931 Take the indexer's verdict on a manifest instead of judging it, and name a held module (ADR 0578) ...

Issue 1585, S17: the engine decodes manifests leniently; a module whose manifest the indexer refused is held and named,
its data key stands, and every other module's items are still published. Policy, HoldsData and the certificate check no
longer parse with the judge.

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

2026-11-01 02:04:34 +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

Take the indexer's verdict on a manifest instead of judging it, and name a held module (ADR 0578)

2026-11-01 02:04:34 +01:00

data.go

Take the indexer's verdict on a manifest instead of judging it, and name a held module (ADR 0578)

2026-11-01 02:04:34 +01:00

selfcompose_test.go

Take the indexer's verdict on a manifest instead of judging it, and name a held module (ADR 0578)

2026-11-01 02:04:34 +01:00

selfcompose.go

Take the indexer's verdict on a manifest instead of judging it, and name a held module (ADR 0578)

2026-11-01 02:04:34 +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