Pin the group's final mesh-sdk 206f794e with its captured conformance files, and read the engine's superseded word on a secret move (issue 774)

The captured SDK (testdata/beside, conformance/events) is taken again at the pinned commit, as CAPTURED
says. The controller's mirror of MoveSecretAnswer gains `superseded` (mesh-host b9c24a7): the vault holds
another value, the live one, and the machine's older value is not moved and not asked again. The field
test names it. A superseded row is still counted with the moved ones: counting it apart needs a field and
its words in nodeMove, more than the one line asked.
This commit is contained in:
2026-10-30 18:37:56 +01:00
parent 93d167f0e8
commit dd366f8a3f
5 changed files with 10 additions and 6 deletions
+1 -1
View File
@@ -9,7 +9,7 @@ a second place to clean besides the catalogue itself.
mesh-catalog f3a57dcc56fb6c198095cafd11d0decff9f720c4 modules/*/module.json, modules/*/files, modules/*/templates, predefined.json
mesh-host 9d9e3a46c4f5943cfffb413d962ce48b75e2fd39 examples/foundation-first-node.lock
mesh-sdk ef1ec1c93544f0fc12b2dca608167bf2af11a846 conformance/events/module-event.json
mesh-sdk 206f794eb319136a93cfaac57e5f18bee0a1ce8b conformance/events/module-event.json
To move them, from this repository's root, with the two repositories checked out beside it: