docs(milestone): archive v1.0 roadmap requirements and state
This commit is contained in:
parent
5a4da6e581
commit
931c418c87
|
|
@ -0,0 +1,16 @@
|
||||||
|
# Milestones
|
||||||
|
|
||||||
|
## v1.0 milestone (Shipped: 2026-04-07)
|
||||||
|
|
||||||
|
**Phases completed:** 5 phases, 6 plans, 9 tasks
|
||||||
|
|
||||||
|
**Key accomplishments:**
|
||||||
|
|
||||||
|
- 交付了可复现冲突证据链、文件级风险清单与 Titan 重叠决策矩阵，形成“旧视觉+新逻辑”执行输入。
|
||||||
|
- 线程路由从 isnew 参数切换为路由单路径语义，并将 skills bootstrap 合同统一到 content_ids。
|
||||||
|
- 完成 03-UAT 的关键 gap 收敛：lint 阻塞清零，welcome-and-routing 从 4 失败收敛到 0 失败。
|
||||||
|
- 基于 originui 合并基线完成 Phase 3 执行记录，并输出可审计的视觉与回归验证结果。
|
||||||
|
- 完成 Phase 4 首轮执行：iframe 通信与导出链路加入前端容错，目标 lint/E2E 验证通过。
|
||||||
|
- Phase 5 执行完成：目标 E2E 套件达到“0 失败、可解释 skip”，并形成提交卫生分组建议。
|
||||||
|
|
||||||
|
---
|
||||||
|
|
@ -2,13 +2,13 @@
|
||||||
gsd_state_version: 1.0
|
gsd_state_version: 1.0
|
||||||
milestone: v1.0
|
milestone: v1.0
|
||||||
milestone_name: milestone
|
milestone_name: milestone
|
||||||
status: Ready to plan
|
status: v1.0 milestone complete
|
||||||
last_updated: "2026-04-07T04:32:17.454Z"
|
last_updated: "2026-04-07T06:26:30.389Z"
|
||||||
progress:
|
progress:
|
||||||
total_phases: 5
|
total_phases: 5
|
||||||
completed_phases: 1
|
completed_phases: 5
|
||||||
total_plans: 1
|
total_plans: 6
|
||||||
completed_plans: 1
|
completed_plans: 6
|
||||||
percent: 100
|
percent: 100
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -0,0 +1,82 @@
|
||||||
|
# Requirements Archive: v1.0 milestone
|
||||||
|
|
||||||
|
**Archived:** 2026-04-07
|
||||||
|
**Status:** SHIPPED
|
||||||
|
|
||||||
|
For current requirements, see `.planning/REQUIREMENTS.md`.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
# 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*
|
||||||
|
|
@ -0,0 +1,57 @@
|
||||||
|
# Roadmap: DeerFlow Frontend Merge Recovery
|
||||||
|
|
||||||
|
**Created:** 2026-04-07
|
||||||
|
**Source:** .planning/PROJECT.md + .planning/REQUIREMENTS.md
|
||||||
|
|
||||||
|
## Phase 1: Conflict Inventory and Decision Matrix
|
||||||
|
|
||||||
|
**Goal:** Build an auditable conflict inventory covering merge-overwritten regions, Titan-overlap regions, and keep/replace candidates.
|
||||||
|
|
||||||
|
**Covers:** MERGE-01, MERGE-03
|
||||||
|
|
||||||
|
- Produce file-level conflict matrix with risk levels
|
||||||
|
- Mark visual-only, logic-only, and mixed-change files
|
||||||
|
- Identify Titan-linked hotspots and expected behavior per hotspot
|
||||||
|
|
||||||
|
## Phase 2: Thread and Skills Logic Reconciliation
|
||||||
|
|
||||||
|
**Goal:** Reconcile thread bootstrap/routing and skills API logic so merged behavior is explicit and stable.
|
||||||
|
|
||||||
|
**Covers:** MERGE-02, LOGIC-03, LOGIC-04
|
||||||
|
|
||||||
|
- Reconcile `thread_id`/`isnew`/`xclaw_used` behavior in chat flow
|
||||||
|
- Decide and implement skills bootstrap contract direction
|
||||||
|
- Verify no duplicate or dead logic paths remain
|
||||||
|
|
||||||
|
## Phase 3: Legacy Visual Alignment Pass
|
||||||
|
|
||||||
|
**Goal:** Align workspace visual presentation to legacy baseline without regressing logic.
|
||||||
|
|
||||||
|
**Covers:** UI-01, UI-02, UI-03
|
||||||
|
|
||||||
|
- Apply visual alignment in layout and component layers
|
||||||
|
- Keep behavioral code intact while adjusting style semantics
|
||||||
|
- Validate visual consistency across core workspace views
|
||||||
|
|
||||||
|
## Phase 4: Iframe + Markdown New-System Stabilization
|
||||||
|
|
||||||
|
**Goal:** Keep and harden new-system capabilities for iframe communication and markdown export.
|
||||||
|
|
||||||
|
**Covers:** LOGIC-01, LOGIC-02
|
||||||
|
|
||||||
|
- Stabilize parent/child messaging and selected-skill event flows
|
||||||
|
- Stabilize markdown conversion and download triggers
|
||||||
|
- Validate artifact integration points
|
||||||
|
|
||||||
|
## Phase 5: Test Hardening and Commit Hygiene
|
||||||
|
|
||||||
|
**Goal:** Lock recovery with regression tests and clean commit structure.
|
||||||
|
|
||||||
|
**Covers:** TEST-01, TEST-02, TEST-03
|
||||||
|
|
||||||
|
- Finalize and run E2E suite for target scenarios
|
||||||
|
- Split commits into style / logic / tests concern buckets
|
||||||
|
- Attach reviewer-oriented verification notes for high-risk files
|
||||||
|
|
||||||
|
---
|
||||||
|
*Next command:* `/gsd-plan-phase 1`
|
||||||
Loading…
Reference in New Issue