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.0 KiB
1.0 KiB
草稿:feature/svc-deploy-u1-account-binding 任务卡
状态:待授权。主提案批准并获实施授权后,在共享主检出执行:
RECEIPT=/tmp/precheck-svc-deploy-u1.json CMD="make precheck" make evidence
make task-start NAME=feature/svc-deploy-u1-account-binding PRECHECK_RECEIPT=/tmp/precheck-svc-deploy-u1.json
将本草稿字段拷入新卡并删除本文件或改为「已启动」链接。
建议填写
- 主记录:
modules/documents/docs/proposals/2026-10-12-svc-unified-deploy-and-login-key.mdr1 §7 U1 - 规格:
docs/svc-deploy/u1-instance-account-binding.mdv0.1 - 目标:账户 CLI 绑定实例 manifest;OpenExisting;无 flock 拒绝冲突操作;不破坏 recovery U1
- 非目标:U2 下载、U3 doctor、U4 Key 语义、U5 页面
- 兄弟任务:可与
feature/svc-deploy-u4-login-key共用同一 R0 - 验收:规格 §6 T1–T5;治理回归;真实 PG 缺环境 NOT_RUN
- 启动授权:未授权(须主提案阶段批准 + 明确实施授权)