Dai Ha 19b10e3216 docs: CB-301 session-manager design spec (one-shot, no reuse; recycle in scope) ...

The as-built audit surfaced that WorkerService keeps no registry of what it
spawned (its own Javadoc: 'there is no registry; list() only asks herdr').
CB-301 adds a SessionManager wrapping WorkerService: an authoritative in-daemon
roster with a per-session lifecycle FSM (SPAWNING/READY/BUSY/DONE/RELEASED/
FAILED), deterministic release, and recycle (= release + fresh acquire, no
reuse). Leaves clean seams for CB-302 (checkpoint on release), CB-303 (idle_ttl/
context_cap/drain policy over roster), CB-304 (bridge_list reads roster).

2026-07-16 19:10:13 +02:00

..

CB-301-Session-Manager.md

docs: CB-301 session-manager design spec (one-shot, no reuse; recycle in scope)

2026-07-16 19:10:13 +02:00

MCP-Contract.md

Add MCP design doc

2026-07-14 12:30:20 +07:00

Team.md

docs: add Team.md under docs/

2026-07-14 19:14:25 +07:00

Worker-Startup-and-Trust.md

CB-112: workers inherit the primary's working directory (not $HOME)

2026-07-15 16:33:46 +02:00