jschoubben
6c2d6605a5
The whole test runs the process on its own account against a bus of its own, every bound a setting of seconds, with a stand-in bus module for snapshot-get, snapshot-restore and snapshot-restored: a hand take's log, a restore waiting on the dump past its bound key, busy and the ask again, the expiry on its bound key, a keeper's snapshot in three chunks, a protected restore cancelled at its bound and its aside put back, one the keeper answers neither, and a stop putting the aside back. It found that an act said its ending event while it was still the running one, so a caller told busy that asked again on hearing it was told busy with the same act and heard nothing more: the act is now released and written ended before its ending event, and the removal at a snapshot-kept runs before its ended. Builds: design 47 G §557, §554, §681, §562, §551, A-138, A-140, A-141, A-143 Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
mesh-recovery
Holds the seat mesh-recovery (design 47 G §554): the recovery module takes, sets aside and restores a module's kept
data on the live bus, one act at a time, each act in the hand-act log, its result said as an event under the act's id.
Go: one process (cmd/mesh-recovery) that answers the seat's verbs itself (A-107, A-115) and a tools bundle
(cmd/mesh-recovery-tools) whose recovery_* tools call those verbs and hold no grant of their own (§656).
Its data item points holds the restore points and the asides; the digests of the points are on the bus in its state
digests (§567). Its settings are points-cap, points-filling-mark, point-keep-days and dump-wait-minutes.