feat(blueprint/buff): files 重叠推断降为兜底,同批已有显式推进则不推断 #27
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "feat/blueprint-buff"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
背景
合并 PR #24/#25/#26 后,P6/P7/P8(agent-client-parity)与 A4(architecture-evolution)未开工却被 buff 自动标 🔵,仅因
files与 P1/P3/P9 共用onboarding.rs/mcp_inject.rs/mcp_tools.rs等文件;主仓库工作区反复出现需人工恢复的未提交改动。enterprise-system 2026-07-22 回传过同类问题,本次为第二例。根因:两阶段锁下真正在做的卡提交落地时已是 🔵/✅,
files重叠只能碰到仍为 📋 的卡——选择偏差使精度结构性偏低,不是调匹配规则能解决的。改动(方案 B,用户已确认)
infer_task_marks三道闸:last_commit非 HEAD 祖先(checkout/reset/rebase)→ 跳过,git 出错记日志;本批.blueprint/modulespatch 新增### 🔵/✅/🔴标题行(非原样搬移)→ 归属已显式,不推断;余下才走 files 匹配兜底HEAD)/边界、尾逗号空项丢弃、「、」「,」作分隔Agent 自验
cargo test:256 passed / 0 failed;buff.rs首批 9 条测试(纯函数 + 临时 git 仓库端到端:同批显式推进不推断、无推进兜底标 🔵、checkout 非祖先跳过、首次接入兜底)239d9fd/79853b7对 P6/P7/P8/A4 零命中rustfmt无差异,buff.rs无编译警告没验什么
人终验
重装炼境后合并下一个 PR,主仓库工作区不再出现无关卡被标 🔵。
🤖 Generated with Claude Code