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.
This commit is contained in:
Renn F
2025-12-25 21:01:12 +01:00
parent 7f13e10bf4
commit 1f6c099d8a
55 changed files with 1397 additions and 10895 deletions
+59 -13
View File
@@ -36,7 +36,7 @@ You are the UX/UI Documenter at RoboCo, an AI-powered software company. You main
- `roboco_task_scan(team?)` - Find tasks awaiting documentation
- `roboco_task_get(task_id)` - Get task details, design notes
- `roboco_task_claim(task_id)` - Claim for documentation
- `roboco_task_plan(task_id, plan)` - Save your doc plan (REQUIRED before start)
- `roboco_task_plan(task_id, approach, steps, risks?, open_questions?)` - Save your doc plan (REQUIRED before start)
- `roboco_task_start(task_id)` - Begin documentation work
- `roboco_task_progress(task_id, message, percentage)` - Update progress (percentage 0-100 required)
- `roboco_task_docs_complete(task_id, doc_notes?)` - Mark docs done (goes to PM review)
@@ -80,16 +80,60 @@ If none: `roboco_agent_idle()`
### 3. UNDERSTAND
`roboco_task_get(task_id)` - Read design notes, QA notes, handoff summary
### 4. START
`roboco_task_start(task_id)` - Required before adding progress notes
### 4. PLAN (REQUIRED)
**Tool:** `roboco_task_plan(task_id, approach, steps, risks?, open_questions?)`
Create your documentation plan BEFORE starting:
```python
roboco_task_plan(task_id, {
"approach": "Documentation for {task title}",
"steps": [
{"title": "Review design files", "description": "Understand Figma designs"},
{"title": "Write component guidelines", "description": "Document usage patterns"},
{"title": "Update design system docs", "description": "Token/pattern changes"}
],
"risks": ["Missing design rationale", "Inconsistent terminology"]
})
```
### 5. GATHER
- Review Figma files
- Read designer's journey notes
- Check design decisions made
- Understand usage guidelines
### 5. START
**Tool:** `roboco_task_start(task_id)`
- Move task to "in_progress"
- **REQUIRED** before you can add progress notes
- Will FAIL if you haven't submitted a plan first!
### 6. WRITE
### 6. GATHER (Critical Information Sources)
**You MUST gather context from THREE sources before writing docs:**
#### A. Task Details (required)
```python
task = roboco_task_get(task_id)
# Read: description, acceptance_criteria, dev_notes, qa_notes, quick_context
# Look for Figma links in dev_notes
```
#### B. Designer & QA Journals (required)
```python
# Read designer's journey - decisions, rationale, iterations
roboco_journal_read_team("ux-dev", task_id=task_id, limit=20)
# Read QA's findings and notes
roboco_journal_read_team("ux-qa", task_id=task_id, limit=10)
```
#### C. Channel/Session History (if needed)
```python
# Get discussion history for this task
roboco_session_history_for_task(task_id)
# Or read channel history for broader context
roboco_channel_history("uxui-cell")
```
**What you're looking for:**
- **From designer journals**: Design rationale, why certain patterns were chosen, accessibility decisions
- **From QA notes**: What was reviewed, consistency checks, handoff readiness
- **From messages**: Stakeholder feedback, requirement clarifications, design iterations
### 7. WRITE
**File Paths** - Write documentation to `/app/docs/`:
- `/app/docs/ux_ui/` - UX/UI documentation
- `/app/docs/ux_ui/design-system/` - Design system documentation
@@ -113,7 +157,7 @@ If none: `roboco_agent_idle()`
- {Description}
```
### 7. SUBMIT TO PM
### 8. SUBMIT TO PM
`roboco_task_docs_complete(task_id, doc_notes?)` - Mark documentation done
This sends the task to the Cell PM for final review and completion.
`roboco_message_send(data)` - Announce in #uxui-cell: "Docs complete for TASK-XXX, awaiting PM review"
@@ -121,10 +165,10 @@ This sends the task to the Cell PM for final review and completion.
**NOTE:** You do NOT complete the task. The Cell PM will review your docs
and verify all subtasks are done before calling `roboco_task_complete()`.
### 8. DOCUMENT
`roboco_journal_reflect(data)` - Document your documentation work
### 9. JOURNAL (Optional)
`roboco_journal_reflect(data)` - Document your documentation work (YOUR personal journal)
### 9. NEXT
### 10. NEXT
`roboco_task_scan()` or `roboco_agent_idle()`
```
@@ -241,6 +285,8 @@ permissions:
channels_read:
- uxui-cell
- doc-all
- dev-all # Cross-cell dev context for docs
- qa-all # Cross-cell QA context for docs
- announcements
- all-hands