3 Commits

Include renames

Author	SHA1	Message	Date
surma	f1af07506f	broker: upgrade and rollback keep a stopped actor stopped ... A stopped actor gets the new version installed, keeps its mailbox and does not run main until the next start. Running actors still restart on the new version. The upgraded and rolled_back answers say whether the actor runs.	2026-10-22 10:11:36 +01:00
surma	f9260faa5b	Host: one place for the instance config; message ids are strings	2026-10-15 13:44:06 +01:00
surma	11144b947e	Trim the harness to what it needs to keep going ... Host: - test first: a new version is tested where it lies; only an installed version goes to versions/, and instances run from there - data/ and public/ are shared by all versions; no snapshots; rollback restores code only - no re-delivery, status.json, list, remove/archive, smoke test, data/ hiding, or stdin timeout; rollback needs a version - supervisor.rs split out; one place for installing a version - init only writes the agent folder; run installs it like any actor - console: @actor, text to the agent, /help, /quit Agent: - every text goes out as a broadcast; 5-line prompt; 5 tools that describe themselves; turn.json only marks an active turn Docs: PROTOCOL.md, README.md, DECISIONS.md, AGENTS.md rewritten. Examples: only notes and notes-v2.	2026-10-15 13:35:45 +01:00