kanban-lite 1.0.33 → 1.0.36

package/.vscode/mcp.json

@@ -0,0 +1,20 @@
+{
+  "servers": {
+    "playwriter": {
+      "type": "stdio",
+      "command": "npx",
+      "args": ["-y", "playwriter@latest"],
+      "env": {
+        "PLAYWRITER_AUTO_ENABLE": "1"
+      }
+    },
+    "kanban": {
+      "type": "stdio",
+      "command": "npm",
+      "args": ["run", "mcp"],
+      "env": {
+        "KANBAN_DIR": ".kanban"
+      }
+    }
+  }
+}

package/AGENTS.md

@@ -62,6 +62,7 @@ Never implement a feature directly in an interface layer without the SDK method
 - Cards (sqlite engine): `.kanban/kanban.db` (configurable via `sqlitePath` in `.kanban.json`)
 - Config: `.kanban.json` (boards, columns, display settings, label definitions)
 - Webhooks: `.kanban-webhooks.json`
+- Logs: `.kanban/boards/<boardId>/<status>/attachments/<cardId>.log` (auto-attached text file)
 
 ## Storage Engines
 
@@ -111,3 +112,18 @@ metadata:
 - `completedAt` is auto-managed when status changes to/from `done`
 - `modified` timestamp is auto-updated on any change
 - The standalone server uses synchronous `fs` operations; the SDK uses async `fs/promises`
+
+## Agent execution rules (cost control):
+
+1. Do NOT scan or summarize the entire repository.
+2. Only open and modify the specific file(s) listed in the task plan.
+3. Do NOT rewrite large files from scratch.
+4. Make minimal surgical edits only where required.
+5. Do NOT refactor unrelated code.
+6. Do NOT change formatting, imports, or structure unless strictly necessary.
+7. Do NOT add new dependencies.
+8. Do NOT generate placeholder code or duplicate existing logic.
+9. Keep reasoning concise and implementation focused.
+10. If a task can be implemented by editing constants or inserting small functions, do that instead of restructuring the file.
+
+Goal: complete the tasks with the smallest possible code changes and minimal token usage.

package/CHANGELOG.md

@@ -7,7 +7,16 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+### Changed
+- **Card actions**: `actions` field now accepts either an array of action keys (`string[]`) or an object mapping action keys to display titles (`Record<string, string>`). The "Run Action" dropdown shows the title when the object form is used; the action key is always what's sent to the webhook. Fully backward-compatible — existing array-form cards are unchanged.
+
 ### Added
+- **Card logs**: Append timestamped log entries to any card, stored as a `<cardId>.log` text file auto-added as an attachment. Each entry has timestamp (auto-generated), source label (defaults to `"default"`), markdown text, and optional structured data object (stored as compact JSON). Supports markdown formatting (bold, italic, emoji) in log text.
+- **SDK**: `listLogs(cardId, boardId?)`, `addLog(cardId, text, options?, boardId?)`, `clearLogs(cardId, boardId?)` methods on `KanbanSDK`
+- **REST API**: `GET /api/tasks/:id/logs`, `POST /api/tasks/:id/logs`, `DELETE /api/tasks/:id/logs`
+- **CLI**: `kl log list <id>`, `kl log add <id> --text <msg> [--source <src>] [--object <json>]`, `kl log clear <id>`
+- **MCP**: `list_logs`, `add_log`, `clear_logs` tools
+- **UI**: Logs tab in card editor with toolbar (clear, limit, order, source filter, show/hide toggles for timestamp/source/objects), YAML-rendered objects
 - **Attachments subfolder**: attachments for the markdown storage engine are now stored in an `attachments/` subdirectory inside each column folder (e.g. `.kanban/boards/default/backlog/attachments/`) instead of alongside the card `.md` files
 - **Browser-viewable attachments**: PDFs and other binary attachments now open with the OS/browser default viewer in the VS Code extension; the standalone server now serves PDF, JPEG, GIF, WebP, CSV, plain-text, and XML attachments with correct `Content-Type` headers so browsers render them inline in a new tab
 - **KanbanSDK.getAttachmentDir(cardId, boardId?)**: new public SDK method that returns the absolute path to the attachment directory for a card (delegates to the active storage engine)

package/README.md

@@ -65,6 +65,7 @@ kl add --title "My first task" --priority high
 - **Labels**: Tag cards with multiple labels
 - **Attachments**: Attach files to cards
 - **Comments**: Add discussion threads to cards (stored in the same markdown file)
+- **Logs**: Append timestamped log entries to cards (stored as `<cardId>.log` text file, supports markdown, optional source labels and structured data objects)
 - **Actions**: Attach named triggers to a card (e.g. `retry`, `deploy`, `notify`) and fire them from the UI, CLI, API, or MCP server — calls a configured webhook with the card's full context
 - **Auto-generated IDs**: Based on title and timestamp (e.g., `implement-dark-mode-2026-01-29`)
 - **Timestamps**: Created and modified dates tracked automatically
