choda-deck 0.1.1 → 0.2.3

package/package.json

@@ -1,16 +1,18 @@
 {
   "name": "choda-deck",
-  "version": "0.1.1",
+  "version": "0.2.3",
   "description": "MCP server providing SQLite-backed task/session/conversation orchestration for Claude Code.",
   "author": "Vu Ngo",
   "license": "MIT",
   "packageManager": "pnpm@10.33.0",
   "bin": {
-    "choda-deck": "dist/mcp-server.cjs"
+    "choda-deck": "dist/cli.cjs",
+    "mcp-server": "dist/mcp-server.cjs"
   },
   "files": [
+    "dist/cli.cjs",
     "dist/mcp-server.cjs",
-    "dist/session-rules.md",
+    "dist/mcp-rules.md",
     "README.md",
     "LICENSE"
   ],
@@ -39,11 +41,14 @@
     "test": "node scripts/test.mjs run",
     "test:watch": "node scripts/test.mjs",
     "typecheck": "tsc --noEmit -p tsconfig.node.json --composite false",
-    "build:mcp": "esbuild src/adapters/mcp/server.ts --bundle --platform=node --target=node20 --format=cjs --outfile=dist/mcp-server.cjs --external:better-sqlite3 --external:sqlite-vec --external:@huggingface/transformers --external:onnxruntime-node --external:onnxruntime-web --external:sharp && node -e \"require('fs').copyFileSync('src/adapters/mcp/rules/session-rules.md','dist/session-rules.md')\""
+    "build:mcp": "esbuild src/adapters/mcp/server.ts --bundle --platform=node --target=node20 --format=cjs --outfile=dist/mcp-server.cjs --external:better-sqlite3 --external:sqlite-vec --external:@huggingface/transformers --external:onnxruntime-node --external:onnxruntime-web --external:sharp && node -e \"require('fs').copyFileSync('src/adapters/mcp/rules/mcp-rules.md','dist/mcp-rules.md')\"",
+    "build:cli": "esbuild src/adapters/cli/index.ts --bundle --platform=node --target=node20 --format=cjs --outfile=dist/cli.cjs --external:better-sqlite3 --external:sqlite-vec --external:@huggingface/transformers --external:onnxruntime-node --external:onnxruntime-web --external:sharp",
+    "build": "pnpm run build:mcp && pnpm run build:cli"
   },
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.29.0",
     "better-sqlite3": "^12.9.0",
