kanbo-cli 0.1.0

package/dist/drizzle-postgres/meta/_journal.json

@@ -0,0 +1,48 @@
+{
+  "version": "7",
+  "dialect": "postgresql",
+  "entries": [
+    {
+      "idx": 0,
+      "version": "7",
+      "when": 1790077635921,
+      "tag": "0000_board",
+      "breakpoints": true
+    },
+    {
+      "idx": 1,
+      "version": "7",
+      "when": 1790112642551,
+      "tag": "0001_history_order",
+      "breakpoints": true
+    },
+    {
+      "idx": 2,
+      "version": "7",
+      "when": 1790227027724,
+      "tag": "0002_issue_pull_requests",
+      "breakpoints": true
+    },
+    {
+      "idx": 3,
+      "version": "7",
+      "when": 1790244865401,
+      "tag": "0003_milestone_start_date",
+      "breakpoints": true
+    },
+    {
+      "idx": 4,
+      "version": "7",
+      "when": 1790255382146,
+      "tag": "0004_status_entry_rules",
+      "breakpoints": true
+    },
+    {
+      "idx": 5,
+      "version": "7",
+      "when": 1790266707460,
+      "tag": "0005_run_external_session_ref",
+      "breakpoints": true
+    }
+  ]
+}

package/dist/drizzle-sqlite/0000_board.sql

