211e503409
## Design Decision Per bd (bead) system design, a task should have only ONE agent archetype assigned at a time. This provides clear ownership and simpler mental model. ## What Changed When assigning a new archetype: 1. Remove any existing agent: labels first (DELETE API) 2. Then add the new agent: label (POST API) 3. Optimistic UI updates to match ## Why This Makes Sense - Clear ownership: 'Who's working on this?' - Simpler coordination between tasks - Matches how bd/agent orchestration is intended to work - Reassigning is still possible (just click a different archetype) ## UI Behavior - If task has 'coder' assigned, clicking 'architect' will: 1. Remove 'coder' label 2. Add 'architect' label - Dropdown shows 'Assigned' badge on current archetype - X button still available to unassign completely ## Test Coverage Added graph-node-single-archetype.test.tsx with 5 tests: - Removes existing labels before adding new - Calls DELETE before POST - Only allows one archetype per task - Preserves non-agent labels - Returns early if same archetype clicked |
||
|---|---|---|
| .. | ||
| graph | ||
| sessions | ||
| shared | ||
| social | ||
| swarm | ||
| unified-shell.test.tsx | ||