docs(progress): refresh post-M8 dashboard summary

Align the current-facing dashboard snapshot, phase summary, and next-step
narrative with the integrated sqlite plus local-ANN foundation baseline on
main.

Author: Jacobinwwey

docs/diataxis/en/explanation/development-progress-dashboard.md

@@ -1015,11 +1015,11 @@ This dashboard aligns against the following requirement chain:
 - [2026-04-16 Mainline CI Stabilization and M7 Direction](../../../brainstorms/2026-04-16-mainline-ci-stabilization-and-m7-direction-requirements.md)
 - [2026-04-19 Mainline Progress Reconciliation and Post-M7 Direction](../../../brainstorms/2026-04-19-mainline-progress-reconciliation-and-post-m7-direction-requirements.md)
 
-## Phase Snapshot (2026-04-20)
+## Phase Snapshot (2026-04-21)
 
 | Phase | Plan Target | Branch Progress | Mainline Status |
 |---|---|---|---|
-| Phase 1 | Knowledge parsing + graph backbone + staleness governance | Branch still frames graphdb/vector follow-up ambitions | Explainable retrieval + file-backed persistence baseline integrated on `main`; adapter re-entry still pending |
+| Phase 1 | Knowledge parsing + graph backbone + staleness governance | Branch still frames graphdb/vector follow-up ambitions | Explainable retrieval + sqlite-backed persistence + bounded local ANN vector acceleration are integrated on `main` |
 | Phase 2 | Mastery loop + divergence engine | Branch still carries broader experimentation claims | Misconception/path/session/memory loops are already integrated and tested on `main` |
 | Phase 3 | Pluggable tutor + memory operating layer | Branch still contains broader agent/tutor ambitions | Local tutor adapter + memory-policy baseline are integrated on `main`, but broader multi-tutor ambitions remain unmerged |
 
@@ -1066,14 +1066,14 @@ npm test -- src/learning/KnowledgeLearningPlatform.test.ts --runInBand
 npm test -- src/learning/KnowledgeLearningPlatform.persistence.test.ts --runInBand
 ```
 
-Note: do not list foundation-lane gates as baseline until the corresponding modules/tests exist on mainline.
+Note: foundation-lane gates now exist on `main`; keep them in the normal verification baseline instead of treating them as branch-only future work.
 
 ## Next Direction (Current Priority)
 
 1. Close the checkpoint cleanly: keep EN/ZH docs aligned with the actual `main` state and keep the Windows restore-cache migration path non-flaky.
 2. Treat notification-threshold governance as closed after `M7.29`; do not plan `M7.30+` unless a materially new operator requirement appears.
-3. Treat the current foundation lane as checkpointed at `M8.18/M8.19`: inspectability is strong enough for now, but no document or route may claim independent graph or ANN readiness until stronger backend evidence lands.
-4. Make the next planning round about backend independence, not more runtime inspectability parity.
+3. Treat the current foundation lane as checkpointed and integrated at `M8.18/M8.19`: sqlite graph persistence and bounded local ANN retrieval are already valid baseline claims on `main`.
+4. Make the next planning round about whether the current local backend baseline is sufficient or whether a heavier external graph/vector backend is justified by product/runtime requirements.
 5. Keep markdown-reader governance bounded and secondary until the post-checkpoint lane switch is explicitly chosen.
 
 ## Critical Constraints

docs/diataxis/zh/explanation/development-progress-dashboard.md

@@ -1018,11 +1018,11 @@
 - [2026-04-16 主线 CI 稳定化与 M7 方向](../../../brainstorms/2026-04-16-mainline-ci-stabilization-and-m7-direction-requirements.md)
 - [2026-04-19 主线进度重校准与 Post-M7 后续方向](../../../brainstorms/2026-04-19-mainline-progress-reconciliation-and-post-m7-direction-requirements.md)
 
-## 阶段快照（2026-04-20）
+## 阶段快照（2026-04-21）
 
 | 阶段 | 目标 | 分支进展 | 主线状态 |
 |---|---|---|---|
-| Phase 1 | 知识解析 + 图谱底座 + staleness 治理 | 分支仍在指向 graphdb/vector 后续演进 | 主线已集成 explainable retrieval + file-backed persistence 基线，但 adapter re-entry 仍待启动 |
+| Phase 1 | 知识解析 + 图谱底座 + staleness 治理 | 分支仍在指向 graphdb/vector 后续演进 | 主线已集成 explainable retrieval + sqlite-backed persistence + 受限本地 ANN 向量加速 |
 | Phase 2 | 掌握闭环 + 发散引擎 | 分支仍有更宽的实验化能力 | 主线已集成 misconception/path/session/memory 闭环并有测试覆盖 |
 | Phase 3 | 可插拔导师 + 记忆操作层 | 分支仍有更宽的 agent/tutor 设想 | 主线已集成本地 tutor adapter + memory-policy 基线，但更宽的 multi-tutor 设想尚未并入 |
 
@@ -1069,14 +1069,14 @@ npm test -- src/learning/KnowledgeLearningPlatform.test.ts --runInBand
 npm test -- src/learning/KnowledgeLearningPlatform.persistence.test.ts --runInBand
 ```
 
-说明：foundation lane 对应门禁仅在主线存在相应模块/测试后纳入本看板基线。
+说明：foundation lane 对应门禁现已在主线具备模块与测试，应纳入常态验证基线，而不是继续按“分支未来工作”处理。
 
 ## 后续方向（当前优先级）
 
 1. 先把 checkpoint 收干净：让 EN/ZH 文档与真实 `main` 状态对齐，并保持 Windows restore-cache migration 路径不再抖动。
 2. 将 notification-threshold 治理链路视为在 `M7.29` 后已收口；没有新的强运维需求前，不再规划 `M7.30+`。
-3. 将 foundation 当前阶段视为在 `M8.18/M8.19` 已完成一次 checkpoint：inspectability 已够用，但在更强后端证据进入主线前，仍不能把 graph/vector 说成独立就绪。
-4. 下一轮 planning 应该讨论 backend independence，而不是继续补 runtime inspectability parity。
+3. 将 foundation 当前阶段视为在 `M8.18/M8.19` 已完成 checkpoint 且已集成：sqlite 图持久化与受限本地 ANN 检索已经是 `main` 上可成立的基线结论。
+4. 下一轮 planning 应讨论“当前本地后端基线是否已足够”以及“是否真有必要引入更重的外部 graph/vector backend”，而不是继续补 runtime inspectability parity。
 5. Markdown 阅读器治理继续保持受限且次优先级，直到 post-checkpoint lane switch 被明确选择。
 
 ## 关键约束