@@ -0,0 +1,133 @@
+CREATE TABLE `issue_comments` (
+	`id` text PRIMARY KEY NOT NULL,
+	`issue_id` text NOT NULL,
+	`content` text NOT NULL,
+	`author_kind` text DEFAULT 'user' NOT NULL,
+	`author_id` text,
+	`source_chat_session_id` text,
+	`agent_activity_id` text,
+	`dedupe_key` text,
+	`created_at` integer DEFAULT (unixepoch()) NOT NULL,
+	FOREIGN KEY (`issue_id`) REFERENCES `issues`(`id`) ON UPDATE no action ON DELETE cascade
+);
+--> statement-breakpoint
+CREATE INDEX `issue_comments_issue_id_idx` ON `issue_comments` (`issue_id`);--> statement-breakpoint
+CREATE UNIQUE INDEX `issue_comments_issue_dedupe_idx` ON `issue_comments` (`issue_id`,`dedupe_key`);--> statement-breakpoint
+CREATE TABLE `issue_field_changes` (
+	`id` text PRIMARY KEY NOT NULL,
+	`issue_id` text NOT NULL,
+	`field` text NOT NULL,
+	`from_value` text,
+	`to_value` text,
+	`actor_kind` text DEFAULT 'user' NOT NULL,
+	`actor_id` text,
+	`source_chat_session_id` text,
+	`created_at` integer DEFAULT (unixepoch()) NOT NULL,
+	FOREIGN KEY (`issue_id`) REFERENCES `issues`(`id`) ON UPDATE no action ON DELETE cascade
+);
+--> statement-breakpoint
+CREATE INDEX `issue_field_changes_issue_id_idx` ON `issue_field_changes` (`issue_id`);--> statement-breakpoint
+CREATE TABLE `issue_milestones` (
+	`id` text PRIMARY KEY NOT NULL,
+	`workspace_id` text NOT NULL,
+	`title` text NOT NULL,
+	`description` text,
+	`due_date` integer,
+	`status` text DEFAULT 'open' NOT NULL,
+	`created_at` integer DEFAULT (unixepoch()) NOT NULL,
+	`updated_at` integer DEFAULT (unixepoch()) NOT NULL
+);
+--> statement-breakpoint
+CREATE INDEX `issue_milestones_workspace_id_idx` ON `issue_milestones` (`workspace_id`);--> statement-breakpoint
+CREATE TABLE `issue_relations` (
+	`id` text PRIMARY KEY NOT NULL,
+	`source_issue_id` text NOT NULL,
+	`target_issue_id` text NOT NULL,
+	`type` text NOT NULL,
+	`created_at` integer DEFAULT (unixepoch()) NOT NULL,
+	FOREIGN KEY (`source_issue_id`) REFERENCES `issues`(`id`) ON UPDATE no action ON DELETE cascade,
+	FOREIGN KEY (`target_issue_id`) REFERENCES `issues`(`id`) ON UPDATE no action ON DELETE cascade
+);
+--> statement-breakpoint
+CREATE INDEX `issue_relations_source_issue_id_idx` ON `issue_relations` (`source_issue_id`);--> statement-breakpoint
+CREATE INDEX `issue_relations_target_issue_id_idx` ON `issue_relations` (`target_issue_id`);--> statement-breakpoint
+CREATE UNIQUE INDEX `issue_relations_pair_type_unique` ON `issue_relations` (`source_issue_id`,`target_issue_id`,`type`);--> statement-breakpoint
+CREATE TABLE `issue_runs` (
+	`id` text PRIMARY KEY NOT NULL,
+	`issue_id` text NOT NULL,
+	`launched_by_kind` text DEFAULT 'user' NOT NULL,
+	`launched_by_id` text,
+	`agent_id` text,
+	`agent_name` text NOT NULL,
+	`host` text,
+	`execution_mode` text DEFAULT 'worktree' NOT NULL,
+	`branch` text,
+	`worktree_path` text,
+	`state` text DEFAULT 'running' NOT NULL,
+	`chat_session_id` text,
+	`started_at` integer DEFAULT (unixepoch()) NOT NULL,
+	`ended_at` integer,
+	FOREIGN KEY (`issue_id`) REFERENCES `issues`(`id`) ON UPDATE no action ON DELETE cascade
+);
+--> statement-breakpoint
+CREATE INDEX `issue_runs_issue_id_idx` ON `issue_runs` (`issue_id`);--> statement-breakpoint
+CREATE INDEX `issue_runs_issue_state_idx` ON `issue_runs` (`issue_id`,`state`);--> statement-breakpoint
+CREATE INDEX `issue_runs_chat_session_idx` ON `issue_runs` (`chat_session_id`);--> statement-breakpoint
+CREATE TABLE `issue_statuses` (
+	`id` text PRIMARY KEY NOT NULL,
+	`workspace_id` text NOT NULL,
+	`name` text NOT NULL,
+	`description` text,
+	`color` text,
+	`category` text DEFAULT 'unstarted' NOT NULL,
+	`order` integer DEFAULT 0 NOT NULL,
+	`created_at` integer DEFAULT (unixepoch()) NOT NULL
+);
+--> statement-breakpoint
+CREATE INDEX `issue_statuses_workspace_id_idx` ON `issue_statuses` (`workspace_id`);--> statement-breakpoint
+CREATE UNIQUE INDEX `issue_statuses_workspace_name_unique` ON `issue_statuses` (`workspace_id`,`name`);--> statement-breakpoint
+CREATE TABLE `issues` (
+	`id` text PRIMARY KEY NOT NULL,
+	`workspace_id` text NOT NULL,
+	`number` integer NOT NULL,
+	`status_id` text,
+	`milestone_id` text,
+	`parent_issue_id` text,
+	`title` text NOT NULL,
+	`description` text,
+	`priority` text DEFAULT 'none' NOT NULL,
+	`labels` text DEFAULT '[]' NOT NULL,
+	`assignee_kind` text,
+	`assignee_id` text,
+	`due_date` integer,
+	`created_by_kind` text DEFAULT 'user' NOT NULL,
+	`created_by_id` text DEFAULT '__self__' NOT NULL,
+	`source_chat_session_id` text,
+	`delegate_agent_id` text,
+	`delegate_provider_target_id` text,
+	`context_refs` text DEFAULT '[]' NOT NULL,
+	`status_line` text,
+	`waiting_for` text,
+	`execution_mode` text DEFAULT 'worktree' NOT NULL,
+	`order` integer DEFAULT 0 NOT NULL,
+	`created_at` integer DEFAULT (unixepoch()) NOT NULL,
+	`updated_at` integer DEFAULT (unixepoch()) NOT NULL,
+	FOREIGN KEY (`status_id`) REFERENCES `issue_statuses`(`id`) ON UPDATE no action ON DELETE set null,
+	FOREIGN KEY (`milestone_id`) REFERENCES `issue_milestones`(`id`) ON UPDATE no action ON DELETE set null,
+	FOREIGN KEY (`parent_issue_id`) REFERENCES `issues`(`id`) ON UPDATE no action ON DELETE set null
+);
+--> statement-breakpoint
+CREATE INDEX `issues_workspace_id_idx` ON `issues` (`workspace_id`);--> statement-breakpoint
+CREATE UNIQUE INDEX `issues_workspace_number_unique` ON `issues` (`workspace_id`,`number`);--> statement-breakpoint
+CREATE INDEX `issues_status_id_idx` ON `issues` (`status_id`);--> statement-breakpoint
+CREATE INDEX `issues_milestone_id_idx` ON `issues` (`milestone_id`);--> statement-breakpoint
+CREATE INDEX `issues_parent_issue_id_idx` ON `issues` (`parent_issue_id`);--> statement-breakpoint
+CREATE INDEX `issues_delegate_agent_id_idx` ON `issues` (`delegate_agent_id`);--> statement-breakpoint
+CREATE INDEX `issues_delegate_provider_target_id_idx` ON `issues` (`delegate_provider_target_id`);--> statement-breakpoint
+CREATE TABLE `kanban_meta` (
+	`key` text PRIMARY KEY NOT NULL,
+	`revision` integer DEFAULT 0 NOT NULL,
+	`updated_at` integer DEFAULT (unixepoch()) NOT NULL
+);--> statement-breakpoint
+INSERT OR IGNORE INTO `kanban_meta` (`key`, `revision`) VALUES ('board', 0);--> statement-breakpoint
+INSERT OR IGNORE INTO `kanban_meta` (`key`, `revision`) VALUES ('schema_epoch', 1);

