74 lines
2.9 KiB
Markdown
74 lines
2.9 KiB
Markdown
# Requirements: DeerFlow Frontend Merge Recovery
|
|
|
|
**Defined:** 2026-04-07
|
|
**Core Value:** Keep the frontend visually familiar while preserving and hardening new-system behavior end to end.
|
|
|
|
## v1 Requirements
|
|
|
|
### Merge Reconciliation
|
|
|
|
- [x] **MERGE-01**: Team can list all merge-overwritten hotspots with file-level evidence and risk classification
|
|
- [x] **MERGE-02**: Team can restore required new-system logic removed during merge while avoiding duplicate behavior paths
|
|
- [x] **MERGE-03**: Team can identify and reconcile Titan-overlap code paths with explicit keep/replace decisions
|
|
|
|
### UI Visual Alignment
|
|
|
|
- [ ] **UI-01**: Workspace visual style aligns with legacy baseline for typography, spacing, and component hierarchy
|
|
- [ ] **UI-02**: Visual alignment changes do not break chat/thread/artifact interactions
|
|
- [ ] **UI-03**: Global style changes remain consistent across main workspace pages
|
|
|
|
### New-System Logic Integrity
|
|
|
|
- [ ] **LOGIC-01**: iframe communication flow functions correctly for selected skill and parent message events
|
|
- [ ] **LOGIC-02**: Markdown download flow works from generation to export trigger in workspace
|
|
- [x] **LOGIC-03**: Thread creation/reuse logic remains correct for `thread_id`, `isnew`, and `xclaw_used` combinations
|
|
- [x] **LOGIC-04**: Skills bootstrap API contract is explicitly reconciled (`content_id` vs `content_ids`) without silent breakage
|
|
|
|
### Quality and Regression Safety
|
|
|
|
- [ ] **TEST-01**: E2E tests cover message/history, input/compose, welcome/routing, and artifact/thread reuse flows
|
|
- [ ] **TEST-02**: Recovery changes are committed in separable concern groups (style vs logic vs tests)
|
|
- [ ] **TEST-03**: Critical conflict files have before/after verification notes for reviewer auditing
|
|
|
|
## v2 Requirements
|
|
|
|
### Tooling Improvements
|
|
|
|
- **TOOL-01**: Add automated conflict hotspot detector for future merges
|
|
- **TOOL-02**: Add style-vs-logic diff classifier script for commit preparation
|
|
|
|
## Out of Scope
|
|
|
|
| Feature | Reason |
|
|
|---------|--------|
|
|
| New product feature development unrelated to merge recovery | Would dilute stabilization focus |
|
|
| Backend architecture refactors not required by frontend recovery | Not necessary for current milestone objective |
|
|
| Full design system reimplementation | Too large for recovery scope |
|
|
|
|
## Traceability
|
|
|
|
| Requirement | Phase | Status |
|
|
|-------------|-------|--------|
|
|
| MERGE-01 | Phase 1 | Complete |
|
|
| MERGE-02 | Phase 1 | Complete |
|
|
| MERGE-03 | Phase 1 | Complete |
|
|
| LOGIC-03 | Phase 2 | Complete |
|
|
| LOGIC-04 | Phase 2 | Complete |
|
|
| UI-01 | Phase 3 | Pending |
|
|
| UI-02 | Phase 3 | Pending |
|
|
| UI-03 | Phase 3 | Pending |
|
|
| LOGIC-01 | Phase 4 | Pending |
|
|
| LOGIC-02 | Phase 4 | Pending |
|
|
| TEST-01 | Phase 5 | Pending |
|
|
| TEST-02 | Phase 5 | Pending |
|
|
| TEST-03 | Phase 5 | Pending |
|
|
|
|
**Coverage:**
|
|
- v1 requirements: 13 total
|
|
- Mapped to phases: 13
|
|
- Unmapped: 0
|
|
|
|
---
|
|
*Requirements defined: 2026-04-07*
|
|
*Last updated: 2026-04-07 after initial definition*
|