1. Blueprint updates - Added NO_GROUPS escalation docs to all 12 agent blueprints

2. Multi-image Docker architecture - Created role-specific Dockerfiles:
  - agent-base.Dockerfile (shared foundation)
  - agent-pm.Dockerfile, agent-dev-be.Dockerfile, agent-dev-fe.Dockerfile
  - agent-qa-be.Dockerfile, agent-qa-fe.Dockerfile, agent-doc.Dockerfile, agent-ux.Dockerfile
3. Orchestrator updates - roboco/runtime/orchestrator.py:
  - Added AGENT_IMAGES mapping and get_agent_image() function
  - Updated _ensure_agent_image() to build base + specialized images
  - Updated _spawn_container() to use role-specific image
  - Made _generate_mcp_config() role-aware (though kept notify for all since they need to receive)

agents/blueprints/backend/be-dev.md

@@ -212,6 +212,13 @@ Return to SCAN: `roboco_task_scan()` or `roboco_agent_idle()`
 
 ## Communication Rules
 
+### Handling NO_GROUPS Error
+If you get a NO_GROUPS error when sending a message:
+1. This means the channel hasn't been set up for this work yet
+2. Escalate to your Cell PM (be-pm) using `roboco_task_escalate`
+3. Include the channel and task context in your escalation
+4. If you have a task_id, always include it in message calls (routes to task session)
+
 ### Channels You Access
 - **#backend-cell** (read/write) - Your primary workspace
 - **#dev-all** (read/write) - Cross-cell dev discussion

agents/blueprints/backend/be-documenter.md

@@ -125,6 +125,13 @@ and verify all subtasks are done before calling `roboco_task_complete()`.
 
 ## Communication Rules
 
+### Handling NO_GROUPS Error
+If you get a NO_GROUPS error when sending a message:
+1. This means the channel hasn't been set up for this work yet
+2. Escalate to your Cell PM (be-pm) using `roboco_task_escalate`
+3. Include the channel and task context in your escalation
+4. If you have a task_id, always include it in message calls (routes to task session)
+
 ### When to Post in Session (DO)
 - **Questions about implementation** - Need dev/QA clarification
 - **Missing context** - Dev notes don't explain something critical

agents/blueprints/backend/be-pm.md

@@ -187,6 +187,21 @@ roboco_session_create_for_tasks({
 - Subtasks auto-inherit parent task's primary session
 - Full audit trail preserved
 
+**Handling NO_GROUPS Error:**
+If you get a NO_GROUPS error when creating a session, it means the channel
+doesn't have a group for this initiative yet. Groups are created by Main PM.
+
+Escalate to Main PM:
+```python
+roboco_task_escalate({
+    "task_id": "{task_id}",
+    "reason": "Channel #backend-cell has no group for this work. Need group created.",
+    "escalate_to": "main-pm"
+})
+```
+
+Main PM will create the group, then you can proceed with session creation.
+
 ### 7b. ACTIVATE TASK (REQUIRED)
 **Tool:** `roboco_task_activate(task_id)`
 

agents/blueprints/backend/be-qa.md

@@ -226,6 +226,13 @@ After verdict:
 
 ## Communication Rules
 
+### Handling NO_GROUPS Error
+If you get a NO_GROUPS error when sending a message:
+1. This means the channel hasn't been set up for this work yet
+2. Escalate to your Cell PM (be-pm) using `roboco_task_escalate`
+3. Include the channel and task context in your escalation
+4. If you have a task_id, always include it in message calls (routes to task session)
+
 ### Channels You Access
 - **#backend-cell** (read/write) - Your primary workspace
 - **#qa-all** (read/write) - Cross-cell QA discussion