Record the recovery proposal r1 in the task card and project index

Why: finish the prior session's in-flight records so the tree is clean before the resume precheck (P1.1 object pinning).

Evidence: SELF - documents gitlink now points at 54fc24e (proposal r1 + review record + INDEX); task card carries the prior session's evidence rows and authorization scope.

Impact: task metadata and submodule pointer only; no business code.

Refs: modules/documents/docs/proposals/2026-10-12-service-restart-data-recovery.md

PROJECT.md

@@ -32,6 +32,10 @@ U2 起实施与部署分别评审。
 
 - [RDM 最终目标核对与完整交付方案 r1](modules/documents/docs/proposals/2026-10-11-rdm-final-target-completion.md)：系统级项目、上限内权限覆盖、私域协作、全部文档三权与完整业务链；34 UR／68 SR／10 F 逐条映射；方案已随 #340 合入（2026-10-11），U1 需求基线核对经 RDM #199/#200 落地，U2 起未启动。
 
+- [服务重启与全量数据恢复方案 r1](modules/documents/docs/proposals/2026-10-12-service-restart-data-recovery.md)：
+  svc 启停、异常进程/主机退出后的依赖、配置/数据身份、任务/HITL/副作用、文件与组合备份恢复；
+  2026-10-12 待人工评审，实施、故障注入、部署与运行验收 NOT_RUN；衔接协作存储案及在途 svc-autorecover。
+
 ## 验证
 
 `make test` 先核对子模块工作树与固定指针，再运行治理脚本、公开边界、跨仓指针、库及各模块