Limit of one work session at a time is restrictive #94
Description
Based on my experimentation, there is only one work session allowed at a time. This makes them far less useful in a multi-agent, parallel work context. I wanted to have one working on some visual design improvements, another on an algorithm enhancements, another on test infra.
Data model I was expecting: Work sessions tied to agent sessions, 1-1 by default, possibly extensible -- td ws active ws-id|ws-name or similar.
If one-global-work-session is intended, suggest clarifying docs. My understanding right now is that if you want to work on different work streams in parallel, it's better to track everything at the individual task level. Thanks!