3 Commits

Include renames

Author	SHA1	Message	Date
agent-pool-9	0995824c01	Watch the world folder: auto spawn/upgrade, broker watch/unwatch, retire scan ... The host watches the whole world folder recursively with the notify crate (any writer counts, .sausage-tmp-* skipped, ~100 ms coalescing per path). A new or changed actor/<id>/actor.wasm (or new folder actor/<id>) is booted as at start once quiet: new = spawn (tested first), changed = upgrade. The broker `scan` request is gone; the boot pass stays, plus a full pass when the OS watcher overflows. New broker requests watch/unwatch {path} (saved in actor.json `watches`) deliver fs_changed {path, op: write|create|remove|rename, to?} from `fs`, not routed, dropped when the mailbox is full; overflow sends every watcher one fs_changed {path:"/actor", op:"rescan"}. Card #91 (multi-host step 1).	2026-10-17 07:12:04 +00:00
surma	0a8e8c2e3c	World folder is the source of truth ... - actor/<id>/ holds actor.wasm, actor.json, source/, public/, data/, versions/ - the broker boots by scanning actor/; a changed actor.wasm is an upgrade, a rejected one stays in versions/ with a reason and the files come back - /actor hides every data/ folder - subscriptions live in the subscriber's actor.json - cargo installs the SDK and points sausage-actor at it; no build limits - PROTOCOL.md	2026-10-15 11:14:11 +01:00
surma	1f49d0f7bb	Sausage: host, broker, commit-on-close filesystem, cargo actor, console, agent ... Imported from the spike branch, with: - a library crate (Host API) for the CLI and the tests - JSON test scenarios for candidates - commit on close only for new or truncated files - a Nix flake: nix run -- init, nix run -- run	2026-10-15 10:45:23 +01:00