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 @@
# Advanced Tier 4 QA Auto-Patching
**Track ID:** tier4_auto_patching_20260306
**Status:** Planned
**See Also:**
- [Spec](./spec.md)
- [Plan](./plan.md)

View File

@@ -0,0 +1,9 @@
{
"id": "tier4_auto_patching_20260306",
"name": "Advanced Tier 4 QA Auto-Patching",
"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,25 @@
# Implementation Plan: Advanced Tier 4 QA Auto-Patching (tier4_auto_patching)
# Implementation Plan: Tier 4 Auto-Patching (tier4_auto_patching_20260306)
## Phase 1: Research & Design
- [ ] Task: Analyze existing backend implementation
- [ ] Task: Design GUI/UX approach
- [ ] Task: Conductor - User Manual Verification
## Phase 1: Patch Generation
- [ ] Task: Initialize MMA Environment
- [ ] Task: Extend Tier 4 to generate patches
- WHERE: src/multi_agent_conductor.py
- WHAT: Add patch generation on test failure
- HOW: Use difflib to generate unified diff
- SAFETY: Only generate, don't apply
## Phase 2: Implementation
- [ ] Task: Implement feature
- [ ] Task: Write tests
- [ ] Task: Conductor - User Manual Verification
## Phase 2: Diff Viewer
- [ ] Task: Implement GUI diff viewer
- WHERE: src/gui_2.py
- WHAT: Side-by-side diff display
- HOW: Custom ImGui rendering or third-party
- SAFETY: Read-only preview
- [ ] Task: Implement apply button
- WHERE: src/gui_2.py
- WHAT: Apply patch to working directory
- HOW: subprocess.run(['patch', '-p1'])
- SAFETY: Backup before apply
## Phase 3: Verification
- [ ] Task: Run test suite
- [ ] Task: Verify coverage
- [ ] Task: Conductor - Phase Completion Verification
## Phase 3: Tests & Verification
- [ ] Task: Write patch tests
- [ ] Task: Conductor - Phase Verification

View File

@@ -1,27 +1,22 @@
# Track Specification: Advanced Tier 4 QA Auto-Patching
# Track Specification: Advanced Tier 4 QA Auto-Patching (tier4_auto_patching_20260306)
## Overview
Elevate Tier 4 to auto-patcher with .patch file generation and diff viewer.
Elevate Tier 4 from log summarizer to auto-patcher. When verification tests fail, Tier 4 generates a .patch file. GUI displays side-by-side diff; user clicks Apply Patch to resume pipeline.
## Current State Audit
### Already Implemented
- Tier 4 log analysis
- Error detection in tests
### Gaps to Fill
- No .patch generation
- No GUI diff viewer
## Goals
- Tier 4 generates .patch on test failure
- Side-by-side diff viewer in GUI
- Apply patch button
## Architectural Constraints
- **Safe Preview**: Patches MUST be previewed before application.
- **Rollback**: Failed patches MUST be revertable.
- **Atomic Application**: Patch application MUST be atomic (all-or-nothing).
## Functional Requirements
- .patch file generation
- Diff computation
- Patch application
- **Patch Generation**: Tier 4 generates .patch file on test failure.
- **Diff Viewer**: GUI shows side-by-side diff of proposed changes.
- **Apply Button**: User confirms patch application.
- **Patch Application**: Apply patch to working directory and verify.
## Non-Functional Requirements
- Safe patch preview before apply
- Rollback capability
## Acceptance Criteria
- [ ] Tier 4 generates valid .patch file.
- [ ] GUI displays readable side-by-side diff.
- [ ] User can approve/reject patch.
- [ ] Approved patches applied correctly.
- [ ] Rollback available on failure.