Add benchmark results for fast3 and fast4, implement KeepAliveLspBridge, and add tests for staged strategies

- Added new benchmark result files: compare_2026-02-09_score_fast3.json and compare_2026-02-09_score_fast4.json.
- Implemented KeepAliveLspBridge to maintain a persistent LSP connection across multiple queries, improving performance.
- Created unit tests for staged clustering strategies in test_staged_stage3_fast_strategies.py, ensuring correct behavior of score and dir_rr strategies.
This commit is contained in:
catlog22
2026-02-09 20:45:29 +08:00
parent c62d26183b
commit 4344e79e68
64 changed files with 6154 additions and 123 deletions

View File

@@ -181,7 +181,7 @@ When tests fail during implementation, the CD agent MUST initiate the hypothesis
|---------|-----------|--------|
| **Test Failure** | Automated tests fail during implementation | Start debug workflow |
| **Integration Conflict** | Blockers logged in `issues.md` | Start debug workflow |
| **VAS Feedback** | Orchestrator provides validation failure feedback | Start debug workflow |
| **VAS Feedback** | Main flow provides validation failure feedback | Start debug workflow |
### Debug Workflow Phases
@@ -356,7 +356,7 @@ PHASE_RESULT:
- Used to guide development
- **RA (Requirements Analyst)**: "Requirement FR-X means..."
- Used for clarification
- **Orchestrator**: "Fix these issues in next iteration"
- **Main Flow**: "Fix these issues in next iteration"
- Used for priority setting
### Sends To:
@@ -364,7 +364,7 @@ PHASE_RESULT:
- Used for test generation
- **RA (Requirements Analyst)**: "FR-X is unclear, need clarification"
- Used for requirement updates
- **Orchestrator**: "Found blocker X, need help"
- **Main Flow**: "Found blocker X, need help"
- Used for decision making
## Code Quality Standards