package/dist/drizzle-sqlite/0001_issue_pull_requests.sql

@@ -0,0 +1,15 @@
+CREATE TABLE `issue_pull_requests` (
+	`id` text PRIMARY KEY NOT NULL,
+	`issue_id` text NOT NULL,
+	`owner` text NOT NULL,
+	`repo` text NOT NULL,
+	`number` integer NOT NULL,
+	`url` text NOT NULL,
+	`created_by_kind` text NOT NULL,
+	`created_by_id` text,
+	`created_at` integer DEFAULT (unixepoch()) NOT NULL,
+	FOREIGN KEY (`issue_id`) REFERENCES `issues`(`id`) ON UPDATE no action ON DELETE cascade
+);
+--> statement-breakpoint
+CREATE UNIQUE INDEX `issue_pull_requests_issue_pr_unique` ON `issue_pull_requests` (`issue_id`,`owner`,`repo`,`number`);--> statement-breakpoint
+CREATE INDEX `issue_pull_requests_pr_idx` ON `issue_pull_requests` (`owner`,`repo`,`number`);

package/dist/drizzle-sqlite/0002_milestone_start_date.sql

@@ -0,0 +1 @@
+ALTER TABLE `issue_milestones` ADD `start_date` integer;

package/dist/drizzle-sqlite/0003_status_entry_rules.sql

@@ -0,0 +1 @@
+ALTER TABLE `issue_statuses` ADD `entry_rules` text;

package/dist/drizzle-sqlite/0004_run_external_session_ref.sql

@@ -0,0 +1 @@
+ALTER TABLE `issue_runs` ADD `external_session_ref` text;

package/dist/drizzle-sqlite/README.md

