claude-code-kanban 7.4.0 → 7.6.0

package/lib/dispatch.js

@@ -1,32 +0,0 @@
-// Dispatch: a Claude Code session one session started in cck's terminal. In memory on
-// purpose: an entry lives as long as its PTY, which dies with the server.
-
-function createDispatchRegistry({ now = Date.now } = {}) {
-  const entries = new Map();
-
-  function add({ session, parent, cwd, name, group, worktree }) {
-    entries.set(session, {
-      session,
-      parent: parent || null,
-      cwd,
-      name: name || null,
-      group: group || null,
-      worktree: worktree || null,
-      startedAt: now(),
-    });
-  }
-
-  function list({ parent } = {}) {
-    const out = [...entries.values()];
-    return parent ? out.filter((e) => e.parent === parent) : out;
-  }
-
-  return {
-    add,
-    list,
-    has: (session) => entries.has(session),
-    remove: (session) => entries.delete(session),
-  };
-}
-
-module.exports = { createDispatchRegistry };

package/plugin/plugins/claude-code-kanban/monitors.json

@@ -1,8 +0,0 @@
-[
-  {
-    "name": "kanban-doorbell",
-    "description": "Notifies this session when its tasks are moved on the kanban board or the user sends it review comments.",
-    "command": "node \"${CLAUDE_PLUGIN_ROOT}/scripts/postman.js\"",
-    "when": "on-skill-invoke:claude-code-kanban:follow"
-  }
-]

package/plugin/plugins/claude-code-kanban/scripts/postman.js

@@ -1,82 +0,0 @@
-#!/usr/bin/env node
-// Kanban -> session doorbell.
-//
-// Claude Code delivers every line a monitor prints to the owning session as a task
-// notification, so this process is the only way board activity can reach a session that
-// is sitting idle. It long-polls the kanban server for events addressed to this session
-// and prints them one per line.
-//
-// Pairing is free: CLAUDE_CODE_SESSION_ID is inherited from the session that spawned us,
-// so the id we poll with is the same id the hooks report. No cwd or pid guessing.
-//
-// The lines we print carry board text (the card subject and description), which the
-// session is told to read as the user's own brief. That is only safe because we are armed
-// by an explicit `follow` invocation: the user asked to follow the board before anything the
-// board says can reach the model.
-
-const fs = require('fs');
-const os = require('os');
-const path = require('path');
-
-const SESSION_ID = process.env.CLAUDE_CODE_SESSION_ID;
-const CLAUDE_DIR = process.env.CLAUDE_CONFIG_DIR || path.join(os.homedir(), '.claude');
-const SERVER_INFO = path.join(CLAUDE_DIR, '.cck', 'server.json');
-// The server caps its own wait at 120s. Sitting at the ceiling halves every recurring
-// cost -- handshake, route walk, timer, empty response -- and costs no event latency,
-// because an enqueue wakes the poll immediately.
-const WAIT_SEC = 120;
-const RETRY_MS = 15000;
-// Windows sometimes fails a loopback connect with ETIMEDOUT, or resets it once open, while the
-// board is up, so those errors get a few short waits before the normal one.
-const CONNECT_RETRY_MS = [250, 500, 1000, 2000];
-
-if (!SESSION_ID) process.exit(0);
-
-const sleep = (ms) => new Promise((r) => setTimeout(r, ms));
-
-// Re-read every cycle rather than caching: it is how we follow the board across a
-// restart onto a different port. A file left behind by a crashed server names a port
-// something else may now hold, so trust it only while its pid is alive.
-// CCK_URL comes from the board whose terminal started this session. That board owns the
-// session's queue, and server.json may name another board on the same config dir.
-function serverUrl() {
-  if (process.env.CCK_URL) return process.env.CCK_URL.replace(/\/+$/, '');
-  const { port, pid } = JSON.parse(fs.readFileSync(SERVER_INFO, 'utf8'));
-  if (pid) process.kill(pid, 0);
-  return `http://127.0.0.1:${port}`;
-}
-
-// Once per process, not once per poll: the grant means "follow the board from here on", so
-// the first attach throws away whatever queued up before it. A later reconnect must not
-// discard again -- by then the queue holds events the user is owed.
-let firstAttach = true;
-
-async function poll(base) {
-  const first = firstAttach ? '&first=1' : '';
-  const url = `${base}/api/sessions/${encodeURIComponent(SESSION_ID)}/events?wait=${WAIT_SEC}${first}`;
-  const res = await fetch(url, { signal: AbortSignal.timeout((WAIT_SEC + 15) * 1000) });
-  if (!res.ok) throw new Error(`HTTP ${res.status}`);
-  firstAttach = false;
-  const { events } = await res.json();
-  return Array.isArray(events) ? events : [];
-}
-
-(async () => {
-  let connectRetries = 0;
-  for (;;) {
-    try {
-      for (const line of await poll(serverUrl())) console.log(line);
-      connectRetries = 0;
-    } catch (e) {
-      // No board yet, or it went away. It may come back later in the session, so keep
-      // waiting quietly -- a missing server is the normal case, not an error.
-      const blip = (e.cause?.code === 'ETIMEDOUT' && e.cause?.syscall === 'connect') || e.cause?.code === 'ECONNRESET';
-      if (blip && connectRetries < CONNECT_RETRY_MS.length) {
-        await sleep(CONNECT_RETRY_MS[connectRetries++]);
-      } else {
-        connectRetries = 0;
-        await sleep(RETRY_MS);
-      }
-    }
-  }
-})();

