kanbo-cli 0.1.3 → 0.2.1

package/LICENSE

@@ -1,21 +1,75 @@
-MIT License
-
-Copyright (c) 2026 Krowli
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+Required Notice: Copyright (c) 2026 Krowli (https://github.com/Krowli/kanbo)
+
+# PolyForm Noncommercial License 1.0.0
+
+<https://polyformproject.org/licenses/noncommercial/1.0.0>
+
+## Acceptance
+
+In order to get any license under these terms, you must agree to them as both strict obligations and conditions to all your licenses.
+
+## Copyright License
+
+The licensor grants you a copyright license for the software to do everything you might do with the software that would otherwise infringe the licensor's copyright in it for any permitted purpose.  However, you may only distribute the software according to [Distribution License](#distribution-license) and make changes or new works based on the software according to [Changes and New Works License](#changes-and-new-works-license).
+
+## Distribution License
+
+The licensor grants you an additional copyright license to distribute copies of the software.  Your license to distribute covers distributing the software with changes and new works permitted by [Changes and New Works License](#changes-and-new-works-license).
+
+## Notices
+
+You must ensure that anyone who gets a copy of any part of the software from you also gets a copy of these terms or the URL for them above, as well as copies of any plain-text lines beginning with `Required Notice:` that the licensor provided with the software.  For example:
+
+> Required Notice: Copyright Yoyodyne, Inc. (http://example.com)
+
+## Changes and New Works License
+
+The licensor grants you an additional copyright license to make changes and new works based on the software for any permitted purpose.
+
+## Patent License
+
+The licensor grants you a patent license for the software that covers patent claims the licensor can license, or becomes able to license, that you would infringe by using the software.
+
+## Noncommercial Purposes
+
+Any noncommercial purpose is a permitted purpose.
+
+## Personal Uses
+
+Personal use for research, experiment, and testing for the benefit of public knowledge, personal study, private entertainment, hobby projects, amateur pursuits, or religious observance, without any anticipated commercial application, is use for a permitted purpose.
+
+## Noncommercial Organizations
+
+Use by any charitable organization, educational institution, public research organization, public safety or health organization, environmental protection organization, or government institution is use for a permitted purpose regardless of the source of funding or obligations resulting from the funding.
+
+## Fair Use
+
+You may have "fair use" rights for the software under the law. These terms do not limit them.
+
+## No Other Rights
+
+These terms do not allow you to sublicense or transfer any of your licenses to anyone else, or prevent the licensor from granting licenses to anyone else.  These terms do not imply any other licenses.
+
+## Patent Defense
+
+If you make any written claim that the software infringes or contributes to infringement of any patent, your patent license for the software granted under these terms ends immediately. If your company makes such a claim, your patent license ends immediately for work on behalf of your company.
+
+## Violations
+
+The first time you are notified in writing that you have violated any of these terms, or done anything with the software not covered by your licenses, your licenses can nonetheless continue if you come into full compliance with these terms, and take practical steps to correct past violations, within 32 days of receiving notice.  Otherwise, all your licenses end immediately.
+
+## No Liability
+
+***As far as the law allows, the software comes as is, without any warranty or condition, and the licensor will not be liable to you for any damages arising out of these terms or the use or nature of the software, under any kind of legal claim.***
+
+## Definitions
+
+The **licensor** is the individual or entity offering these terms, and the **software** is the software the licensor makes available under these terms.
+
+**You** refers to the individual or entity agreeing to these terms.
+
+**Your company** is any legal entity, sole proprietorship, or other kind of organization that you work for, plus all organizations that have control over, are under the control of, or are under common control with that organization.  **Control** means ownership of substantially all the assets of an entity, or the power to direct its management and policies by vote, contract, or otherwise.  Control can be direct or indirect.
+
+**Your licenses** are all the licenses granted to you for the software under these terms.
+
+**Use** means anything you do with the software requiring one of your licenses.

package/README.md

@@ -2,7 +2,7 @@
 
 [![CI](https://github.com/Krowli/kanbo/actions/workflows/ci.yml/badge.svg)](https://github.com/Krowli/kanbo/actions/workflows/ci.yml)
 [![npm version](https://img.shields.io/npm/v/kanbo-cli.svg)](https://www.npmjs.com/package/kanbo-cli)
-[![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
+[![License: PolyForm Noncommercial](https://img.shields.io/badge/license-PolyForm%20Noncommercial-orange.svg)](LICENSE)
 [![Node](https://img.shields.io/badge/node-%5E22.19%20%7C%7C%20%3E%3D24.11-brightgreen.svg)](docs/installation.md)
 
 **A Kanban board your AI agents drive, and you watch.** kanbo is a board that lives next to your code — a SQLite file in the project, or a shared Postgres/Supabase database — with a command line and an MCP server made for coding agents. Agents take cards, move them, write a one-line status at every step, split work into subtasks and link their pull requests; when they need you, they hand the card over and stop. Only a person approves or sends a card back, and kanbo enforces that rather than asking nicely. You follow along in a terminal or on a small board page in your browser.
@@ -77,4 +77,6 @@ Every entry point — the CLI, the MCP server, the HTTP server — calls the sam
 
 ## License
 
-[MIT](LICENSE)
+[PolyForm Noncommercial 1.0.0](LICENSE) — free for personal, research, educational and other noncommercial use. Commercial use — selling it, or building it into a paid product or service — needs a separate license: write to lionmause999@gmail.com.
+
+Versions up to and including 0.2.0 were released under MIT and stay under MIT.

package/dist/cli.cjs

@@ -3084,7 +3084,7 @@ var import_picocolors = /* @__PURE__ */ __toESM((/* @__PURE__ */ __commonJSMin((
 * `package.version`. A build carries it as a literal; running from source
 * (tests, `tsx`) reads the package's own `package.json` instead.
 */
-const KANBO_PACKAGE_VERSION = "0.1.3";
+const KANBO_PACKAGE_VERSION = "0.2.1";
 /**
 * Every exit code this tool promises, and what it means — the capabilities
 * manifest's `exitCodes` reads this rather than naming the codes again. `0` and
@@ -10789,15 +10789,12 @@ async function approve(store, issueId, input, actor, scope) {
 * leaves even says "returned by you".
 */
 async function returnCard(store, issueId, input, actor, scope) {
-	if (actor.kind !== "user") throw new BoardError("board_return_requires_user", {
-		issueId,
-		actorKind: actor.kind
-	});
 	return await runBoardWrite(store, async ({ tx }) => {
+		await ensureDefaultColumns(tx, (await requireCard$1(tx, issueId)).workspaceId, { tx });
+		const target = await assertReturnable(tx, issueId, input, actor);
 		const card = await requireCard$1(tx, issueId);
-		const columns = await ensureDefaultColumns(tx, card.workspaceId, { tx });
 		const updates = {
-			statusId: (input.toStatusName ? await requireColumn(tx, card.workspaceId, input.toStatusName) : previousColumn(columns, card)).id,
+			statusId: target.id,
 			waitingFor: null,
 			updatedAt: currentUnixSeconds()
 		};
@@ -10818,6 +10815,27 @@ async function returnCard(store, issueId, input, actor, scope) {
 		};
 	}, scope);
 }
+/**
+* Every reason `returnCard` would refuse, asked on reads alone, and the column
+* the card would go back to when none applies.
+*
+* `returnCard` asks exactly this inside its write. A caller that has to undo
+* something of its own before the return — stop listening for the approval the
+* card is waiting on, say — asks it first, so a return the board refuses leaves
+* that untouched. The refusals are the same `BoardError` codes: an actor who is
+* not a person (`board_return_requires_user`), a card that is not there
+* (`issue_not_found`), a named column the workspace does not hold
+* (`issue_status_not_found`), and a card already in the first column with no
+* column named (`board_return_no_previous_column`).
+*/
+async function assertReturnable(store, issueId, input, actor) {
+	if (actor.kind !== "user") throw new BoardError("board_return_requires_user", {
+		issueId,
+		actorKind: actor.kind
+	});
+	const card = await requireCard$1(store, issueId);
+	return input.toStatusName ? await requireColumn(store, card.workspaceId, input.toStatusName) : previousColumn(await listColumns(store, card.workspaceId), card);
+}
 /** Write a comment on the card, as the actor unless the caller names another author. */
 async function addComment(store, input, actor, scope) {
 	return await runBoardWrite(store, async ({ tx }) => {
@@ -11695,6 +11713,7 @@ function createBoardOps(store) {
 		waitApproval: async (issueId, input, actor, scope) => await waitApproval(store, issueId, input, actor, scope),
 		approve: async (issueId, input, actor, scope) => await approve(store, issueId, input, actor, scope),
 		returnCard: async (issueId, input, actor, scope) => await returnCard(store, issueId, input, actor, scope),
+		assertReturnable: async (issueId, input, actor) => await assertReturnable(store, issueId, input, actor),
 		readApproval: async (issueId) => await readApproval(store, issueId),
 		linkPullRequest: async (issueId, urlOrRef, actor, scope) => await linkPullRequest(store, issueId, urlOrRef, actor, scope),
 		unlinkPullRequest: async (issueId, linkId, actor, scope) => await unlinkPullRequest(store, issueId, linkId, actor, scope),
@@ -43395,21 +43414,6 @@ function sendBoardPage(response, pathname, assets) {
 * reason turned around: the answer will be yes once the card meets them, and
 * `details.unmet` says what is missing.
 *
-* The five failures about where a board is kept read the same rule. A database
-* that holds no board this build can speak for is 409 — the setting is there,
-* the board behind it is not yet, and `board-storage prepare` is what settles
-* that — and one nobody could reach at all is 503, because nothing about the
-* request was wrong. A workspace naming no board at all is 404: the caller
-* asked about a setting that is not there. A board still holding cards when
-* somebody asks to point the workspace elsewhere is 409, because the answer
-* would have been yes on an empty board and `board-storage migrate` is what
-* makes it one. An operation naming cards from two different boards is 400: no
-* transaction reaches both, so the caller asked for something that cannot be
-* done. A copy that would land on a card number or a column name the target
-* already holds under a different id is 409 for the same reason the others
-* are: the answer would have been yes on a target that did not hold that
-* board, and `details.conflicts` names every value that clashed.
-*
 * A failure may also be renamed here: the package names its codes after the
 * board, while every error the `/issues` routes answer with is named after the
 * issue, and a client matching on `issue_*` should not have to learn a second
@@ -43431,10 +43435,6 @@ const BOARD_ERROR_RESPONSES = {
 		message: "The card does not meet what that column asks for yet",
 		code: "issue_column_rules_unmet"
 	},
-	board_copy_conflict: {
-		status: 409,
-		message: "That board already holds cards or columns of this workspace under the same numbers or names; nothing was copied"
-	},
 	board_entry_rule_invalid: {
 		status: 400,
 		message: "Unknown column entry rule"
@@ -43443,10 +43443,6 @@ const BOARD_ERROR_RESPONSES = {
 		status: 400,
 		message: "Execution mode cannot change once the card has been launched"
 	},
-	board_mixed_workspaces: {
-		status: 400,
-		message: "Those cards are not all on the same board"
-	},
 	board_pull_request_invalid: {
 		status: 400,
 		message: "Not a GitHub pull request: give its URL or owner/repo#number"
@@ -43506,22 +43502,6 @@ const BOARD_ERROR_RESPONSES = {
 		status: 400,
 		message: "A sprint cannot start after it is due"
 	},
-	board_storage_not_configured: {
-		status: 404,
-		message: "This workspace names no board storage"
-	},
-	board_storage_not_empty: {
-		status: 409,
-		message: "That board still holds cards of this workspace; move them with migrate before changing where the board is kept"
-	},
-	board_storage_not_prepared: {
-		status: 409,
-		message: "That board has not been prepared yet"
-	},
-	board_storage_unavailable: {
-		status: 503,
-		message: "That board could not be reached"
-	},
 	issue_comment_delete_requires_user: {
 		status: 403,
 		message: "Only a person can delete a comment the board wrote"