sanitizelisted

# Completion Closeout 完成开发后的 scoped publish、Canon closeout，或 formal task report。 Read the shared Canon contract before finalizing meaningful work: ```text /home/yhr/.agents/repos/agent-skills/references/canon-output-contract.md ``` ## Mode Routing - **Closeout** — user asks to commit, push, save, or wrap up completed work. - **Report** — user asks for a formal end-to-end report on completed work. Read `references/formal-report.md`; do not enter git mutation steps. - **Both** — user explicitly requests report plus closeout. Generate and gate the report first, include it in the confirmed file scope, then publish and promote. A one-incident troubleshooting story belongs to after-action. One reusable wrong/correct/trigger guardrail belongs to codify. ## Closeout Mode ```text 1. 检查 git 状态 2. 识别当前任务相关文件 3. 生成并确认 commit message 4. 执行 Review Gate（如本 diff 尚未通过） 5. 执行 git commit + push 6. 更新 Canon task page（替代旧的 runtime conversation 保存） 7. 更新 Canon task page § Progress / § Evidence / § Timeline 8. 写入 Canon update card / artifact reference ``` Reuse runtime-native review and Git capabilities: - Use the shared Review Gate only when equivalent evidence is not already recorded by execute, tasking, repair, or traceback. - Use ordinary scoped Git for local commit/push. - If the requested outcome includes a GitHub PR, hand off publication to `$github:yeet` instead of duplicating PR creation logic here. ## Formal Report Mode Read `references/formal-report.md` completely, th