+    "pg": "^8.21.0",
     "sqlite-vec": "^0.1.9"
   },
   "optionalDependencies": {
@@ -52,8 +57,10 @@
     "sharp": "^0.34.5"
   },
   "devDependencies": {
+    "@testcontainers/postgresql": "^12.0.0",
     "@types/better-sqlite3": "^7.6.13",
     "@types/node": "^22.19.1",
+    "@types/pg": "^8.20.0",
     "esbuild": "^0.27.0",
     "eslint": "^9.39.1",
     "eslint-config-prettier": "^9.1.0",

package/dist/session-rules.md

@@ -1,83 +0,0 @@
-# Session Rules
-
-Behavioral contract for session lifecycle tools. Edit this file to update compliance rules — no MCP restart needed.
-
-## On session_start
-
-`session_start` now requires a `taskId` — the task is bound to the session at creation and auto-set to IN-PROGRESS.
-
-Before calling `session_start`:
-
-1. Call `task_list` (or `roadmap`) to show the user available tasks, grouped by priority (high → medium → low).
-2. Wait for the user to pick a task. Do not guess.
-3. Call `session_start({ projectId, taskId, workspaceId?, cwd? })`. Always pass `cwd` (current shell directory) so the MCP can auto-detect `workspaceId` for projects with registered workspaces — the MCP server's own cwd is fixed and cannot be inferred.
-4. Echo the `lastSession` block to the user verbatim — resume point, decisions, loose ends, tasks updated, commits. Do not summarize.
-5. Create a feature branch for the task:
-   - Branch name: `feat/<task-id>-<short-slug>` (e.g. `feat/task-564-session-conv-ui`)
-   - Required: `git checkout -b feat/<task-id>-<short-slug>`
-   - Optional (if user wants parallel worktree): detect repo root via `git rev-parse --show-toplevel`, then `git worktree add <repo-root>.worktrees/<slug> -b feat/<task-id>-<short-slug>`
-   - Ask the user whether they want a worktree or just a branch before proceeding.
-
-Workspace resolution order (when project has ≥1 workspace registered):
-- explicit `workspaceId` wins
-- else `cwd` is matched against registered workspace cwds (longest prefix wins for nested repos)
-- else MCP throws — pick a workspace explicitly or call `workspace_add`
-
-If the project has no workspaces registered, `workspaceId` may be `null` (backward-compatible).
-
-Blocking conditions (MCP returns an error):
-- Task not found
-- Task already `DONE` — reopen it with `task_update` first
-- Task already bound to another active session — end that session first
-- Project has workspaces but neither `workspaceId` nor a matching `cwd` was provided
-
-## On session_checkpoint
-
-`session_checkpoint` snapshots progress on an active session **without ending it**. Overwrite-in-place — each call replaces the previous checkpoint.
-
-When to checkpoint:
-
-- Before risky operations (rebase, force-push, schema migration, large refactor)
-- Before context window compaction (when conversation grows long)
-- Every ~30 minutes of active work, or after a meaningful sub-step
-- When pausing work mid-task (lunch, meeting) — so a future `session_resume` recovers state cleanly
-
-Required field:
-
-- **resumePoint** — one sentence describing exactly where you stopped and what to pick up next
-
-Recommended fields (include whichever apply):
-
-- **lastConversationId** — most recent conversation touched (resume context)
-- **dirtyFiles** — files edited but not yet committed (so resume knows what's in flight)
-- **lastCommit** — last commit SHA written this session (resume git position)
-- **notes** — free-form context that matters for resume (decisions made, dead ends ruled out)
-
-Do not call `session_checkpoint` as a substitute for `session_end`. Checkpoint = pause; end = finalize + handoff.
-
-## On session_resume
-
-`session_resume` returns the session row, last checkpoint, linked conversations, and active context sources. Use after crash, restart, or context compaction — not as a way to spawn a new session for the same task.
-
-After calling `session_resume`:
-
-1. **Echo the checkpoint summary verbatim** — `resumePoint`, `notes`, `dirtyFiles`, `lastCommit`, `lastConversationId`. Do not summarize. Butter needs the same view the prior session had.
-2. **Confirm task binding** — name the `taskId` and current status. If the task is no longer IN-PROGRESS, surface the discrepancy before proceeding.
-3. **Resume from `resumePoint`** — pick up the exact next step. Do not re-plan from scratch.
-4. **Do not call `session_start`** — resume reactivates the existing session; starting a new one orphans the checkpoint and creates duplicate state.
-
-If no checkpoint exists (resumed session was never checkpointed), say so explicitly and ask Butter where to pick up before continuing.
-
-## On session_end
-
-When preparing the session_end payload, always include:
-
-- **resumePoint** (required) — one sentence describing where you stopped and what the next session should pick up.
-- **tasksUpdated** (required if session had a taskId) — list of task ids and their new status.
-- **decisions** — architectural or implementation decisions made this session. Explicit > implicit.
-- **looseEnds** — anything unfinished, deferred, or noted for later. Include pre-existing issues you touched but did not resolve.
-- **commits** — commit SHAs + short message if commits were made.
-
-Never end a session with only resumePoint. If the session was trivial (read-only), explicitly note "no changes" in looseEnds.
-
-`looseEnds` are auto-converted to inbox entries (status=raw) under the session's project — one entry per item, tagged with the source session/task ID. Butter reviews the inbox in `/daily` and decides which deserve to become TODO tasks via `inbox_convert`. Keep each loose end short (1 line, concrete) — they are capture, not specification.