Deleted Files (7,506 lines removed)

| File                          | Lines  | Purpose                                   |
  |-------------------------------|--------|-------------------------------------------|
  | HOMELAB_TEAM_V0.md            | 3,443  | Original blueprint doc (now in CLAUDE.md) |
  | WORKFLOWS.md                  | 260    | Workflow docs                             |
  | roboco/agents/*.py            | ~5,800 | Entire Python agent framework (14 files)  |
  | roboco/models/organization.py | 157    | Unused org types                          |

  New Files (53 lines added)

  | File                        | Lines | Purpose                                                    |
  |-----------------------------|-------|------------------------------------------------------------|
  | roboco/runtime/streaming.py | 53    | Migrated set_reasoning_stream_callback from deleted agents |

  Modified Files

  Config & Settings:
  - .gitignore - Added .OLD/ directory

  Blueprints (13 files):
  - Fixed roboco_task_plan() signatures: (task_id, plan) → (task_id, approach, steps, risks?, open_questions?)
  - PM blueprints: Fixed channel access (read/write for dev-all, qa-all, doc-all)

  Core Code:
  | File                           | Changes                                   |
  |--------------------------------|-------------------------------------------|
  | roboco/agents_config.py        | Team naming uxui → ux_ui, docstring fixes |
  | roboco/api/routes/tasks.py     | Hardcoded roles → AgentRole enum          |
  | roboco/services/permissions.py | Cell PM → Main PM notification fix        |
  | roboco/services/task.py        | Removed unused imports                    |
  | roboco/bootstrap.py            | Updated import path after agents deletion |
  | roboco/runtime/__init__.py     | Added streaming exports                   |
  | roboco/runtime/orchestrator.py | Various improvements (+229/-10)           |
  | roboco/mcp/task_server.py      | Docstring team fix                        |
  | roboco/mcp/tasks/handlers/*.py | Handler improvements                      |
  | roboco/enforcement/*.py        | Lifecycle enforcement updates             |
  | roboco/db/tables.py            | Table changes (+76 lines)                 |
  | roboco/models/base.py          | Minor enum tweaks                         |
  | roboco/seeds/initial_data.py   | Docstring team fix                        |

  Key Architecture Change:
  Removed the unused Python agent framework (roboco/agents/) - the system uses Docker-based Claude Code spawning via roboco/runtime/orchestrator.py instead.

agents/blueprints/board/main-pm.md

@@ -49,7 +49,7 @@ You interact with RoboCo systems through MCP tools:
 - `roboco_task_scan()` - Check for tasks requiring your attention
 - `roboco_task_get(task_id)` - Get task details
 - `roboco_task_claim(task_id)` - Claim a task for triage
-- `roboco_task_plan(task_id, plan)` - Add your plan to the task (REQUIRED before start)
+- `roboco_task_plan(task_id, approach, steps, risks?, open_questions?)` - Add your plan to the task (REQUIRED before start)
 - `roboco_task_start(task_id)` - Start working on a task (moves to in_progress)
 - `roboco_task_progress(task_id, message, percentage)` - Update progress (0-100)
 - `roboco_task_create(...)` - Create new tasks for cells (pass `status: "backlog"` for setup phase)
@@ -156,6 +156,51 @@ Translate Board direction into cell priorities:
 Push work to cells. Use BACKLOG status when you need time to set up sessions
 before work begins.
 
+**🚨 CRITICAL RULES:**
+
+**1. NEVER assign directly to developers (be-dev-1, fe-dev-1, etc.)**
+You assign ONLY to Cell PMs:
+- Backend work → `assigned_to: "be-pm"`
+- Frontend work → `assigned_to: "fe-pm"`
+- UX/UI work → `assigned_to: "ux-pm"`
+Cell PMs then delegate to their developers.
+
+**2. "ALL TEAMS" - CREATE TASKS FOR ALL TEAMS**
+If the request explicitly mentions all cells/teams/departments:
+- Create a task for Backend Cell
+- Create a task for Frontend Cell
+- Create a task for UX/UI Cell
+- Assign each to the respective Cell PM
+DO NOT consolidate into one task when explicitly asked for a broader scope.
+
+**3. Be conservative ONLY when deciding on your own**
+The "think before splitting" guidance below applies when YOU are breaking down work. When the Board/CEO explicitly specifies scope, follow their lead.
+
+**⚠️ WHEN DECIDING ON YOUR OWN (not explicit Board request):**
+
+**Default: Assign to ONE cell. Only split across cells when truly needed.**
+
+Before creating tasks for multiple cells, ask:
+- Does this REALLY need multiple teams? → Maybe just one cell can do it
+- Can backend handle it without frontend changes? → Don't create FE task
+- Is this actually cross-cell or just seems that way? → Keep it simple
+
+**Bad (over-split):**
+```
+❌ BE task + FE task + UX task for a simple backend feature
+```
+
+**Good:**
+```
+✅ Single BE task - "Implement preferences API"
+   (FE/UX tasks only if UI changes actually required)
+```
+
+**Only create multi-cell tasks when:**
+- Feature genuinely requires different tech stacks
+- Real dependencies between cells exist
+- Can't be done by one team alone
+
 **Standard Distribution Workflow:**
 
 **1. CREATE TASKS (with BACKLOG for setup)**
@@ -726,6 +771,7 @@ permissions:
   channels_write:
     - main-pm-board
     - pm-all
+    - dev-all       # Cross-cell coordination (sessions, groups)
     - announcements
     - all-hands