@@ -0,0 +1,67 @@
+<!-- Once this directory changes, update this README.md -->
+
+# Board migrations for a board file of this package's own
+
+The board schema for a SQLite file nobody but this package owns — the one a
+project keeps beside its code. It is one of the chains that build the same
+board (ruling 5-2):
+
+| Where the board lives | Who migrates it | With what |
+| --- | --- | --- |
+| a board file of a project's own | this package, through `migrateBoardFile` | **this folder** |
+| an external Postgres | `kanbo migrate` (`migrateBoardDatabase`) | `drizzle-postgres/` |
+| a host app's own database | the app, with its own migrations | the app's own chain |
+
+**A change to the board is a migration in every chain, written together** — at
+the same `BOARD_SCHEMA_EPOCH` — or a board stops being the same board when it
+moves. An app that keeps the board in its own database re-exports
+`kanbo/sqlite/schema` and generates its own migration from it. `src/postgres/schema.parity.test.ts` compares the two schemas the chains
+are generated from, so a column added on one side alone fails there rather than
+in somebody's database.
+
+Generated with `npm run generate:sqlite` from
+`src/sqlite/schema.ts`.
+
+## Files
+
+- **0000_board.sql**: the whole board at epoch 1 — eight tables, their indexes
+  and the foreign keys that point inside the board. There are no foreign keys
+  out of it: this file has no `workspaces`, `agents` or `provider_targets` to
+  point at (ruling 5-1). The two `INSERT OR IGNORE` statements at the end seed
+  `kanban_meta` with `board` revision `0` and `schema_epoch` `1` (the generation
+  `assertBoardSchema` demands). They are hand-written, because `drizzle-kit`
+  generates structure, not rows: regenerating this file drops them, and they
+  have to be put back.
+- **0001_issue_pull_requests.sql**: `issue_pull_requests`, the pull requests a
+  card names (ruling 4-1) — a plain `CREATE TABLE` with its foreign key onto
+  `issues` (cascade), the unique `(issue_id, owner, repo, number)` and the
+  `(owner, repo, number)` index. The epoch stays 1: a file still at 0000 carries
+  the right stamp and lacks the table, which `assertBoardSchema` reports as
+  `missingAddedTables` until `kanbo migrate` has been run on it.
+- **0002_milestone_start_date.sql**: `issue_milestones.start_date` (unix
+  seconds, nullable), the day a milestone read as a sprint begins (ruling
+  5x-3) — a plain `ADD COLUMN`. The epoch stays 1; a file still at 0001 reads as
+  `board_schema_outdated` (`missingColumns`) until `kanbo migrate` has run.
+- **0003_status_entry_rules.sql**: `issue_statuses.entry_rules` (text, a JSON
+  array of `ENTRY_RULES`, nullable), what a card must satisfy before an agent
+  may put it in the column (ruling 6-1) — a plain `ADD COLUMN`; `null` asks for
+  nothing. The epoch stays 1; a file still at 0002 reads as
+  `board_schema_outdated` (`missingColumns`) until `kanbo migrate` has run.
+- **0004_run_external_session_ref.sql**: `issue_runs.external_session_ref`
+  (text, nullable), where an external agent's own log of a run lives, once it
+  has said (ruling 7-1): `claude:<id>` (a Claude Code session id) or
+  `codex:<id>` (a Codex session id — the one in the rollout's `session_meta`); `null` while it never has — a plain
+  `ADD COLUMN`. The epoch stays 1; a file still at 0003 reads as
+  `board_schema_outdated` (`missingColumns`) until `kanbo migrate` has run.
+- **meta/**: the drizzle journal and schema snapshots. JSON only, or
+  `drizzle-kit generate` fails to parse the directory.
+
+Nothing here rebuilds a table, and nothing here ever should: `migrateBoardFile`
+is drizzle's own migrator, in one pass with foreign keys left as the caller set
+them. A rebuild would need a runner that turns foreign keys off around it, and
+the only reason to have one is other tables that point at the board — of which
+this file has none.
+
+A second migration takes a name of its own — the package script carries
+`--name board` for the first one — so it is
+`npx drizzle-kit generate --config drizzle.sqlite.config.ts --name <what it does>`.