feat(workspace): 增加工作活动日报引擎

docs/decisions.md

@@ -330,3 +330,16 @@
 - 测试用例按所属需求分组时展示“已提测/待提测”标签；只有该需求下所有开发任务都 `submitted` 才展示“已提测”，否则展示“待提测”。
 
 **理由**：第一轮承载完整测试范围，后续轮次应复跑同一范围而不是临时拼装；执行记录按轮次隔离，整体投入按版本累计，能同时回答“这一轮测得怎么样”和“这个版本测试总共花了多少”。
+## 28. Daily report uses work activity log, not a generic rules engine
+
+**Problem**: A daily report based only on manual `task-worklogs` misses important actions such as submitting a product plan, starting a development task, submitting code to test, fixing bugs, or marking blockers.
+
+**Decision**: Add a lightweight `work-activities` document key and a typed `work-activity-factory.ts`. Business stores append activity records after successful operations. The workspace daily report derives a personal report from activities, legacy worklogs, and current work items.
+
+**Why**:
+- Automatic activity records provide evidence that work happened today.
+- Manual progress notes explain multi-day work when no status changed today.
+- A generic rules engine is too heavy for the current AppData stage and would hide business rules behind configuration.
+- A pure aggregation function keeps report behavior testable and predictable.
+
+**Rule**: Key status changes count as daily evidence. Multi-day in-progress work without today's activity or progress note is flagged as needing a progress update.