Refresh the cap48 checkpoint now that high-energy reached evaluation

Update the handoff and changelog with the newer cap48 runtime milestone so later sessions know the high_energy lane has advanced from build-index into capped evaluation.

Constraint: No measured cap48 high_energy score is available yet, only a later execution milestone
Rejected: Leave the older build-index note in place | Would make the restart handoff stale and less actionable
Confidence: high
Scope-risk: narrow
Directive: Replace the cap48 runtime note with final top-two scores as soon as high_energy eval.json or report.json lands
Tested: Verified active cap48 high_energy evaluate.py process; verified docs now record high_energy current phase as evaluate.py --max-queries 24
Not-tested: Final cap48 comparison because high_energy eval.json has not landed yet

@@ -19,7 +19,7 @@
   - `top1 = 0.7917`
   - `top1 = 0.7917`
   - `topk = 1.0`
   - `topk = 1.0`
 - `high_energy` 已进入：
 - `high_energy` 已进入：
-  - `run_demo.py build-index --resume --checkpoint-every-refs 100`
+  - `evaluate.py --data /tmp/ab_smoke_seg_cap48_top2/high_energy/fma/manifests ... --max-queries 24`
 - `report.json` 尚未落盘
 - `report.json` 尚未落盘
 
 
 结论：
 结论：

@@ -486,7 +486,7 @@ cd /workspace/acr-engine
 | `subset_size` | `48` |
 | `subset_size` | `48` |
 | `max_test_queries` | `24` |
 | `max_test_queries` | `24` |
 | `hybrid` | `num_queries=24`, `top1=0.7917`, `topk=1.0` |
 | `hybrid` | `num_queries=24`, `top1=0.7917`, `topk=1.0` |
-| `high_energy` | `run_demo.py build-index --resume --checkpoint-every-refs 100` |
+| `high_energy` | `evaluate.py --max-queries 24` |
 | `report.json` | 尚未生成 |
 | `report.json` | 尚未生成 |
 
 
 恢复检查命令：
 恢复检查命令：