Why: land the approved review conclusions as a formal proposal, U1/U4 specs, and draft task cards without starting business implementation. Evidence: SELF precheck READY (receipt in task card); docs-only change. Impact: planning docs and Documents gitlink; runtime behavior unchanged. Refs: .task/feature-svc-unified-deploy-login-key.md Co-authored-by: Cursor <cursoragent@cursor.com>
1.1 KiB
1.1 KiB
草稿:feature/svc-deploy-u4-login-key 任务卡
状态:待授权。主提案批准并获实施授权后,在共享主检出执行:
RECEIPT=/tmp/precheck-svc-deploy-u4.json CMD="make precheck" make evidence
make task-start NAME=feature/svc-deploy-u4-login-key PRECHECK_RECEIPT=/tmp/precheck-svc-deploy-u4.json
将本草稿字段拷入新卡并删除本文件或改为「已启动」链接。
建议填写
- 主记录:
modules/documents/docs/proposals/2026-10-12-svc-unified-deploy-and-login-key.mdr1 §7 U4 - 规格:
docs/svc-deploy/u4-one-time-login-key.mdv0.1 - 目标:独立 login_keys;原子兑换;受限会话中间件;设密事务;无密码开户/恢复签发;OpenExisting 最小集
- 非目标:svc 账户接线与登录页(U5);部署来源(U2/U3)
- 组件:Backend 为主;Dev 仅 gitlink / 文档引用;Frontend 不强制本增量改动
- 兄弟任务:可与
feature/svc-deploy-u1-account-binding共用同一 R0 - 验收:规格 §7 T1–T11;SQLite+PG;并发兑换;治理/Backend 测试
- 启动授权:未授权(须主提案阶段批准 + 明确实施授权)