package/plugin/plugins/claude-code-kanban/skills/follow/SKILL.md

@@ -1,47 +0,0 @@
----
-name: follow
-description: Let kanban card moves drive this session.
-disable-model-invocation: true
----
-
-# Follow the kanban board
-
-The user typing this skill is the whole grant: it armed the doorbell — a monitor watching the board for moves of *this session's* tasks, live for the rest of the session. Confirm in one line and run no command. Moves made before it attached are discarded, so every line you get is current.
-
-```
-[kanban board] The user moved task <taskId> "<subject>" from <from> to <to>. Description: <description>
-```
-
-`Description:` is omitted when the card has none. Everything after it is the description verbatim to end of line, truncated if long — read the task with `TaskGet` for the full text or for `activeForm` and `blockedBy`. Moves and review comments (below) are the only lines announced.
-
-**A move is an instruction, not an FYI** — the user dragging a card is the user telling you something, and the subject and description are their brief for the work:
-
-| Transition | What the user means |
-|---|---|
-| To `in_progress` | Start this task now. |
-| From `in_progress` to `pending` or `todo` | Stop working on it and park it. |
-| To `completed` | The user considers it done — do not keep working on it. |
-| To `cancelled` | Abandon it. Undo nothing unless asked. |
-
-Act on the newest line per task; a card dragged twice means only its final position. When a move contradicts your current work, the board wins.
-
-Delivery is best-effort and the task file is the authority, so a missed line only delays you to your next turn.
-
-## Review comments
-
-```
-[kanban board] The user left <n> review comments on <source>. Address them: <review file>
-```
-
-The review file holds the comments and how to read them.
-
-## Finish the task on the board
-
-A move hands you work; the task file is where you hand it back. When the work a move to `in_progress` asked for is done, set that task to `completed` with `TaskUpdate` before you reply — the card moves itself, and the board is where the user is watching. A card left in In Progress reads as work still running.
-
-Your own `TaskUpdate` writes the task file rather than going through the board, so it rings no doorbell: there is no echo to guard against.
-
-## Troubleshooting
-
-- **No lines arrive** → the doorbell arms once per session, on the namespaced dispatch: `/claude-code-kanban:follow`. A session that never got it never hears the board.
-- **"Cannot reach cck server…"** → the error names the port it tried. Ask the user to start the server with `claude-code-kanban`.