feat(workspace): 增加工作活动日报引擎
This commit is contained in:
@@ -203,3 +203,21 @@ AI 估时约束:
|
||||
- `version-plan-workflow.ts` 是调研/产品方案/UI 设计完成条件的唯一入口。
|
||||
- `requirement-selector.ts` 是版本内关联需求候选的唯一入口。
|
||||
- `TaskCategory.code` 是 AI 和系统任务类型的稳定映射锚点,`id` 只作为存储主键。
|
||||
## Work Activity Daily Report Flow (2026-06-26)
|
||||
|
||||
The daily report flow uses mixed evidence:
|
||||
|
||||
1. Automatic evidence is written when a user performs a successful domain action:
|
||||
- VersionPlan created, started, or completed.
|
||||
- DevTask created, started, moved to self-test, submitted to test, blocked, or unblocked.
|
||||
- TestCase created, started, passed, failed, or blocked.
|
||||
- Bug created, moved to fixing, fixed, closed, or transferred.
|
||||
2. Manual progress notes are used for multi-day work that does not change status today.
|
||||
3. `/workspace` shows only the current logged-in user's report.
|
||||
4. Project-owner and management views will reuse the same `work-activities` data later, but are not part of the personal workspace panel.
|
||||
|
||||
Implementation convention:
|
||||
|
||||
- Activity wording and category mapping belong in `apps/web/lib/work-activity-factory.ts`.
|
||||
- Daily report grouping belongs in `apps/web/lib/workspace-daily-report.ts`.
|
||||
- Page components should consume report output, not rebuild report rules.
|
||||
|
||||
Reference in New Issue
Block a user