task-signal-sync: MECE 完成信号检测（commit/verify/authorization）→ 提醒同步 tasks

[agnitum2009]

multi-signal-sync: MECE 五类完成信号（A commit/B verify/C authorization 自动检测 + D/E 收口纪律），dual-channel（footer setStatus 驻留 + context 注入 agent 不可忽略）。A/B/C 三信号验证通过（notify 确认触发）。v5 footer 驻留显示。

[tt-a1i]

OpenPI review — changes applied

P0 [fixed]

• Removed the superseded commit-task-sync extension so commit events are not auto-loaded twice.
• Made authorization detection once-per-user-message instead of once-per context call.
• Reduced obvious false positives: quoted examples, git commit --dry-run, failed commands, and negated authorization no longer trigger.
• Clear the persistent footer status during session shutdown.
• Excluded the task reminder extension from Direct/Workflow child resources because children cannot use parent-owned tasks_* tools.
• Rebased onto current main; Biome format/lint now pass.

Tests added

• authorization idempotence and new-message retrigger
• negated authorization
• quoted examples / dry-run / failed verification
• footer shutdown cleanup
• parent-only child resource boundary

Verification

• bun install --frozen-lockfile
• bun run check
• 600 Node tests and 29 Vitest tests
• npm pack: 122 files; exactly one new runtime extension
• git diff --check

P1 product decisions still open

• Whether broad authorization/verification heuristics should ship always-on.
• Whether this behavior belongs inside the existing tasks extension/config rather than a separate extension.
• README/package-facing documentation is still absent; the added knowledge-base docs are not shipped by the npm allowlist.

I am not approving or merging; final read-only re-review is running.

[tt-a1i]

Re-review update

The final P0 reviewer found two remaining heuristic false positives. Fixed at d4a27c7:

• strip single/double/curly-quoted segments before command or authorization matching, including examples like echo "example; git commit"
• reject additional authorization negations such as 未同意, while preserving a later genuinely new authorization turn

Regression tests added; full local gate remains green: 603 Node tests + 29 Vitest tests, Biome format/lint, TypeScript/Effect, frozen Bun install, pack allowlist, and git diff --check.

GitHub CI is not running yet because this repository requires workflow approval for first-time fork contributors (approval_policy: first_time_contributors). The PR should not merge until those workflows are approved and green. P1 product decisions from the prior comment remain open.

[tt-a1i]

方案结论：收敛到现有 tasks，不做完成信号推断

感谢这个 PR 抓到了真实问题：用户连续执行多个任务时，模型可能完成了工作，却没有及时调用 tasks_update，导致任务面板一直停留在旧状态。

我们进一步审计了当前 Codex CLI 0.147.0 的 update_plan 和 Hermes Agent 0.20.0 的 todo 实现。两者的共同设计是：

• task/todo 状态由模型通过结构化工具显式更新；
• runtime 负责存储、恢复、约束和 UI 投影；
• 不根据 commit、测试命令或用户的“同意/授权”措辞自动推断任务完成；
• commit / test / authorization 最多是证据候选，不能代表某个具体 task 已完成。

因此我们不会沿着独立 multi-signal-sync 正则扩展继续扩大匹配规则。复合 Shell 命令的整体成功无法证明其中某条命令成功，授权文本也无法可靠绑定到具体 task；尤其 blocked → done 不是授权解除后的通用正确迁移。

接下来方案收敛为修改现有 extensions/tasks：

1. 强化模型协议：开始某项前标记 in_progress；每项产生结果后立即同步为 done / blocked / dropped；最终答复前对本轮涉及的 tasks 做一次对账。
2. tasks_add / tasks_update 返回完整但有界的当前任务快照，让模型明确看到下一项及未收口项，而不只看到本次变更行。
3. 保持证据语义：done 仍要求 task-scoped note，但任务记录只是声明；文件、Git、测试、工具结果和用户确认仍是真相，不自动改状态，也不阻塞正常 final answer。
4. 增加“四个任务逐项执行、逐项更新、Widget 随每次 tasks_update 刷新”的自然语言 E2E 回归。
5. 保持 parent-only 边界；Direct/Workflow child 不接收无法执行的 parent task 提醒。

所以：问题成立，当前实现方向不采用；我们会把有效目标整合进已有 tasks 状态机，而不是合并基于正则的旁路提醒扩展。 前面已经完成的 P0 修复和测试对厘清边界很有帮助，感谢贡献。

[tt-a1i]

已按前面讨论的方向实现替代方案：#7

新 PR 将修复收敛进现有 extensions/tasks：逐项 in_progress / 终态同步、final 前对账，以及每次 mutation 返回完整有界快照；没有 commit/test/authorization 正则推断，也没有自动 task mutation。

真实 Pi/model 四任务 E2E 已验证严格序列 add → start/done ×4，持久化 revision 1–9 逐次推进并在最后关闭批次。这个 PR (#6) 先保持打开，等 #7 CI/审查完成后再做最终 disposition。

[tt-a1i]

#7 已完成替代实现并通过 Node 22.19/24 全部 CI 与只读复审。关闭此 PR 作为 superseded；保留讨论和修复记录，感谢贡献。