@@ -134,6 +135,13 @@ kl comment add implement-search --author alice \
 kl comment edit implement-search c1 --body "Updated"    # Edit a comment
 kl comment remove implement-search c1                   # Remove a comment
 
+# Logs
+kl log list implement-search                             # List log entries
+kl log add implement-search --text "Build passed"         # Add a log entry
+kl log add implement-search --text "Deployed" \
+  --source ci --object '{"version":"1.0"}'               # With source and data
+kl log clear implement-search                            # Clear all logs
+
 # Boards
 kl boards                                               # List boards
 kl boards add --id bugs --name "Bug Tracker"            # Create a board
@@ -291,6 +299,14 @@ Board-scoped equivalents are available at `/api/boards/:boardId/tasks/...`.
 | `PUT` | `/api/tasks/:id/comments/:commentId` | Update a comment (`{ content }`) |
 | `DELETE` | `/api/tasks/:id/comments/:commentId` | Delete a comment |
 
+#### Logs
+
+| Method | Endpoint | Description |
+|--------|----------|-------------|
+| `GET` | `/api/tasks/:id/logs` | List log entries on a card |
+| `POST` | `/api/tasks/:id/logs` | Add a log entry (`{ text, source?, object?, timestamp? }`) |
+| `DELETE` | `/api/tasks/:id/logs` | Clear all log entries |
+
 #### Attachments
 
 | Method | Endpoint | Description |
@@ -382,15 +398,17 @@ Actions let you attach named triggers to a card — things like `retry`, `deploy
 }
 ```
 
-2. **Add actions to a card** — as a list of simple strings stored in the card's frontmatter:
+2. **Add actions to a card** — either as an array of action keys, or an object mapping action keys to display titles:
 
 ```yaml
----
-id: "42-deploy-v2"
-status: "in-progress"
+# Array form — action key is used as the button label
 actions: ["retry", "rollback", "notify-slack"]
----
-# Deploy v2.0
+
+# Object form — keys are the action names sent to the webhook, values are the UI labels
+actions:
+  retry: "Retry deployment"
+  rollback: "Roll back to v1"
+  notify-slack: "Notify Slack"
 ```
 
 3. **Trigger an action** from any interface:
@@ -415,7 +433,7 @@ actions: ["retry", "rollback", "notify-slack"]
     "assignee": "alice",
     "labels": ["deploy"],
     "content": "# Deploy v2.0\n...",
-    "actions": ["retry", "rollback", "notify-slack"]
+    "actions": ["retry", "rollback", "notify-slack"]  // or {"retry": "Retry deployment", ...}
   }
 }
 ```
@@ -424,7 +442,7 @@ The webhook receives the full card object (same shape as the SDK `Card` type, mi
 
 ### Managing actions
 
-Actions are plain strings in the `actions` array of the card's YAML frontmatter. Edit them directly in the markdown file, or use any interface:
+Actions are stored in the `actions` field of the card's YAML frontmatter — either as a plain string array or as a key→title object. Edit them directly in the markdown file, or use any interface:
 
 ```bash
 # Add actions when creating a card
@@ -508,6 +526,9 @@ kanban-mcp --dir .kanban        # Via dedicated binary
 | `add_comment` | Add a comment to a card |
 | `update_comment` | Edit a comment's content |
 | `delete_comment` | Remove a comment from a card |
+| `list_logs` | List log entries on a card |
+| `add_log` | Add a log entry to a card |
+| `clear_logs` | Clear all log entries from a card |
 | `list_columns` | List all board columns |
 | `add_column` | Add a new column to the board |
 | `update_column` | Update a column's name or color |

package/SKILL.md

@@ -42,6 +42,9 @@ Use **MCP tools** when available (native LLM integration). Fall back to **CLI**
 | List attachments | `list_attachments` | `kl attach <id>` | via card object |
 | Add attachment | `add_attachment` | `kl attach add <id> <path>` | `POST /api/tasks/:id/attachments` |
 | Remove attachment | `remove_attachment` | `kl attach remove <id> <name>` | `DELETE /api/tasks/:id/attachments/:name` |
+| List logs | `list_logs` | `kl log list <id>` | `GET /api/tasks/:id/logs` |
+| Add log | `add_log` | `kl log add <id> --text "..."` | `POST /api/tasks/:id/logs` |
+| Clear logs | `clear_logs` | `kl log clear <id>` | `DELETE /api/tasks/:id/logs` |
 | Get settings | `get_settings` | `kl settings` | `GET /api/settings` |
 | Update settings | `update_settings` | `kl settings update` | `PUT /api/settings` |
 | List webhooks | `list_webhooks` | `kl webhooks` | `GET /api/webhooks` |