账号恢复
身份与会话 · /identity/recovery
REGISTRY POLICY
设计契约检查全部通过,不等于产品证据通过
stable-idf4-targetnine-stateinteractioncontractsguardsevidence-planNINE-STATE FIXTURE MAP
九个状态都有产品语义,但 fixture 文件尚待实现
状态名称来自该 Screen Contract;K16 canonical key 用于跨仓聚合。产品仓必须提交确定性数据,而不是让 CI 依赖线上随机状态。
READY恢复入口就绪
FIXTURE MISSINGLOADING恢复方式加载
FIXTURE MISSINGEMPTY没有可用恢复方式
FIXTURE MISSINGPARTIAL_ERROR可信设备或人工复核部分失败
FIXTURE MISSINGERROR恢复服务不可用
FIXTURE MISSINGOFFLINE_STALE离线恢复快照只读
FIXTURE MISSINGFORBIDDEN恢复受限或安全等待
FIXTURE MISSINGDESTRUCTIVE_CONFIRM提交人工复核确认
FIXTURE MISSINGSUCCESS_RECEIPT恢复回执完成
FIXTURE MISSINGG1–G8 EVIDENCE
缺一项就保持阻断
路径是跨仓约定,不表示文件已经存在。上传凭证、token、PII、signed URL 与原始敏感 payload 永远不能成为证据内容。
Task packet
scope、owner paths、依赖、non-goals 与 rollback
ui-ci/platform-auth-recovery/task-packet.yamlScreen contract
稳定 Screen ID、route、regions、actions、states、contracts 与 risks
/api/ui-ci/platform-auth-recoveryStatic report
format、lint、typecheck、schema 与 secret scan
ui-ci/platform-auth-recovery/static/report.jsonState fixture pack
九态确定性 fixture、long/large/locale 与错误注入
ui-ci/platform-auth-recovery/fixtures/manifest.jsonConsumer contract
producer schema、consumer fixtures、compatibility 与 migration window
ui-ci/platform-auth-recovery/contracts/results.jsonExperience bundle
visual、a11y、interaction、responsive 与 native device matrix
ui-ci/platform-auth-recovery/experience/manifest.jsonSecurity negative
authz、resource binding、abuse、privacy、redaction 与 artifact integrity
ui-ci/platform-auth-recovery/security/results.jsonRelease manifest
exact commit、artifact digest、SBOM、config、migration 与 rollback drill
ui-ci/platform-auth-recovery/release/manifest.jsonProduction proof
external synthetic、telemetry、error budget、owner ack 与 incident link
ui-ci/platform-auth-recovery/production/evidence.jsonCONTRACTS & ACTIONS
实现输入
- RecoveryRequest
- TrustedDevice
- ManualReview
- RecoveryStatus
- 开始恢复
- 使用可信设备
- 提交人工复核
- 返回登录