mesh-delivery

Files

T

jschoubben f904ff425e mesh-enrolment: confirm closes an enrolment on the node's own call

Only the node dialled as node.<node> confirms (the runtime's proof of the caller is the confirmation, ADR 0587 §6); the
holder then says node-enrolled with the key's content and deletes the address key (while it still names the node) and the
node's key. A stop between the event and the deletes is finished by calling confirm again; the event keeps one message.
release now answers what it could not delete. Tests added: one table-style test.

(issue 774, 774/S57)

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

2026-11-02 01:44:46 +01:00

mesh-delivery-assigner

Pin mesh-sdk at c21d8fd, the removal group's head, so every member builds the same contract (issue 774)

2026-11-02 00:53:42 +01:00

mesh-delivery-builder

Name the agreed toolchain in the checker's check asks; pin mesh-sdk 67354f8 (ADR 0584, issue 1578)

2026-11-01 15:38:16 +01:00

mesh-delivery-checker

Integration test: mesh-grants writes the lease and hands it back on a real bus

2026-11-02 00:40:00 +01:00

mesh-delivery-forge-bridge

Expect the mesh packages a merged message carries in the forge bridge's whole test (ADR 0573 §2)