WIP next tracks planing
This commit is contained in:
@@ -1,33 +1,26 @@
|
||||
# Track Specification: Cache Analytics Display
|
||||
|
||||
## Overview
|
||||
Implement cache analytics display for Manual Slop application.
|
||||
Gemini cache hit/miss visualization and TTL status.
|
||||
|
||||
## Current State Audit
|
||||
### Already Implemented (DO NOT re-implement)
|
||||
- Existing backend functionality in src/ modules
|
||||
- Test coverage for core features
|
||||
### Already Implemented
|
||||
- get_gemini_cache_stats() in ai_client.py
|
||||
- Cache creation/deletion
|
||||
|
||||
### Gaps to Fill (This Track Scope)
|
||||
This track addresses the gap between backend implementation and user-facing GUI/control.
|
||||
### Gaps to Fill
|
||||
- No GUI display
|
||||
- No hit/miss tracking
|
||||
|
||||
## Goals
|
||||
- Implement cache analytics display
|
||||
- Ensure test coverage
|
||||
- Follow existing code patterns
|
||||
- Cache status panel
|
||||
- Hit/miss ratio
|
||||
- TTL countdown
|
||||
|
||||
## Functional Requirements
|
||||
- User-facing functionality as described in TASKS.md
|
||||
- Integration with existing backend
|
||||
- Cache size display
|
||||
- TTL visualization
|
||||
- Manual cache clear
|
||||
|
||||
## Non-Functional Requirements
|
||||
- Performance: Maintain UI responsiveness
|
||||
- Tests: >80% coverage for new code
|
||||
|
||||
## Architecture Reference
|
||||
- docs/guide_architecture.md
|
||||
- docs/guide_mma.md
|
||||
- docs/guide_tools.md
|
||||
|
||||
## Out of Scope
|
||||
- Major refactoring of unrelated systems
|
||||
- Non-blocking UI updates
|
||||
|
||||
@@ -1,33 +1,28 @@
|
||||
# Track Specification: Cost & Token Analytics Panel
|
||||
|
||||
## Overview
|
||||
Implement cost & token analytics panel for Manual Slop application.
|
||||
Real-time cost tracking panel for API usage by model and tier.
|
||||
|
||||
## Current State Audit
|
||||
### Already Implemented (DO NOT re-implement)
|
||||
- Existing backend functionality in src/ modules
|
||||
- Test coverage for core features
|
||||
### Already Implemented
|
||||
- cost_tracker.py with MODEL_PRICING
|
||||
- estimate_cost() function
|
||||
- Token tracking in ai_client.py
|
||||
|
||||
### Gaps to Fill (This Track Scope)
|
||||
This track addresses the gap between backend implementation and user-facing GUI/control.
|
||||
### Gaps to Fill
|
||||
- No GUI panel for cost display
|
||||
- No session totals
|
||||
|
||||
## Goals
|
||||
- Implement cost & token analytics panel
|
||||
- Ensure test coverage
|
||||
- Follow existing code patterns
|
||||
- Cost per model display
|
||||
- Session totals
|
||||
- Breakdown by tier
|
||||
|
||||
## Functional Requirements
|
||||
- User-facing functionality as described in TASKS.md
|
||||
- Integration with existing backend
|
||||
- Real-time cost updates
|
||||
- Per-model breakdown
|
||||
- Tier breakdown
|
||||
|
||||
## Non-Functional Requirements
|
||||
- Performance: Maintain UI responsiveness
|
||||
- Tests: >80% coverage for new code
|
||||
|
||||
## Architecture Reference
|
||||
- docs/guide_architecture.md
|
||||
- docs/guide_mma.md
|
||||
- docs/guide_tools.md
|
||||
|
||||
## Out of Scope
|
||||
- Major refactoring of unrelated systems
|
||||
- <10ms update latency
|
||||
- Clear visual formatting
|
||||
|
||||
@@ -1,33 +1,28 @@
|
||||
# Track Specification: Deep AST-Driven Context Pruning (RAG for Code)
|
||||
# Track Specification: Deep AST-Driven Context Pruning
|
||||
|
||||
## Overview
|
||||
Implement deep ast-driven context pruning (rag for code) for Manual Slop application.
|
||||
Use tree_sitter to parse target file AST and inject condensed skeletons into worker prompts.
|
||||
|
||||
## Current State Audit
|
||||
### Already Implemented (DO NOT re-implement)
|
||||
- Existing backend functionality in src/ modules
|
||||
- Test coverage for core features
|
||||
### Already Implemented
|
||||
- file_cache.py with skeleton generation
|
||||
- outline_tool.py for code outlines
|
||||
- AST-based file analysis
|
||||
|
||||
### Gaps to Fill (This Track Scope)
|
||||
This track addresses the gap between backend implementation and user-facing GUI/control.
|
||||
### Gaps to Fill
|
||||
- No automatic AST pruning based on edit target
|
||||
- Skeletons not customizable by user
|
||||
|
||||
## Goals
|
||||
- Implement deep ast-driven context pruning (rag for code)
|
||||
- Ensure test coverage
|
||||
- Follow existing code patterns
|
||||
- Parse target file AST before worker dispatch
|
||||
- Strip unrelated function bodies
|
||||
- Inject surgical skeleton to reduce tokens
|
||||
|
||||
## Functional Requirements
|
||||
- User-facing functionality as described in TASKS.md
|
||||
- Integration with existing backend
|
||||
- tree_sitter integration
|
||||
- Target function/method detection
|
||||
- Configurable skeleton depth
|
||||
|
||||
## Non-Functional Requirements
|
||||
- Performance: Maintain UI responsiveness
|
||||
- Tests: >80% coverage for new code
|
||||
|
||||
## Architecture Reference
|
||||
- docs/guide_architecture.md
|
||||
- docs/guide_mma.md
|
||||
- docs/guide_tools.md
|
||||
|
||||
## Out of Scope
|
||||
- Major refactoring of unrelated systems
|
||||
- <100ms parsing time per file
|
||||
- >50% token reduction target
|
||||
|
||||
@@ -1,33 +1,27 @@
|
||||
# Track Specification: Kill/Abort Running Workers
|
||||
|
||||
## Overview
|
||||
Implement kill/abort running workers for Manual Slop application.
|
||||
Add ability to kill/abort running Tier 3 workers mid-execution.
|
||||
|
||||
## Current State Audit
|
||||
### Already Implemented (DO NOT re-implement)
|
||||
- Existing backend functionality in src/ modules
|
||||
- Test coverage for core features
|
||||
### Already Implemented
|
||||
- Worker lifecycle in multi_agent_conductor.py
|
||||
- Thread-based execution
|
||||
|
||||
### Gaps to Fill (This Track Scope)
|
||||
This track addresses the gap between backend implementation and user-facing GUI/control.
|
||||
### Gaps to Fill
|
||||
- No kill mechanism
|
||||
- Workers run to completion
|
||||
|
||||
## Goals
|
||||
- Implement kill/abort running workers
|
||||
- Ensure test coverage
|
||||
- Follow existing code patterns
|
||||
- Kill button per worker
|
||||
- Forced termination
|
||||
- Graceful abort option
|
||||
|
||||
## Functional Requirements
|
||||
- User-facing functionality as described in TASKS.md
|
||||
- Integration with existing backend
|
||||
- Thread termination
|
||||
- Cleanup handlers
|
||||
- Confirmation dialog
|
||||
|
||||
## Non-Functional Requirements
|
||||
- Performance: Maintain UI responsiveness
|
||||
- Tests: >80% coverage for new code
|
||||
|
||||
## Architecture Reference
|
||||
- docs/guide_architecture.md
|
||||
- docs/guide_mma.md
|
||||
- docs/guide_tools.md
|
||||
|
||||
## Out of Scope
|
||||
- Major refactoring of unrelated systems
|
||||
- Clean resource release
|
||||
- No zombie processes
|
||||
|
||||
@@ -1,33 +1,26 @@
|
||||
# Track Specification: Manual Block/Unblock Control
|
||||
|
||||
## Overview
|
||||
Implement manual block/unblock control for Manual Slop application.
|
||||
Manually block/unblock tickets with custom reasons.
|
||||
|
||||
## Current State Audit
|
||||
### Already Implemented (DO NOT re-implement)
|
||||
- Existing backend functionality in src/ modules
|
||||
- Test coverage for core features
|
||||
### Already Implemented
|
||||
- Ticket blocked status
|
||||
- Dependency-based blocking
|
||||
|
||||
### Gaps to Fill (This Track Scope)
|
||||
This track addresses the gap between backend implementation and user-facing GUI/control.
|
||||
### Gaps to Fill
|
||||
- No manual override
|
||||
- No custom reasons
|
||||
|
||||
## Goals
|
||||
- Implement manual block/unblock control
|
||||
- Ensure test coverage
|
||||
- Follow existing code patterns
|
||||
- Manual block with reason
|
||||
- Unblock button
|
||||
- Block reason display
|
||||
|
||||
## Functional Requirements
|
||||
- User-facing functionality as described in TASKS.md
|
||||
- Integration with existing backend
|
||||
- Block/unblock actions
|
||||
- Reason field
|
||||
- Visual blocked indicator
|
||||
|
||||
## Non-Functional Requirements
|
||||
- Performance: Maintain UI responsiveness
|
||||
- Tests: >80% coverage for new code
|
||||
|
||||
## Architecture Reference
|
||||
- docs/guide_architecture.md
|
||||
- docs/guide_mma.md
|
||||
- docs/guide_tools.md
|
||||
|
||||
## Out of Scope
|
||||
- Major refactoring of unrelated systems
|
||||
- Clear block indication
|
||||
|
||||
@@ -1,33 +1,26 @@
|
||||
# Track Specification: Manual Skeleton Context Injection
|
||||
|
||||
## Overview
|
||||
Implement manual skeleton context injection for Manual Slop application.
|
||||
UI controls to manually flag files for skeleton injection.
|
||||
|
||||
## Current State Audit
|
||||
### Already Implemented (DO NOT re-implement)
|
||||
- Existing backend functionality in src/ modules
|
||||
- Test coverage for core features
|
||||
### Already Implemented
|
||||
- Auto-generated skeletons for workers
|
||||
- file_cache skeleton generation
|
||||
|
||||
### Gaps to Fill (This Track Scope)
|
||||
This track addresses the gap between backend implementation and user-facing GUI/control.
|
||||
### Gaps to Fill
|
||||
- No manual file selection
|
||||
- No def-level control
|
||||
|
||||
## Goals
|
||||
- Implement manual skeleton context injection
|
||||
- Ensure test coverage
|
||||
- Follow existing code patterns
|
||||
- File picker for skeleton injection
|
||||
- Manual skeleton refresh
|
||||
- Def-level granularity
|
||||
|
||||
## Functional Requirements
|
||||
- User-facing functionality as described in TASKS.md
|
||||
- Integration with existing backend
|
||||
- File browser integration
|
||||
- Skeleton regeneration trigger
|
||||
- Context preview
|
||||
|
||||
## Non-Functional Requirements
|
||||
- Performance: Maintain UI responsiveness
|
||||
- Tests: >80% coverage for new code
|
||||
|
||||
## Architecture Reference
|
||||
- docs/guide_architecture.md
|
||||
- docs/guide_mma.md
|
||||
- docs/guide_tools.md
|
||||
|
||||
## Out of Scope
|
||||
- Major refactoring of unrelated systems
|
||||
- Fast skeleton generation
|
||||
|
||||
5
conductor/tracks/manual_ux_validation_20260302/index.md
Normal file
5
conductor/tracks/manual_ux_validation_20260302/index.md
Normal file
@@ -0,0 +1,5 @@
|
||||
# Track manual_ux_validation_20260302 Context
|
||||
|
||||
- [Specification](./spec.md)
|
||||
- [Implementation Plan](./plan.md)
|
||||
- [Metadata](./metadata.json)
|
||||
@@ -0,0 +1,8 @@
|
||||
{
|
||||
"track_id": "manual_ux_validation_20260302",
|
||||
"type": "feature",
|
||||
"status": "new",
|
||||
"created_at": "2026-03-02T22:40:00Z",
|
||||
"updated_at": "2026-03-02T22:40:00Z",
|
||||
"description": "Highly interactive human-in-the-loop track to review and adjust GUI UX, animations, popups, and layout structures based on slow-interval simulation feedback."
|
||||
}
|
||||
43
conductor/tracks/manual_ux_validation_20260302/plan.md
Normal file
43
conductor/tracks/manual_ux_validation_20260302/plan.md
Normal file
@@ -0,0 +1,43 @@
|
||||
# Implementation Plan: Manual UX Validation & Polish (manual_ux_validation_20260302)
|
||||
|
||||
> **TEST DEBT NOTE:** This track is explicitly manual/visual and naturally bypasses the current `live_gui` automated testing debt (documented in `test_architecture_integrity_audit_20260304`).
|
||||
|
||||
## Phase 1: Observation Harness Setup
|
||||
- [ ] Task: Initialize MMA Environment `activate_skill mma-orchestrator`
|
||||
- [ ] Task: Create Slow-Mode Simulation
|
||||
- [ ] WHERE: `simulation/` directory
|
||||
- [ ] WHAT: Create `ux_observation_sim.py` that executes a standard workflow but with forced 3-5 second delays between actions to allow the user to watch the GUI respond.
|
||||
- [ ] HOW: Use `ApiHookClient` with heavy `time.sleep()` blocks specifically designed for human observation (exempt from the fast-test rule).
|
||||
- [ ] SAFETY: Keep this script strictly separate from the automated test suite.
|
||||
- [ ] Task: Conductor - User Manual Verification 'Phase 1: Observation Harness' (Protocol in workflow.md)
|
||||
|
||||
## Phase 2: Structural Layout & Organization
|
||||
- [ ] Task: Interactive Layout Iteration
|
||||
- [ ] WHERE: `gui_2.py`
|
||||
- [ ] WHAT: Work live with the user to shift UI elements between Tabs, Panels, and Collapsing Headers. Focus on logical grouping of AI settings, operations, and logs.
|
||||
- [ ] HOW: Rapidly apply changes requested by the user and re-render.
|
||||
- [ ] SAFETY: Avoid breaking data bindings during structural moves.
|
||||
- [ ] Task: Conductor - User Manual Verification 'Phase 2: Layout Finalization' (Protocol in workflow.md)
|
||||
|
||||
## Phase 3: Animations, Knobs & Visual Feedback
|
||||
- [ ] Task: Tune Blinking & State Animations
|
||||
- [ ] WHERE: `gui_2.py`
|
||||
- [ ] WHAT: Adjust `math.sin(time.time() * X)` frequencies, color vectors, and trigger conditions for "streaming", "working", and "error" states.
|
||||
- [ ] HOW: Modify rendering loops based on user feedback.
|
||||
- [ ] SAFETY: None.
|
||||
- [ ] Task: Refine Controls & Knobs
|
||||
- [ ] WHERE: `gui_2.py`
|
||||
- [ ] WHAT: Evaluate the placement and feel of sliders, combo boxes, and buttons.
|
||||
- [ ] HOW: Adjust ImGui spacing, item widths, and same-line alignments.
|
||||
- [ ] SAFETY: None.
|
||||
- [ ] Task: Conductor - User Manual Verification 'Phase 3: Visual Polish' (Protocol in workflow.md)
|
||||
|
||||
## Phase 4: Popup Behavior & Final Sign-off
|
||||
- [ ] Task: Implement Auto-Close Popups
|
||||
- [ ] WHERE: `gui_2.py`
|
||||
- [ ] WHAT: Review existing popups. Implement a timer mechanism (e.g., comparing `time.time()` against a trigger time) to automatically close specific informational popups after N seconds.
|
||||
- [ ] HOW: Add timer state to `app_instance` and use `imgui.close_current_popup()` conditionally.
|
||||
- [ ] SAFETY: Do not auto-close critical confirmation dialogs (like file write approvals).
|
||||
- [ ] Task: Final UX Sign-off
|
||||
- [ ] Ask the user for a final comprehensive review of the application's feel.
|
||||
- [ ] Task: Conductor - User Manual Verification 'Phase 4: Final Sign-off' (Protocol in workflow.md)
|
||||
22
conductor/tracks/manual_ux_validation_20260302/spec.md
Normal file
22
conductor/tracks/manual_ux_validation_20260302/spec.md
Normal file
@@ -0,0 +1,22 @@
|
||||
# Track Specification: Manual UX Validation & Polish (manual_ux_validation_20260302)
|
||||
|
||||
## Overview
|
||||
This track is an unusual, highly interactive human-in-the-loop review session. The user will act as the primary QA and Designer, manually using the GUI and observing it during slow-interval simulation runs. The goal is to aggressively iterate on the "feel" of the application: analyzing blinking animations, structural decisions (Tabs vs. Panels vs. Collapsing Headers), knob/control placements, and the efficacy of popups (including adding auto-close timers).
|
||||
|
||||
## Architectural Constraints: The "Immediate Mode Iteration Contract"
|
||||
- **Rapid Prototyping**: This track bypasses strict TDD for layout changes to allow the user to rapidly see and "feel" UI adjustments.
|
||||
- **View-Only Changes**: Refactoring MUST remain confined to the GUI layer (`gui_2.py` or the future `app_controller.py` if decoupled). State machine logic should not be altered unless directly required for a visual effect (like an animation timer).
|
||||
- **Simulation Harness**: Changes must be observable via a specialized slow-mode simulation that gives the user time to watch state transitions.
|
||||
|
||||
## Functional Requirements
|
||||
- **Slow-Mode Observation**: Create or modify a simulation script to run with deliberately long delays (e.g., 3-5 seconds between AI actions) so the user can observe UI states.
|
||||
- **Layout Restructuring**: Adjust the hierarchy of Tabs, Panels, and Collapsing Headers iteratively based on user feedback during the session.
|
||||
- **Animation & Feedback**: Tune blinking animations (frequency, color) and visual cues for AI activity and user input.
|
||||
- **Popup Behavior**: Review all error and confirmation popups. Implement timed auto-close logic for non-critical informational popups.
|
||||
|
||||
## Acceptance Criteria
|
||||
- [ ] A slow-interval observation simulation exists and functions.
|
||||
- [ ] Structural layout (Tabs/Panels/Headers) is finalized and explicitly approved by the user.
|
||||
- [ ] Animations and visual feedback triggers feel responsive and intuitive to the user.
|
||||
- [ ] Popup behaviors (including any new auto-close timers) are implemented and approved.
|
||||
- [ ] Final explicit sign-off from the user on the overall GUI UX.
|
||||
@@ -1,33 +1,28 @@
|
||||
# Track Specification: MMA Multi-Worker Visualization
|
||||
|
||||
## Overview
|
||||
Implement mma multi-worker visualization for Manual Slop application.
|
||||
Split-view GUI for parallel worker streams per tier.
|
||||
|
||||
## Current State Audit
|
||||
### Already Implemented (DO NOT re-implement)
|
||||
- Existing backend functionality in src/ modules
|
||||
- Test coverage for core features
|
||||
### Already Implemented
|
||||
- mma_streams in app_controller.py
|
||||
- Tier source tagging
|
||||
|
||||
### Gaps to Fill (This Track Scope)
|
||||
This track addresses the gap between backend implementation and user-facing GUI/control.
|
||||
### Gaps to Fill
|
||||
- Single stream display only
|
||||
- No per-worker status
|
||||
- No kill/restart controls
|
||||
|
||||
## Goals
|
||||
- Implement mma multi-worker visualization
|
||||
- Ensure test coverage
|
||||
- Follow existing code patterns
|
||||
- Split view per worker
|
||||
- Individual status/output tabs
|
||||
- Kill/restart per worker
|
||||
|
||||
## Functional Requirements
|
||||
- User-facing functionality as described in TASKS.md
|
||||
- Integration with existing backend
|
||||
- Multi-pane layout
|
||||
- Worker lifecycle controls
|
||||
- Output streaming per worker
|
||||
|
||||
## Non-Functional Requirements
|
||||
- Performance: Maintain UI responsiveness
|
||||
- Tests: >80% coverage for new code
|
||||
|
||||
## Architecture Reference
|
||||
- docs/guide_architecture.md
|
||||
- docs/guide_mma.md
|
||||
- docs/guide_tools.md
|
||||
|
||||
## Out of Scope
|
||||
- Major refactoring of unrelated systems
|
||||
- Handle 4+ concurrent workers
|
||||
- Graceful termination
|
||||
|
||||
@@ -1,33 +1,27 @@
|
||||
# Track Specification: Transitioning to Native Orchestrator
|
||||
# Track Specification: Native Orchestrator
|
||||
|
||||
## Overview
|
||||
Implement transitioning to native orchestrator for Manual Slop application.
|
||||
Absorb mma_exec.py into core app for pure Python MMA orchestration.
|
||||
|
||||
## Current State Audit
|
||||
### Already Implemented (DO NOT re-implement)
|
||||
- Existing backend functionality in src/ modules
|
||||
- Test coverage for core features
|
||||
### Already Implemented
|
||||
- mma_exec.py for tier delegation
|
||||
- ConductorEngine in multi_agent_conductor.py
|
||||
|
||||
### Gaps to Fill (This Track Scope)
|
||||
This track addresses the gap between backend implementation and user-facing GUI/control.
|
||||
### Gaps to Fill
|
||||
- External CLI dependency
|
||||
- No native plan.md management
|
||||
|
||||
## Goals
|
||||
- Implement transitioning to native orchestrator
|
||||
- Ensure test coverage
|
||||
- Follow existing code patterns
|
||||
- Read/write plan.md natively
|
||||
- Manage metadata.json in Python
|
||||
- Remove mma_exec.py dependency
|
||||
|
||||
## Functional Requirements
|
||||
- User-facing functionality as described in TASKS.md
|
||||
- Integration with existing backend
|
||||
- Plan file CRUD operations
|
||||
- Metadata management
|
||||
- Tier delegation in-process
|
||||
|
||||
## Non-Functional Requirements
|
||||
- Performance: Maintain UI responsiveness
|
||||
- Tests: >80% coverage for new code
|
||||
|
||||
## Architecture Reference
|
||||
- docs/guide_architecture.md
|
||||
- docs/guide_mma.md
|
||||
- docs/guide_tools.md
|
||||
|
||||
## Out of Scope
|
||||
- Major refactoring of unrelated systems
|
||||
- Backward compatible with existing tracks
|
||||
- No breaking changes to API
|
||||
|
||||
@@ -1,33 +1,26 @@
|
||||
# Track Specification: On-Demand Definition Lookup
|
||||
|
||||
## Overview
|
||||
Implement on-demand definition lookup for Manual Slop application.
|
||||
Agent can request specific class/function definitions during discussion.
|
||||
|
||||
## Current State Audit
|
||||
### Already Implemented (DO NOT re-implement)
|
||||
- Existing backend functionality in src/ modules
|
||||
- Test coverage for core features
|
||||
### Already Implemented
|
||||
- outline_tool.py for definitions
|
||||
- py_get_definition tool
|
||||
|
||||
### Gaps to Fill (This Track Scope)
|
||||
This track addresses the gap between backend implementation and user-facing GUI/control.
|
||||
### Gaps to Fill
|
||||
- No @mention syntax
|
||||
- No inline display
|
||||
|
||||
## Goals
|
||||
- Implement on-demand definition lookup
|
||||
- Ensure test coverage
|
||||
- Follow existing code patterns
|
||||
- @symbol lookup syntax
|
||||
- Inline definition display
|
||||
- Auto-fetch on unknown symbols
|
||||
|
||||
## Functional Requirements
|
||||
- User-facing functionality as described in TASKS.md
|
||||
- Integration with existing backend
|
||||
- Symbol parsing
|
||||
- Definition retrieval
|
||||
- Inline rendering
|
||||
|
||||
## Non-Functional Requirements
|
||||
- Performance: Maintain UI responsiveness
|
||||
- Tests: >80% coverage for new code
|
||||
|
||||
## Architecture Reference
|
||||
- docs/guide_architecture.md
|
||||
- docs/guide_mma.md
|
||||
- docs/guide_tools.md
|
||||
|
||||
## Out of Scope
|
||||
- Major refactoring of unrelated systems
|
||||
- Quick lookup (<100ms)
|
||||
|
||||
@@ -1,33 +1,27 @@
|
||||
# Track Specification: Per-Ticket Model Override
|
||||
|
||||
## Overview
|
||||
Implement per-ticket model override for Manual Slop application.
|
||||
Allow manual model selection per ticket.
|
||||
|
||||
## Current State Audit
|
||||
### Already Implemented (DO NOT re-implement)
|
||||
- Existing backend functionality in src/ modules
|
||||
- Test coverage for core features
|
||||
### Already Implemented
|
||||
- Model selection per tier
|
||||
- Ticket model field
|
||||
|
||||
### Gaps to Fill (This Track Scope)
|
||||
This track addresses the gap between backend implementation and user-facing GUI/control.
|
||||
### Gaps to Fill
|
||||
- No per-ticket override UI
|
||||
- No model picker
|
||||
|
||||
## Goals
|
||||
- Implement per-ticket model override
|
||||
- Ensure test coverage
|
||||
- Follow existing code patterns
|
||||
- Model dropdown per ticket
|
||||
- Override default tier model
|
||||
- Clear override indication
|
||||
|
||||
## Functional Requirements
|
||||
- User-facing functionality as described in TASKS.md
|
||||
- Integration with existing backend
|
||||
- Model picker UI
|
||||
- Override flag
|
||||
- Model validation
|
||||
|
||||
## Non-Functional Requirements
|
||||
- Performance: Maintain UI responsiveness
|
||||
- Tests: >80% coverage for new code
|
||||
|
||||
## Architecture Reference
|
||||
- docs/guide_architecture.md
|
||||
- docs/guide_mma.md
|
||||
- docs/guide_tools.md
|
||||
|
||||
## Out of Scope
|
||||
- Major refactoring of unrelated systems
|
||||
- Valid model list
|
||||
- Clear indication of override
|
||||
|
||||
@@ -1,33 +1,29 @@
|
||||
# Track Specification: Performance Dashboard
|
||||
|
||||
## Overview
|
||||
Implement performance dashboard for Manual Slop application.
|
||||
Expand performance metrics with CPU/RAM, frame time, input lag graphs.
|
||||
|
||||
## Current State Audit
|
||||
### Already Implemented (DO NOT re-implement)
|
||||
- Existing backend functionality in src/ modules
|
||||
- Test coverage for core features
|
||||
### Already Implemented
|
||||
- performance_monitor.py
|
||||
- get_metrics() method
|
||||
- Basic FPS display
|
||||
|
||||
### Gaps to Fill (This Track Scope)
|
||||
This track addresses the gap between backend implementation and user-facing GUI/control.
|
||||
### Gaps to Fill
|
||||
- No historical graphs
|
||||
- No input lag tracking
|
||||
- No CPU/RAM visualization
|
||||
|
||||
## Goals
|
||||
- Implement performance dashboard
|
||||
- Ensure test coverage
|
||||
- Follow existing code patterns
|
||||
- Historical performance graphs
|
||||
- CPU/RAM usage display
|
||||
- Input lag metrics
|
||||
|
||||
## Functional Requirements
|
||||
- User-facing functionality as described in TASKS.md
|
||||
- Integration with existing backend
|
||||
- Rolling metrics history
|
||||
- Graph rendering
|
||||
- Alert thresholds
|
||||
|
||||
## Non-Functional Requirements
|
||||
- Performance: Maintain UI responsiveness
|
||||
- Tests: >80% coverage for new code
|
||||
|
||||
## Architecture Reference
|
||||
- docs/guide_architecture.md
|
||||
- docs/guide_mma.md
|
||||
- docs/guide_tools.md
|
||||
|
||||
## Out of Scope
|
||||
- Major refactoring of unrelated systems
|
||||
- 60fps UI during metrics collection
|
||||
- Configurable history length
|
||||
|
||||
@@ -1,33 +1,27 @@
|
||||
# Track Specification: Pipeline Pause/Resume
|
||||
|
||||
## Overview
|
||||
Implement pipeline pause/resume for Manual Slop application.
|
||||
Global pause/resume for entire DAG execution pipeline.
|
||||
|
||||
## Current State Audit
|
||||
### Already Implemented (DO NOT re-implement)
|
||||
- Existing backend functionality in src/ modules
|
||||
- Test coverage for core features
|
||||
### Already Implemented
|
||||
- DAG engine execution
|
||||
- auto_queue mode
|
||||
|
||||
### Gaps to Fill (This Track Scope)
|
||||
This track addresses the gap between backend implementation and user-facing GUI/control.
|
||||
### Gaps to Fill
|
||||
- No pause mechanism
|
||||
- No resume capability
|
||||
|
||||
## Goals
|
||||
- Implement pipeline pause/resume
|
||||
- Ensure test coverage
|
||||
- Follow existing code patterns
|
||||
- Global pause button
|
||||
- Resume button
|
||||
- Frozen state visualization
|
||||
|
||||
## Functional Requirements
|
||||
- User-facing functionality as described in TASKS.md
|
||||
- Integration with existing backend
|
||||
- Pause all workers
|
||||
- Resume from paused state
|
||||
- State persistence
|
||||
|
||||
## Non-Functional Requirements
|
||||
- Performance: Maintain UI responsiveness
|
||||
- Tests: >80% coverage for new code
|
||||
|
||||
## Architecture Reference
|
||||
- docs/guide_architecture.md
|
||||
- docs/guide_mma.md
|
||||
- docs/guide_tools.md
|
||||
|
||||
## Out of Scope
|
||||
- Major refactoring of unrelated systems
|
||||
- Worker state preservation
|
||||
- Clean resume
|
||||
|
||||
@@ -1,33 +1,27 @@
|
||||
# Track Specification: Session Insights & Efficiency Scores
|
||||
|
||||
## Overview
|
||||
Implement session insights & efficiency scores for Manual Slop application.
|
||||
Token usage over time, cost projections, efficiency metrics.
|
||||
|
||||
## Current State Audit
|
||||
### Already Implemented (DO NOT re-implement)
|
||||
- Existing backend functionality in src/ modules
|
||||
- Test coverage for core features
|
||||
### Already Implemented
|
||||
- session_logger.py
|
||||
- Token counting
|
||||
|
||||
### Gaps to Fill (This Track Scope)
|
||||
This track addresses the gap between backend implementation and user-facing GUI/control.
|
||||
### Gaps to Fill
|
||||
- No visualization
|
||||
- No efficiency scoring
|
||||
|
||||
## Goals
|
||||
- Implement session insights & efficiency scores
|
||||
- Ensure test coverage
|
||||
- Follow existing code patterns
|
||||
- Token usage graphs
|
||||
- Cost projections
|
||||
- Efficiency scores
|
||||
|
||||
## Functional Requirements
|
||||
- User-facing functionality as described in TASKS.md
|
||||
- Integration with existing backend
|
||||
- Rolling token history
|
||||
- Cost calculation
|
||||
- Efficiency algorithm
|
||||
|
||||
## Non-Functional Requirements
|
||||
- Performance: Maintain UI responsiveness
|
||||
- Tests: >80% coverage for new code
|
||||
|
||||
## Architecture Reference
|
||||
- docs/guide_architecture.md
|
||||
- docs/guide_mma.md
|
||||
- docs/guide_tools.md
|
||||
|
||||
## Out of Scope
|
||||
- Major refactoring of unrelated systems
|
||||
- Session comparison
|
||||
- Export capability
|
||||
|
||||
@@ -1,33 +1,28 @@
|
||||
# Track Specification: Manual Ticket Queue Management
|
||||
|
||||
## Overview
|
||||
Implement manual ticket queue management for Manual Slop application.
|
||||
Reorder, prioritize, and requeue tickets with drag-drop UI.
|
||||
|
||||
## Current State Audit
|
||||
### Already Implemented (DO NOT re-implement)
|
||||
- Existing backend functionality in src/ modules
|
||||
- Test coverage for core features
|
||||
### Already Implemented
|
||||
- Ticket system in models.py
|
||||
- DAG dependency resolution
|
||||
|
||||
### Gaps to Fill (This Track Scope)
|
||||
This track addresses the gap between backend implementation and user-facing GUI/control.
|
||||
### Gaps to Fill
|
||||
- No drag-drop reordering
|
||||
- No priority tags
|
||||
- No bulk operations
|
||||
|
||||
## Goals
|
||||
- Implement manual ticket queue management
|
||||
- Ensure test coverage
|
||||
- Follow existing code patterns
|
||||
- Drag-drop ticket reordering
|
||||
- Priority tags (high/med/low)
|
||||
- Bulk select and execute/skip/block
|
||||
|
||||
## Functional Requirements
|
||||
- User-facing functionality as described in TASKS.md
|
||||
- Integration with existing backend
|
||||
- Drag-drop handlers
|
||||
- Priority field on tickets
|
||||
- Bulk action buttons
|
||||
|
||||
## Non-Functional Requirements
|
||||
- Performance: Maintain UI responsiveness
|
||||
- Tests: >80% coverage for new code
|
||||
|
||||
## Architecture Reference
|
||||
- docs/guide_architecture.md
|
||||
- docs/guide_mma.md
|
||||
- docs/guide_tools.md
|
||||
|
||||
## Out of Scope
|
||||
- Major refactoring of unrelated systems
|
||||
- Maintain DAG validity
|
||||
- Undo capability
|
||||
|
||||
@@ -1,33 +1,27 @@
|
||||
# Track Specification: Advanced Tier 4 QA Auto-Patching
|
||||
|
||||
## Overview
|
||||
Implement advanced tier 4 qa auto-patching for Manual Slop application.
|
||||
Elevate Tier 4 to auto-patcher with .patch file generation and diff viewer.
|
||||
|
||||
## Current State Audit
|
||||
### Already Implemented (DO NOT re-implement)
|
||||
- Existing backend functionality in src/ modules
|
||||
- Test coverage for core features
|
||||
### Already Implemented
|
||||
- Tier 4 log analysis
|
||||
- Error detection in tests
|
||||
|
||||
### Gaps to Fill (This Track Scope)
|
||||
This track addresses the gap between backend implementation and user-facing GUI/control.
|
||||
### Gaps to Fill
|
||||
- No .patch generation
|
||||
- No GUI diff viewer
|
||||
|
||||
## Goals
|
||||
- Implement advanced tier 4 qa auto-patching
|
||||
- Ensure test coverage
|
||||
- Follow existing code patterns
|
||||
- Tier 4 generates .patch on test failure
|
||||
- Side-by-side diff viewer in GUI
|
||||
- Apply patch button
|
||||
|
||||
## Functional Requirements
|
||||
- User-facing functionality as described in TASKS.md
|
||||
- Integration with existing backend
|
||||
- .patch file generation
|
||||
- Diff computation
|
||||
- Patch application
|
||||
|
||||
## Non-Functional Requirements
|
||||
- Performance: Maintain UI responsiveness
|
||||
- Tests: >80% coverage for new code
|
||||
|
||||
## Architecture Reference
|
||||
- docs/guide_architecture.md
|
||||
- docs/guide_mma.md
|
||||
- docs/guide_tools.md
|
||||
|
||||
## Out of Scope
|
||||
- Major refactoring of unrelated systems
|
||||
- Safe patch preview before apply
|
||||
- Rollback capability
|
||||
|
||||
@@ -1,33 +1,26 @@
|
||||
# Track Specification: Tool Usage Analytics
|
||||
|
||||
## Overview
|
||||
Implement tool usage analytics for Manual Slop application.
|
||||
Analytics panel for tool usage patterns.
|
||||
|
||||
## Current State Audit
|
||||
### Already Implemented (DO NOT re-implement)
|
||||
- Existing backend functionality in src/ modules
|
||||
- Test coverage for core features
|
||||
### Already Implemented
|
||||
- tool_log_callback
|
||||
- Tool execution tracking
|
||||
|
||||
### Gaps to Fill (This Track Scope)
|
||||
This track addresses the gap between backend implementation and user-facing GUI/control.
|
||||
### Gaps to Fill
|
||||
- No analytics UI
|
||||
- No aggregation
|
||||
|
||||
## Goals
|
||||
- Implement tool usage analytics
|
||||
- Ensure test coverage
|
||||
- Follow existing code patterns
|
||||
- Most-used tools ranking
|
||||
- Average execution time
|
||||
- Failure rate tracking
|
||||
|
||||
## Functional Requirements
|
||||
- User-facing functionality as described in TASKS.md
|
||||
- Integration with existing backend
|
||||
- Usage histograms
|
||||
- Time series data
|
||||
- Failure logging
|
||||
|
||||
## Non-Functional Requirements
|
||||
- Performance: Maintain UI responsiveness
|
||||
- Tests: >80% coverage for new code
|
||||
|
||||
## Architecture Reference
|
||||
- docs/guide_architecture.md
|
||||
- docs/guide_mma.md
|
||||
- docs/guide_tools.md
|
||||
|
||||
## Out of Scope
|
||||
- Major refactoring of unrelated systems
|
||||
- Efficient data aggregation
|
||||
|
||||
@@ -1,33 +1,26 @@
|
||||
# Track Specification: Track Progress Visualization
|
||||
|
||||
## Overview
|
||||
Implement track progress visualization for Manual Slop application.
|
||||
Progress bars and completion percentage for tracks/tickets.
|
||||
|
||||
## Current State Audit
|
||||
### Already Implemented (DO NOT re-implement)
|
||||
- Existing backend functionality in src/ modules
|
||||
- Test coverage for core features
|
||||
### Already Implemented
|
||||
- Track/ticket status tracking
|
||||
- DAG execution state
|
||||
|
||||
### Gaps to Fill (This Track Scope)
|
||||
This track addresses the gap between backend implementation and user-facing GUI/control.
|
||||
### Gaps to Fill
|
||||
- No progress bars
|
||||
- No completion %
|
||||
|
||||
## Goals
|
||||
- Implement track progress visualization
|
||||
- Ensure test coverage
|
||||
- Follow existing code patterns
|
||||
- Visual progress bars
|
||||
- % completion
|
||||
- Time estimates
|
||||
|
||||
## Functional Requirements
|
||||
- User-facing functionality as described in TASKS.md
|
||||
- Integration with existing backend
|
||||
- Progress calculation
|
||||
- Bar rendering
|
||||
- ETA estimation
|
||||
|
||||
## Non-Functional Requirements
|
||||
- Performance: Maintain UI responsiveness
|
||||
- Tests: >80% coverage for new code
|
||||
|
||||
## Architecture Reference
|
||||
- docs/guide_architecture.md
|
||||
- docs/guide_mma.md
|
||||
- docs/guide_tools.md
|
||||
|
||||
## Out of Scope
|
||||
- Major refactoring of unrelated systems
|
||||
- Accurate state sync
|
||||
|
||||
@@ -1,33 +1,28 @@
|
||||
# Track Specification: True Parallel Worker Execution (The DAG Realization)
|
||||
# Track Specification: True Parallel Worker Execution
|
||||
|
||||
## Overview
|
||||
Implement true parallel worker execution (the dag realization) for Manual Slop application.
|
||||
Implement true concurrency for the DAG engine to spawn parallel Tier 3 workers.
|
||||
|
||||
## Current State Audit
|
||||
### Already Implemented (DO NOT re-implement)
|
||||
- Existing backend functionality in src/ modules
|
||||
- Test coverage for core features
|
||||
### Already Implemented
|
||||
- threading.local() for tier isolation (Track 5)
|
||||
- DAG engine in dag_engine.py
|
||||
- Worker spawning in multi_agent_conductor.py
|
||||
|
||||
### Gaps to Fill (This Track Scope)
|
||||
This track addresses the gap between backend implementation and user-facing GUI/control.
|
||||
### Gaps to Fill
|
||||
- No parallel worker spawning
|
||||
- No file locking for concurrent file access
|
||||
|
||||
## Goals
|
||||
- Implement true parallel worker execution (the dag realization)
|
||||
- Ensure test coverage
|
||||
- Follow existing code patterns
|
||||
- Spawn 4 independent Tier 3 workers in parallel
|
||||
- Implement file locking or Git-based diff-merging
|
||||
- Thread-safe ticket status updates
|
||||
|
||||
## Functional Requirements
|
||||
- User-facing functionality as described in TASKS.md
|
||||
- Integration with existing backend
|
||||
- Worker pool with configurable size
|
||||
- File locking mechanism
|
||||
- Status tracking for each worker
|
||||
|
||||
## Non-Functional Requirements
|
||||
- Performance: Maintain UI responsiveness
|
||||
- Tests: >80% coverage for new code
|
||||
|
||||
## Architecture Reference
|
||||
- docs/guide_architecture.md
|
||||
- docs/guide_mma.md
|
||||
- docs/guide_tools.md
|
||||
|
||||
## Out of Scope
|
||||
- Major refactoring of unrelated systems
|
||||
- No race conditions on file access
|
||||
- >80% test coverage for new code
|
||||
|
||||
@@ -1,33 +1,27 @@
|
||||
# Track Specification: Visual DAG & Interactive Ticket Editing
|
||||
|
||||
## Overview
|
||||
Implement visual dag & interactive ticket editing for Manual Slop application.
|
||||
Replace linear ticket list with interactive node graph using ImGui Bundle.
|
||||
|
||||
## Current State Audit
|
||||
### Already Implemented (DO NOT re-implement)
|
||||
- Existing backend functionality in src/ modules
|
||||
- Test coverage for core features
|
||||
### Already Implemented
|
||||
- Ticket/DAG display in gui_2.py
|
||||
- DAG engine for dependency resolution
|
||||
|
||||
### Gaps to Fill (This Track Scope)
|
||||
This track addresses the gap between backend implementation and user-facing GUI/control.
|
||||
### Gaps to Fill
|
||||
- Linear ticket list only
|
||||
- No drag-drop dependency editing
|
||||
|
||||
## Goals
|
||||
- Implement visual dag & interactive ticket editing
|
||||
- Ensure test coverage
|
||||
- Follow existing code patterns
|
||||
- Interactive node graph visualization
|
||||
- Drag dependency lines
|
||||
- Split/delete nodes visually
|
||||
|
||||
## Functional Requirements
|
||||
- User-facing functionality as described in TASKS.md
|
||||
- Integration with existing backend
|
||||
- ImGui Bundle node editor integration
|
||||
- Click-drag node positioning
|
||||
- Visual dependency lines
|
||||
|
||||
## Non-Functional Requirements
|
||||
- Performance: Maintain UI responsiveness
|
||||
- Tests: >80% coverage for new code
|
||||
|
||||
## Architecture Reference
|
||||
- docs/guide_architecture.md
|
||||
- docs/guide_mma.md
|
||||
- docs/guide_tools.md
|
||||
|
||||
## Out of Scope
|
||||
- Major refactoring of unrelated systems
|
||||
- Maintain DAG validity on edit
|
||||
- Smooth 60fps rendering
|
||||
|
||||
Reference in New Issue
Block a user