kanban-pro(vider)

Built for the agent that reads it. A session registered once asks list_work and gets its cards with the legal moves inline, claims one under a lease, moves it, reports what it found and asks its question, all with instructions the server hands it up front, so it acts on the first call instead of guessing at a second. The repository is written the same way: paste Do I need this? and the link into any agent and it answers plainly, installs it and proves it works by moving a card.

An augmenting proxy, not just a board. One canonical API sits over swappable backends, its own SQLite store, an ephemeral one, a Hermes harness or a whitelisted Jira project, and where the backend lacks a capability kanban-pro supplies it on top: WIP limits, flow enforcement, comments, relations, checks. capabilities reports each as native, polyfilled or unavailable, so an agent knows exactly what it can rely on, and the backend stays the system of record.

The flow is fixed, and everything about it is set over MCP. Each board carries a state machine over its columns, stored on the board and administered from the session with set_flow, set_transitions, declare_checks and a WIP limit per column; no config file, so an orchestrator reshapes the pipeline while it runs. An illegal move is refused, not logged. A card cannot advance until verification that someone else declared has been recorded as passed with evidence. A crashed agent's lease expires and its card comes back. force=true works, and is stamped on the event forever.

Every write carries the acting agent, and an append-only change feed with cursors makes the board the source of truth rather than a transcript. wait_changes turns it into a queue: workers wake on the feed, a stuck worker raises attention to whichever actor may decide, a reviewer agent as readily as a person, and only what no agent may decide reaches you.