verify-tasks 1.2.0: flag "phantom completion" tasks after the implement/converge loop

[davesharpe13]

In #4576, @markuswondrak asked how verify-tasks differs from /speckit.converge. The short answer: converge finds what is not built; verify-tasks finds what is falsely marked built. Working through that question produced verify-tasks v1.2.0, which makes the two fit together.

The loop

/speckit.implement → /speckit.converge → /speckit.implement → … → Converged
                                                                  ↓
                                  /speckit.verify-tasks (fresh session)

Converge appends unbuilt work as new tasks. Those get implemented and marked [X] too, and those marks need checking. verify-tasks is the gate after Converged, before the PR.

What 1.2.0 adds

• after_converge hook, alongside the existing after_implement one.
• PARTIAL (code) vs PARTIAL (record). Is the work missing, or is the code there and the task text wrong? The tag tells you which loop to enter.
• Walkthrough action D: demote. Flip a task from [X] to [ ] (one character, after you confirm) so converge and implement pick it up. Nothing else in tasks.md is touched.
• Source-ref aware. Convergence tasks carry per FR-003 (missing); verify-tasks now reads that exact requirement instead of searching the spec for the concept.
• Fresh-session advice extends to converge. The agent that implemented is a poor judge of its own coverage, so run both in a clean session.

Install

specify extension add verify-tasks --from https://github.com/datastone-inc/spec-kit-verify-tasks/archive/refs/tags/v1.2.0.zip

Requires spec-kit 0.12.17 or later. Converge is optional; the hook and source-ref rule only matter when you use it.

Why phantom completions happen in the first place: blog post.