BUG-1355project-13高已修复deploy-script

'后续再做' 等于'永远不做' — 每次会话都重复踩同一个坑

发现：2026-10-12验证：2026-10-12置信度：70%

症状

User frustration multiple times in this session: '那时候早忘了' (we'll forget by then). The Ledgent package name bug alone caused 9 APK downloads because each individual fix 'forgot' that another location also hardcoded the old brand name. 'Do later' without trigger conditions is effectively 'do never'.

根因

Pattern identified across this session: 'We should do X later' decisions had no mechanism to ensure they actually got done. Examples: 1) Channel table design decided 'do when 2nd channel launches' — but no trigger condition was written. 2) APK package name hardcoded Ledgent 3 times — each fix was forgotten. 3) Multiple hardcoded URLs — each 'fix later' became permanent hardcode. Root cause: 'later' = 'never' without explicit trigger conditions and persistence.

修复方案

Established Three-Layer Guarantee for any 'do later' decision: 1. CODE LAYER: migration/TODO comments write 'WHEN to do + WHAT to do + HOW to trigger' (not vague TODO, explicit checklist) 2. GOVERNANCE LAYER: write to .governance/attention/latest.md L3 — this file is loaded at every session start 3. HISTORY LAYER: commit message contains full context + execution checklist — git log --grep will find it Documented as §11.31 in AI-KNOWLEDGE-BASE.md. Applied to DS-063 (channel refactor): V112 SQL has 20+ line header explaining step-1 (pre-install tables) vs step-2 (FK refactor, trigger = 2nd channel launch).

错误签名

'后续再做' never executed — no trigger condition, no checklist, forgotten by next session or agent

技术信息

来源项目

project-13

涉及文件

backend/src/main/resources/db/migration/V112__channel_and_subject_tables.sql, .governance/attention/latest.md, docs/AI-KNOWLEDGE-BASE.md

标签

project-13, mcp-reported, source-agent