v0.1.4

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).

---

The complete list of changes is in the changelog.

Full Changelog: v0.1.3...v0.1.4

v0.1.3

Released 2 October 2026.

Architecture decisions can now be accepted or rejected by the person who owns them, from the
command line or the Review page. Every release now carries notes like these, and the release's own
installer check runs correctly on every platform.

Highlights

• Accept or reject an architecture decision. A decision drafted with kanbanr adr new starts
  as proposed; until now the only way to accept it was to edit its file. Now:

  kanbanr adr accept ADR-0007
  kanbanr adr reject ADR-0007 --reason "the browser is enough"

  The verdict, who gave it and when are written on the decision and appear in the activity log.
  Accepting is refused while a section is unanswered; a rejection keeps its reason. The Review page
  lists proposed decisions beside the definitions waiting for approval, with Accept and Reject.

• Release notes. Each release has a notes page in the docs — this is one — and the same text
  opens its GitHub release page.

What's fixed

• The release's installer check runs from a folder of its own. In 0.1.2 it ran inside the
  repository checkout and failed on all four platforms although every install worked.

Upgrade notes

Nothing to do. Claude now drafts decisions as proposed and asks you to accept them; the skill
updates with the program (kanbanr self-update, or rerun the installer).

---

The complete list of changes is in the changelog.

Full Changelog: v0.1.2...v0.1.3

v0.1.2

Released 2 October 2026.

From this release, kanbanr's feature set is frozen until 1.0. The 0.1.x releases take fixes,
documentation, and the work that makes the 1.0 promise checkable. This one writes that promise
down, makes boards safe to share across versions, and ships the VS Code extension.

Highlights

• What 1.0 keeps compatible is written down. Stability lists what
  stays stable from 1.0 until 2.0 — the board format and config.yaml, the .kanbanr marker, CLI
  commands, flags, exit status and --json, the monitor's /api/…, the commit trailer and hooks —
  what is not covered, and how anything stable is deprecated before it is removed.
• An older kanbanr no longer deletes what a newer one wrote. Rewriting an item, a milestone, the
  config or the charter used to drop every field the running version did not know. Unknown fields
  are now kept and written back unchanged, so machines sharing a board can run different versions.
• The VS Code extension ships with every release as kanbanr-vscode-<version>.vsix, at the
  program's version and covered by SHA256SUMS.

What's new

• The release installs itself on every platform it publishes for. After publishing, it runs
  install.sh on macOS and install.ps1 on Windows (as irm … | iex, the way the docs say)
  beside the two Linux containers.

What's fixed

• The VS Code extension packages. It now names the repository and the docs site, carries its
  licence, and installs from the packaged .vsix in a clean VS Code.

Known limits

• The new installer check reported all four platforms as failed for this release, although every
  install worked and named 0.1.2 and its commit: the check ran kanbanr init inside the repository
  checkout. Fixed in 0.1.3.
• The extension is not on Open VSX or the Visual Studio Marketplace yet.

Installing the extension

gh release download v0.1.2 -R startr-trade/kanbanr -p 'kanbanr-vscode-*.vsix'
code --install-extension kanbanr-vscode-0.1.2.vsix

---

The complete list of changes is in the changelog.

Full Changelog: v0.1.1...v0.1.2

v0.1.1

Released 2 October 2026.

A fix release for the container image. The binaries and installers are unchanged in behaviour from
0.1.0; the image now carries exactly the program the archives do.

What's fixed

• The image's kanbanr names its build. kanbanr --version in
  ghcr.io/startr-trade/kanbanr printed (unknown, built unknown), because the image is built
  without .git. It now names the commit and date, like the archives — and the release refuses to
  push an image that cannot.
• The image's kanbanr carries the skill. Its binary embedded no Claude Code skill, so it was not
  quite the program the archives ship under the same version. It does now, and the release checks
  the image installs the repository's skill, file for file, before pushing it.

Upgrade notes

Nothing to do for the binary. If you run the monitor from the image, pull v0.1.1 (or latest).

docker pull ghcr.io/startr-trade/kanbanr:v0.1.1

---

The complete list of changes is in the changelog.

Full Changelog: v0.1.0...v0.1.1

v0.1.0

Released 1 October 2026.

kanbanr is a system of record for development done with Claude Code: the plan, the reasoning and
the evidence live on a git-backed kanban board beside your code, and Claude keeps them current as
part of doing the work. This is the first release anyone outside the project can install. It
carries everything the project was built with, because kanbanr has been developed on its own board
from the start — the board is public.

Highlights

• One binary, installed in one line. The CLI, the live monitor and the Claude Code skill are
  one executable, checked against the release's SHA256SUMS by the installer. The installer puts
  the matching skill in place when Claude Code is installed.
• A board Claude recovers from. Every session starts from the board; a stop hook reminds Claude
  to record what changed. Nothing about the plan lives only in a transcript.
• Work that says why it exists. Each item carries a definition — a statement, the goals it
  serves, the six Zachman questions, EARS requirements each naming the test that proves it — and is
  approved before work starts. Change the definition and the approval lapses.
• Your process, as configuration. Kanban, Scrum, agile, TOGAF, PDCA, a design-control flow or
  your own file: each stage declares what an item needs to enter it and who signs off.
• Code traced to its reason. Commits carry Refs: kanbanr:FEAT-…; kanbanr why <file>:<line>
  walks from a line of code to its requirement and goal.
• Set up by interview. Say "set up kanbanr for this project" and Claude interviews you in plan
  mode — where the board lives, who you are, a charter drafted from your repository, the process —
  and sets it all up when you approve the plan.

What's new

• The method: a project charter with goals; feature definitions; approval, ratification and
  named sign-offs; EARS and ISO/IEC 25010 checks; tests carried through planned → red → green;
  defects with their origin; retrospectives per milestone; lessons with confidence that decays.
• Processes: declarable gates per status (block or warn), presets as data, kanbanr check
  saying what the next stage needs, --override with the reason kept.
• Cadence, when you want it: sprints with a burndown derived from what actually moved, story
  points, releases planned up front and cut with notes.
• Traceability: one item, one branch; commit hooks that refuse unreferenced commits; trace
  and why; architecture decisions as documents joined to the items they affect.
• The monitor: board, item pages, review queue, sprints and releases, Gantt, workflow, charter
  and lessons, docs with Mermaid diagrams, a portfolio across projects, light and dark themes —
  updating live, read-only unless you start it to take verdicts.
• Sharing: a board is its own git repository; push it to a remote to share it. The push policy
  is a board setting (kanbanr remote push-policy).
• Also: a container image of the monitor, a GitHub issue mirror, import from existing task
  trackers, session summaries, a VS Code extension (in the repository).

Known limits

• The VS Code extension is not published yet; build it from editor/vscode/.
• The container image's kanbanr --version says unknown and its binary carries no skill —
  fixed in 0.1.1.
• Only the Linux installer is verified by the release; macOS and Windows are built and tested in
  CI but their installers are not yet run end to end.

Installing

curl -fsSL https://github.com/startr-trade/kanbanr/releases/download/v0.1.0/install.sh | sh -s -- --version v0.1.0

See Installation. The complete list of changes is in the
changelog.

---

The complete list of changes is in the changelog.