WIP almost done with track planning

This commit is contained in:
2026-03-06 15:00:15 -05:00
parent 2c90020682
commit 3b79f2a4e1
77 changed files with 1186 additions and 674 deletions

View File

@@ -0,0 +1,9 @@
# Per-Ticket Model Override
**Track ID:** per_ticket_model_20260306
**Status:** Planned
**See Also:**
- [Spec](./spec.md)
- [Plan](./plan.md)

View File

@@ -0,0 +1,9 @@
{
"id": "per_ticket_model_20260306",
"name": "Per-Ticket Model Override",
"status": "planned",
"created_at": "2026-03-06T00:00:00Z",
"updated_at": "2026-03-06T00:00:00Z",
"type": "feature",
"priority": "medium"
}

View File

@@ -1,16 +1,32 @@
# Implementation Plan: Per-Ticket Model Override (per_ticket_model)
# Implementation Plan: Per-Ticket Model Override (per_ticket_model_20260306)
## Phase 1: Research & Design
- [ ] Task: Analyze existing backend implementation
- [ ] Task: Design GUI/UX approach
- [ ] Task: Conductor - User Manual Verification
## Phase 1: Model Field
- [ ] Task: Initialize MMA Environment
- [ ] Task: Add override field
- WHERE: src/models.py
- WHAT: model_override on Ticket
- HOW: Optional[str]
- [ ] Task: Update ticket creation
- WHERE: src/conductor_tech_lead.py
- WHAT: Pass override to ticket
- HOW: Include in ticket dict
## Phase 2: Implementation
- [ ] Task: Implement feature
- [ ] Task: Write tests
- [ ] Task: Conductor - User Manual Verification
## Phase 2: UI Controls
- [ ] Task: Add model dropdown
- WHERE: src/gui_2.py
- WHAT: Select model per ticket
- HOW: imgui.combo with model list
- [ ] Task: Add override indicator
- WHERE: src/gui_2.py
- WHAT: Show override is active
- HOW: Different style
## Phase 3: Verification
- [ ] Task: Run test suite
- [ ] Task: Verify coverage
- [ ] Task: Conductor - Phase Completion Verification
## Phase 3: Execution Integration
- [ ] Task: Use override at runtime
- WHERE: src/multi_agent_conductor.py
- WHAT: Use ticket.model_override if set
- HOW: Check and apply
## Phase 4: Verification
- [ ] Test override works
- [ ] Conductor - Phase Verification

View File

@@ -1,27 +1,21 @@
# Track Specification: Per-Ticket Model Override
# Track Specification: Per-Ticket Model Override (per_ticket_model_20260306)
## Overview
Allow manual model selection per ticket.
Allow user to manually select which model to use for a specific ticket, overriding the default tier model. Useful for forcing smarter model on hard tickets.
## Current State Audit
### Already Implemented
- Model selection per tier
- Ticket model field
### Gaps to Fill
- No per-ticket override UI
- No model picker
## Goals
- Model dropdown per ticket
- Override default tier model
- Clear override indication
## Architectural Constraints
- **Validation**: Selected model MUST be valid and available.
- **Clear Override**: Override MUST be visually distinct.
## Functional Requirements
- Model picker UI
- Override flag
- Model validation
- **Model Dropdown**: Select model per ticket.
- **Override Flag**: Mark ticket as using override.
- **Clear Indicator**: Visual show override is active.
- **Reset Option**: Remove override and revert to tier default.
## Non-Functional Requirements
- Valid model list
- Clear indication of override
## Acceptance Criteria
- [ ] Model dropdown works.
- [ ] Override saves correctly.
- [ ] Visual indicator shows override.
- [ ] Reset returns to default.
- [ ] Override used during execution.