feat(learning): measure rebuild and recovery sufficiency pressure

Author: Jacobinwwey

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

@@ -58,7 +58,8 @@ Execution anchor:
 - Upgraded the first real measured observation path:
   - runtime query traffic now promotes sufficiency query-latency observation from `policy_default` to `measured`,
   - the warm-query threshold now carries `observedValue` when runtime telemetry exists,
-  - docs/verifier output now expose query observation mode and latest persistence event timestamps.
+  - full-corpus ingest and store reload now promote rebuild/recovery duration observations to `measured`,
+  - docs/verifier output now expose query/rebuild/recovery observation mode and latest persistence event timestamps.
 - Locked the current architectural posture to an evidence-first rule:
   - local sqlite + deterministic ANN remains the default backend baseline,
   - heavier backend work now needs explicit escalation triggers,
@@ -68,7 +69,7 @@ Execution anchor:
   - `mkdocs.yml`
   - EN/ZH Diataxis overview progress entry points.
 - Changed the next bounded backend-governance slice:
-  - extend measurement beyond query latency into rebuild/recovery duration capture rather than redoing initial route/report wiring.
+  - keep repeated device-level measurement honest and move the next default budget into product/memory/operator work unless a measured trigger fires.
 
 ## Latest Mainline Increment (2026-04-14 M1 Baseline)
 

docs/diataxis/en/explanation/local-backend-sufficiency-and-escalation-plan.md

@@ -36,7 +36,9 @@ This decision is no longer prose-only.
 
 Important limitation:
 
-- top-level evidence mode is still `policy_default`, but query-latency observation now upgrades to `measured` when runtime query history exists.
+- top-level evidence mode is still often `policy_default` or `observed_event`,
+- query-latency observation upgrades to `measured` when runtime query history exists,
+- rebuild/recovery observations now also upgrade to `measured` when the runtime executes a full-corpus ingest or store reload.
 
 That means the next backend-governance step is **measurement hardening**, not backend replacement.
 
@@ -221,11 +223,11 @@ Delivered so the dashboard and this page consume the same decision language:
 The remaining bounded slice is not "add the first report."
 That is done.
 
-The remaining slice is:
+The remaining slice is now narrower:
 
-- replace the remaining `policy_default` thresholds with measured capture where feasible,
-- extend measurement beyond query latency into rebuild / recovery duration fields,
-- keep escalation tied to measured pressure instead of architectural anxiety.
+- keep collecting repeated rebuild / recovery samples on a reference device instead of falling back to architecture speculation,
+- use measured overruns, not roadmap inertia, to trigger backend escalation,
+- move the next engineering budget into product/memory/operator work while the sufficiency report stays green.
 
 ## Recommended Next Lane
 

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

@@ -58,7 +58,8 @@
 - 已补上第一条真实 measured observation 路径：
   - 运行时 query 流量会把 sufficiency query-latency observation 从 `policy_default` 升级为 `measured`，
   - warm-query threshold 在存在运行时 telemetry 时会携带 `observedValue`，
-  - docs/verifier 输出现在会暴露 query observation mode 与最近 persistence event 时间戳。
+  - full-corpus ingest 与 store reload 现在也会把 rebuild/recovery duration observation 升级为 `measured`，
+  - docs/verifier 输出现在会暴露 query/rebuild/recovery observation mode 与最近 persistence event 时间戳。
 - 已把当前架构姿态锁定为证据优先规则：
   - local sqlite + 确定性 ANN 继续作为默认 backend baseline，
   - 更重 backend 工作必须提供显式 escalation trigger，
@@ -68,7 +69,7 @@
   - `mkdocs.yml`
   - EN/ZH Diataxis overview 的进度入口。
 - 已更新下一段有界 backend governance 切片：
-  - 把测量范围从 query latency 继续扩展到 rebuild/recovery duration，而不是重复补第一版 route/report。
+  - 保持设备级测量诚实，把默认预算转向 product / memory / operator 工作，除非 measured trigger 真实触发。
 
 ## 主线最新增量（2026-04-14 M1 基线）
 

docs/diataxis/zh/explanation/local-backend-sufficiency-and-escalation-plan.md

@@ -36,7 +36,9 @@
 
 当前限制：
 
-- 顶层 evidence mode 仍然是 `policy_default`，但 query-latency observation 已可在运行时产生查询历史后升级为 `measured`。
+- 顶层 evidence mode 仍然经常停留在 `policy_default` 或 `observed_event`，
+- query-latency observation 已可在运行时产生查询历史后升级为 `measured`，
+- rebuild / recovery observation 也已经能在运行时执行 full-corpus ingest 或 store reload 后升级为 `measured`。
 
 所以，下一步 backend governance 工作应是**测量加固**，不是 backend replacement。
 
@@ -220,11 +222,11 @@
 剩余的有界切片已经不是“补第一版报告”。
 这一步已经完成。
 
-剩余切片是：
+剩余切片已经进一步收窄为：
 
-- 在剩余维度上继续用测量采集替换 `policy_default` 阈值，
-- 把测量范围从 query latency 扩展到 rebuild / recovery duration 字段，
-- 保证升级依然由测量压力驱动，而不是由架构焦虑驱动。
+- 在参考设备上持续积累 rebuild / recovery 样本，而不是退回到架构猜测，
+- 只让 measured overrun 触发 backend escalation，而不是被旧路线图惯性牵引，
+- 当 sufficiency report 仍为绿色时，把默认工程预算继续投向 product / memory / operator 工作。
 
 ## 推荐下一条主线