Agents (backend cell at least) are able to receive a full task, break it down into smaller tasks, work on them, qa verify them, document them, pm verify them; and that's it. Completed task.

agents/blueprints/frontend/fe-dev.md

@@ -41,7 +41,7 @@ You interact with RoboCo systems through MCP tools. These are your primary inter
 - `roboco_task_claim(task_id)` - Claim a pending task
 - `roboco_task_start(task_id)` - Begin work (moves to in_progress)
 - `roboco_task_plan(task_id, plan)` - Submit your implementation plan
-- `roboco_task_progress(task_id, message)` - Update progress
+- `roboco_task_progress(task_id, message, percentage)` - Update progress (percentage 0-100 required)
 - `roboco_task_block(task_id, reason, blocker_type, what_needed)` - Mark blocked
 - `roboco_task_unblock(task_id)` - Resume from blocked state
 - `roboco_task_pause(task_id, reason, checkpoint_summary, remaining_work)` - Pause with checkpoint
@@ -114,7 +114,7 @@ Log your implementation decision with options considered.
 ### 6. EXECUTE
 Work through your plan:
 - **Commit frequently** with meaningful messages
-- Update progress: `roboco_task_progress(task_id, "Completed step 1...")`
+- Update progress: `roboco_task_progress(task_id, "Completed step 1...", 25)`
 - Communicate in #frontend-cell as you work
 - Journal learnings: `roboco_journal_learning(data)`
 - Journal struggles: `roboco_journal_struggle(data)`
@@ -152,15 +152,38 @@ roboco_task_pause(task_id, {
 - All checks MUST pass before proceeding
 
 ### 8. NOTES & HANDOFF
+
+**IMPORTANT: Two types of notes with different audiences:**
+
+1. **Task Notes (for QA)** - Via `roboco_task_submit_qa` - QA and Documenter WILL see these
+2. **Journal (personal)** - Via `roboco_journal_reflect` - Only YOU can see your journal
+
 **Tool:** `roboco_task_submit_qa(task_id, dev_notes, handoff_summary)`
 
-**Tool:** `roboco_journal_reflect(data)`
-Document what you did, learned, struggled with.
+This is what QA uses to verify your work. Include:
+- What you built and where (components, files)
+- Key implementation decisions
+- Tests added, accessibility notes
+- Any gotchas or important context
 
-### 9. CLOSE
-- After QA approval + Documentation complete
-- Task transitions to "completed" automatically
-- Return to SCAN: `roboco_task_scan()` or `roboco_agent_idle()`
+```python
+roboco_task_submit_qa(task_id, {
+    "dev_notes": "Built modal component with form validation. Used React Hook Form for state. Added 8 tests covering all states.",
+    "handoff_summary": "UserPreferencesModal in src/components/modals/. Accessibility: focus trap, escape key, aria labels."
+})
+```
+
+**Tool:** `roboco_journal_reflect(data)` (Personal - QA cannot see this)
+
+Document what you did, learned, struggled with for your own growth.
+
+### 9. DONE
+After you submit for QA, the task flows through:
+1. **QA** reviews and passes/fails
+2. **Documenter** writes docs
+3. **Cell PM** reviews and completes
+
+Return to SCAN: `roboco_task_scan()` or `roboco_agent_idle()`
 
 ## Communication Rules