External/roboco
1
0
Fork 0
mirror of https://github.com/rennf93/roboco.git synced 2026-08-03 07:23:24 +02:00
Code Issues Packages Projects Releases Wiki Activity

feat(sessions): Session-Task linking with scoped context management

Browse Source 
Major feature: Sessions are now linked to tasks with smart routing and context loading, ensuring agents have proper discussion context.

## Session-Task Relationship (Many-to-Many)
  - Added SessionTaskTable junction table linking sessions to tasks
  - Sessions can link to multiple tasks, tasks can have multiple sessions
  - is_primary flag marks the main discussion session for a task
  - relationship_type: discussion, planning, review, retrospective
  - Subtasks auto-inherit parent task's session

## BACKLOG Status + Activation Flow
  - Tasks now created with BACKLOG status (not PENDING)
  - PMs must create session BEFORE activating task
  - roboco_task_activate() transitions BACKLOG → PENDING
  - Prevents race condition where dev starts before session exists
  - Flow: CREATE (backlog) → SESSION → ACTIVATE (pending) → spawn

## Session Scopes
  - SessionScope enum: initiative, cell, task
  - initiative: Cross-cell coordination (Main PM, #dev-all)
  - cell: Cell-specific work (Cell PM default)
  - task: Individual task execution (dev level)
  - Enables future smart context loading by scope

## Message Routing to Task Sessions
  - When task_id provided in roboco_message_send(), routes to task's primary session instead of channel's active session
  - New API endpoint: GET /sessions/for-task/{task_id}
  - TaskResponse now includes linked sessions array

## Dev Session Access
  - New tool: roboco_session_history_for_task(task_id)
  - Devs can now see their task's discussion history
  - Messages tagged with task_id for filtering

## Communication Guidelines
  - Added "When to Post / When NOT to Post" to all 9 agent blueprints
  - Devs/QA/Doc should use task tools for status, journal for reasoning
  - Sessions reserved for coordination that needs response
  - Reduces noise: no "Starting work" or "Made progress" chat messages

Files changed:
  - DB: SessionTaskTable, SessionScope column
  - Services: messaging.py (linking), task.py (activation)
  - MCP: 5 new session tools, message routing update
  - API: session-task endpoints, TaskResponse sessions
  - Blueprints: All 13 updated with session/activation workflow
This commit is contained in:
Renn F
2025-12-22 18:04:31 +01:00
parent 4e06bdb842
commit b7611c24fc
36 changed files with 2118 additions and 92 deletions
Download Patch File Download Diff File Expand all files Collapse all files
agents/blueprints/backend/be-qa.md
+16 -9
View File
@@ -227,15 +227,22 @@ After verdict:
- **#announcements** (read only) - Company announcements
- **#all-hands** (read/write) - Company-wide discussion
### How to Communicate
Use `roboco_message_send(data)`:
```json
{
"channel_slug": "backend-cell",
"content": "Testing TASK-XXX: Found issue with null handling...",
"message_type": "technical"
}
```
### When to Post in Session (DO)
- **Questions about implementation** - Need dev clarification on behavior
- **Critical bugs** - Security issues, data loss, blockers
- **Decisions needing input** - Edge cases with unclear expected behavior
- **Cross-cell patterns** - Issues you're seeing across cells
### When NOT to Post (USE OTHER TOOLS)
- ❌ "Starting QA on X" → Orchestrator knows, task status tracks this
- ❌ "Testing in progress" → Use `roboco_task_progress()` instead
- ❌ "Completed QA" → Use `roboco_qa_pass()`/`roboco_qa_fail()` instead
- ❌ Internal test notes → Use `roboco_journal_*()` instead
- ❌ Minor issues → Put in QA verdict notes, not session chat
**Rule of thumb:** Only post if you need a response from dev/PM, or if
the issue affects other tasks. The orchestrator spawns you with full
context including dev's handoff notes.
### You CANNOT
- Send formal notifications (only PMs can)