@kanera/cli 1.5.0 → 1.5.1

package/README.md

@@ -10,6 +10,12 @@ Requires Node 22 or newer. The package has no dependencies.
 npm install --global @kanera/cli
 ```
 
+An agent can inspect the complete command surface without installing anything globally:
+
+```bash
+npx -y @kanera/cli commands
+```
+
 ## Authenticate
 
 You need a Kanera API key. Create one in the Kanera web app under **Settings → API keys**
@@ -130,3 +136,7 @@ kanera mcp              # serve the same tools over stdio MCP, using the stored
 
 `kanera mcp` means a user who has already run `kanera auth login` does not configure a second
 credential in a second place to use Kanera from an MCP client.
+
+When connected Kanera MCP tools are already available, prefer them over the CLI. The CLI is the
+fallback for shell-only agents; both transports should be used instead of browser automation for
+supported card and project operations.

package/dist/kanera.mjs

@@ -37651,7 +37651,7 @@ var init_package = __esm({
   "../mcp/package.json"() {
     package_default = {
       name: "@kanera/mcp",
-      version: "2.2.0",
+      version: "2.2.1",
       private: true,
       type: "module",
       exports: {
@@ -63895,7 +63895,7 @@ function createKaneraMcpServer(ctx) {
       // custom MCP clients connect directly to /mcp and never discover server.json.
       icons: serverIcons
     },
-    { instructions: `For cross-board reporting, first resolve people with kanera_list_workspace_members, then use kanera_query_work_cards for active or completed assignments and kanera_query_work_history for one person's actions in a date range. Use kanera_get_cards_content for selected evidence and kanera_get_card or kanera_list_card_history only when deeper detail is needed. kanera_search returns one bounded, typed result stream with canonical links. Kanera MCP is work-focused: it reads configuration needed to resolve boards, lists, labels, fields, options, members, and permissions; workspace admins can manage automations with the dedicated automation tools, while other workspace/board/list/field/label administration remains in the Kanera UI. Standard-workspace lists, fields, labels, membership, and automations are shared across its boards; standalone boards have dedicated configuration. Card reference fields accept a UUID, human key such as PROJ-123, or canonical card URL. Use kanera_list_accessible_boards for complete discovery including standalone and guest boards, kanera_get_board for metadata/configuration, and kanera_get_cards_list for bounded list pages. Use kanera_get_portfolio_summary for portfolio rollups. Use the priority tools (kanera_list_priorities, kanera_add_priority, kanera_move_priority, kanera_remove_priority) to read and curate a user's ranked cross-board "Up next" queue; kanera_list_priority_targets shows whose queues a manager can reach. Use kanera_search_docs for product guidance and kanera_search for live user data. Personal notes are private to their owner. Read-only credentials cannot mutate. Board, workspace, list, field, label, note, and note-attachment deletion or administration not represented by a tool must be completed manually in the Kanera UI.` }
+    { instructions: `Use Kanera MCP tools instead of browser automation for every supported read or write; reserve the web interface for explicitly visual tasks and UI-only administration. For an exact human card key or canonical card URL, call kanera_get_card directly before a mutation and reserve kanera_search for names, phrases, and other ambiguous text. For cross-board reporting, first resolve people with kanera_list_workspace_members, then use kanera_query_work_cards for active or completed assignments and kanera_query_work_history for one person's actions in a date range. Use kanera_get_cards_content for selected evidence and kanera_get_card or kanera_list_card_history only when deeper detail is needed. kanera_search returns one bounded, typed result stream with canonical links. Kanera MCP is work-focused: it reads configuration needed to resolve boards, lists, labels, fields, options, members, and permissions; workspace admins can manage automations with the dedicated automation tools, while other workspace/board/list/field/label administration remains in the Kanera UI. Standard-workspace lists, fields, labels, membership, and automations are shared across its boards; standalone boards have dedicated configuration. Card reference fields accept a UUID, human key such as PROJ-123, or canonical card URL. Use kanera_list_accessible_boards for complete discovery including standalone and guest boards, kanera_get_board for metadata/configuration, and kanera_get_cards_list for bounded list pages. Use kanera_get_portfolio_summary for portfolio rollups. Use the priority tools (kanera_list_priorities, kanera_add_priority, kanera_move_priority, kanera_remove_priority) to read and curate a user's ranked cross-board "Up next" queue; kanera_list_priority_targets shows whose queues a manager can reach. Use kanera_search_docs for product guidance and kanera_search for live user data. Personal notes are private to their owner. Read-only credentials cannot mutate. Board, workspace, list, field, label, note, and note-attachment deletion or administration not represented by a tool must be completed manually in the Kanera UI.` }
   );
   registerTools(server, ctx);
   registerResources(server, ctx);
@@ -65251,7 +65251,7 @@ var init_doctor = __esm({
 function skillDocument() {
   return `---
 name: kanera
-description: Read and manage Kanera work \u2014 boards, cards, comments, notes, and priority queues \u2014 from the shell with the kanera CLI. Use when the user mentions Kanera, a card key like MKT-42, a board, or their "Up next" queue.
+description: Read and manage Kanera work from the shell with the kanera CLI. Use when MCP tools are unavailable and the user mentions Kanera, a human card key such as DEV-938, a board, or an "Up next" queue.
 ---
 
 # Kanera
@@ -65259,6 +65259,10 @@ description: Read and manage Kanera work \u2014 boards, cards, comments, notes,
 The \`kanera\` CLI talks to Kanera's public API. Every command accepts \`--json\` for a structured
 envelope and \`--quiet\` for the bare result, which is what you should use when parsing output.
 
+Use this shell transport instead of browser automation for supported Kanera work. Open the Kanera
+web interface only for an explicitly visual task or an administration operation the CLI does not
+expose. When connected Kanera MCP tools are available, prefer those tools over this CLI.
+
 ## Before anything else
 
 \`\`\`bash
@@ -65822,7 +65826,7 @@ var init_cli = __esm({
     init_output();
     init_skill();
     init_tools();
-    cliVersion = false ? process.env.npm_package_version ?? "0.0.0-dev" : "1.5.0";
+    cliVersion = false ? process.env.npm_package_version ?? "0.0.0-dev" : "1.5.1";
     USAGE = `kanera \u2014 manage Kanera work from the terminal or an AI agent
 
 Usage: