feat(v2.2): 完成高频读取热路径

docs/roadmap.md

@@ -1,8 +1,8 @@
 # 开发路线图
 
-## 当前阶段：V2.1 — 服务端持久化第一阶段
+## 当前阶段：V2.2 — 分区关系表与高频读取热路径
 
-业务流程仍保持 V1 的前端 store 形状，但业务数据主存储已切到 NestJS + PostgreSQL `app_data` 文档表。浏览器只保留登录态，不再保存产品、项目、版本、需求、版本详情、成员、任务类型等业务数据。
+V2.2 已完成第一批高频读取热路径：分区关系表基础、AppData 迁移预演、V2.2 scoped read API，以及版本详情、需求池、与我相关、小宝预警的前端快读接入。业务写入仍保留现有 AppData store 兼容窗口，后续再逐步打开关系表写入和领域 CRUD。
 
 ### 已完成（按时间倒序）
 
@@ -12,6 +12,11 @@
 - Xiaobao precompute storage foundation added: `xiaobao_risk_summaries` stores the current version risk, and `xiaobao_risk_snapshots` stores historical snapshots.
 - Prisma schema now includes the V2.2 relational model skeleton, and the legacy `RequirementService` now uses the `(id, product_id)` composite key.
 - AppData V2.2 migration mapper and preview service added, so legacy JSON can be rehearsed into relation-table rows with counts and skipped-record diagnostics before inserts are enabled.
+- V2.2 scoped read API added for version detail, requirement pool, workspace, and Xiaobao warning summaries.
+- Version detail, requirement pool, workspace, sidebar badges, version list Xiaobao indicators, and Xiaobao warning page now prefer V2.2 fast-read data and fall back to AppData only for compatibility.
+- Requirement pool V2.2 queries require `productId`, avoiding accidental full-table scans against annual hundreds-of-thousands-row data.
+- Xiaobao warning now consumes precomputed `xiaobao_risk_summaries` before loading heavy AppData task/test/bug/activity documents.
+- V2.2 completion boundary: read hot paths are complete; writes remain on AppData until the relation-table write APIs are enabled.
 
 **2026-07-02**
 - `app_data` 读写增加乐观锁版本：`GET` 返回 `version`，前端保存携带最近版本，后端用 `key + updatedAt` 原子更新