Refs: Dev docs/svc-deploy/2026-10-13-login-recovery-contract.md
Why: 2026-10-13 登录恢复流程已按用户「按此方案实施」批准并合入（Backend #187、Frontend #76、Dev #504）；主方案按谱系惯例回写三裁定、实施记录与证据指针。
Evidence: Dev #504 HEAD CI 三作业 success（GATE）；浏览器验收收据 be7ae9a2/b3a9e691 绑定 Dev HEAD 268ef29（SELF）。
Impact: 仅实施记录（r3），不改 R/KTD/U 编号语义；U7 明确不记完成（原子开户/CLI 凭据交付余量）；INDEX.md 状态行同步。
Refs: Dev docs/svc-deploy/2026-10-13-login-recovery-contract.md
Why: The 2026-10-13 login recovery flow was approved and merged
(Backend #187, Frontend #76, Dev #504); the master proposal must carry
the three adjudications, implementation record, and evidence pointers
per the repo's lineage conventions.
Evidence: Dev #504 HEAD CI (test/test-pg/svc-realcombo) success; browser
acceptance receipts be7ae9a2/b3a9e691 bound to Dev HEAD 268ef29 (SELF).
Impact: r3 is an implementation record only; R/KTD/U numbering semantics
unchanged; U7 explicitly NOT marked complete (atomic bootstrap and CLI
credential delivery remain). INDEX.md status line updated.
Refs: Dev docs/svc-deploy/2026-10-13-login-recovery-contract.md
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Why: 2026-10-13 登录恢复流程已按用户「按此方案实施」批准并合入（Backend #187、Frontend #76、Dev #504）；主方案按谱系惯例回写三裁定、实施记录与证据指针。
Evidence: Dev #504 HEAD CI 三作业 success（GATE）；浏览器验收收据 be7ae9a2/b3a9e691 绑定 Dev HEAD 268ef29（SELF）。
Impact: 仅实施记录（r3），不改 R/KTD/U 编号语义；U7 明确不记完成（原子开户/CLI 凭据交付余量）；INDEX.md 状态行同步。
Refs: Dev docs/svc-deploy/2026-10-13-login-recovery-contract.md
92b8df4a85to0b290b7461