kanbanr 0.1.4 — Completed means proven

Released 3 October 2026.

An item now reaches Completed only when its requirements are proven, however it gets there. And the installers can put the VS Code extension into your editor, in the same step as the program.

Highlights

• Completed means proven. On a workflow with no declared gates, ticking an item’s last task used to complete it even when its requirements had no green test, although kanbanr finish refused the same move. Now the last task completes a defined item only when every requirement is proven; otherwise the item stays where it is, and the task command names what is missing:

  $ kanbanr task state FEAT-001 TL-001 T1 Completed
  FEAT-001/TL-001 T1 -> Completed (feature now In Progress)
    all tasks are done, but it stays in In Progress: R-1 has tests but none is green — not yet
    proven — record the evidence with `kanbanr test`, or move it by hand if you disagree
  

  A batch is judged once, after its last operation, so one that ticks the last task and then adds another can no longer complete the item in between.

• The VS Code extension, from the installer. Add --vscode and the installer also installs the release’s extension into every editor it finds — VS Code, VSCodium, Cursor, Windsurf — or --vscode=codium into one. Without the option nothing touches an editor.

  curl -fsSL https://github.com/startr-trade/kanbanr/releases/latest/download/install.sh | sh -s -- --vscode
  

What’s new

• kanbanr editor install downloads the .vsix of the version you are running over https, checks it against the release’s SHA256SUMS, and installs it (--editor codium for one editor). kanbanr self-update now keeps the extension in step in every editor that has it, as it already did the Claude Code skill.
• The extension is on Open VSX, for VSCodium, Cursor and Windsurf, and from this release on every version is published there automatically.

Upgrade notes

• Items without a definition, items created before your charter was adopted, and workflows that declare their own gates behave exactly as before.
• On a workflow without gates, an item whose last task you complete may now stay in progress. That is the fix: record its evidence (kanbanr test <CODE> <R-n> <test> green) and it completes, or move it by hand if you disagree.
• Update with kanbanr self-update (macOS and Linux) or by rerunning the installer (Windows).