Overview
dsh-team-rooms
README / EN
Package documentation
Registry summary
dsh.pub verifies the pinned bundle contract, runtime facts, and distribution semantics. The complete README remains in the source repository.
Read the full README on GitHubLIMITATIONS
Known limitations
- Rooms require the storage domain to be composed; without `@deepseek-ai/dsh-storage-domain`, the `/room` command and the `room_*` tools are disabled. - A room needs at least two members to be interesting, and the roster is bounded by `maxMembersPerRoom`; membership is per session, not per user. - There is no cross-machine membership: every member is a process-local session of this deployment. - `room_transfer_task` needs an approval answerer. Without one it fails closed by design, so automated profiles that want handoffs must compose an approval service. - Cost/usage accounting is out of scope here (that lived in the background-agent half); the room surfaces report structure, not spend.
