Fix list_tasks response size - remove verbose fields

Tinker

Home Epics Fix list_tasks response size - remove verbose fieldsEdit

Cancel

Title *

Project *

Description

## Problem
The `list_tasks` MCP tool returns ~110KB of JSON even with `limit: 20`, wasting tokens and causing slow responses.

## Root Cause
The list response includes verbose fields:
1. `comments` - Contains full code reviews + nested `agent` objects
2. `working_memory` - Can accumulate large data
3. `dependencies` - Empty most of the time
4. `acceptance_criteria` - Not used, should be removed from system
5. `technical_constraints` - Not used, should be removed from system

## Solution

### Part 1: Fix list_tasks response
Remove from list view (agents can use `get_ticket(id)` for full details):
- `comments` (contains large code reviews + agent objects)
- `working_memory` (can be large)
- `dependencies` (usually empty)

Keep in list view:
- `id`, `ticket_type`, `title`, `status`, `priority`
- `parent_id`, `project_id`
- `created_at`, `updated_at`
- `description` (useful context for list view)
- `pull_request_url`, `ci_status`
- `archived`, `is_blocked`, `subtask_count`
- `available_transitions`

### Part 2: Remove unused fields from entire system
- Remove `acceptance_criteria` column from tickets table
- Remove `technical_constraints` column from tickets table

## Files to Modify
- Ticket serializer/index action (list view)
- Database migration for dropping columns
- Update any code that references these fields

## Acceptance Criteria
1. list_tasks with limit=20 returns <10KB of JSON
2. `acceptance_criteria` and `technical_constraints` columns removed from database
3. No code references to removed fields