@work-graph/cli 0.2.7 → 0.2.8

package/README.md

@@ -8,7 +8,7 @@ Use it when you want:
 
 - a project-local backlog without SaaS lock-in;
 - BVC work contracts that can be reviewed in Git;
-- Cursor MCP configuration generated for the project;
+- optional MCP client configuration for the project (Cursor by default);
 - a local UI for task status, evidence and project navigation;
 - repeatable setup through `npx`, not a copied engine repository.
 
@@ -45,8 +45,8 @@ Typical output:
 | `.work-graph/config.json` | Project id, label and UI settings |
 | `intent/` | BVC intent tree for work items |
 | `intent/index.bvc` | Index of work item files |
-| `.cursor/mcp.json` | Cursor MCP server entry for Work Graph |
-| `.cursor/rules/work-graph-project.mdc` | Project rule that tells agents to use Work Graph |
+| `.cursor/mcp.json` | Optional: MCP server entry when using Cursor |
+| `.cursor/rules/work-graph-project.mdc` | Optional: project rule for agents in Cursor |
 | `package.json` | `workgraph:*` scripts and devDependencies |
 
 After `npm install`, the project owns its Work Graph runtime through `node_modules/@work-graph/cli` and `node_modules/@work-graph/mcp`.
@@ -55,7 +55,7 @@ After `npm install`, the project owns its Work Graph runtime through `node_modul
 
 | Command | Description |
 |---------|-------------|
-| `init [path]` | Scaffold Work Graph into a project: BVC intent tree, config, npm scripts, MCP config and Cursor rule |
+| `init [path]` | Scaffold Work Graph into a project: BVC intent tree, config, npm scripts, optional MCP/rule files |
 | `ui [path]` | Start the local backlog UI for the project |
 | `doctor [path]` | Verify that project config, package dependencies and runtime resolution are healthy |
 | `register [path]` | Optional: register a project in the shared multiproject host |
@@ -116,7 +116,7 @@ The CLI installs the runtime and UI. The BVC format itself is published separate
 | Symptom | Fix |
 |---|---|
 | `work-graph doctor` says dependencies are missing | Run `npm install` in the target project |
-| Cursor does not see Work Graph MCP tools | Re-run `npx @work-graph/cli init .` without `--no-mcp`, then reload Cursor MCP servers |
+| Agent does not see Work Graph MCP tools | Re-run `npx @work-graph/cli init .` without `--no-mcp`, then reload MCP servers in your IDE |
 | UI port is already in use | Run `npx @work-graph/cli ui . --port 4178` |
 | Existing package scripts were not updated | Re-run without `--no-package` or add the `workgraph:*` scripts manually |
 | You are hacking Work Graph itself | Use `WORKGRAPH_ENGINE_ROOT=.` or `--engine` from the monorepo, not in normal projects |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@work-graph/cli",
-  "version": "0.2.7",
+  "version": "0.2.8",
   "description": "Work Graph CLI — install local agent work tracking, BVC work items and backlog UI in any project",
   "type": "module",
   "bin": {

package/vendor/packages/workgraph-mcp/README.md

@@ -2,9 +2,11 @@
 
 [MCP](https://modelcontextprotocol.io) server for Work Graph — list, create, and update work items in `intent/**/*.work.bvc`.
 
-## Cursor
+Works with any MCP-capable agent client (Cursor, Claude Desktop, Claude Code, and others).
 
-After `npx @work-graph/cli init .`, `.cursor/mcp.json` includes:
+## After `work-graph init`
+
+`npx @work-graph/cli init .` writes `.cursor/mcp.json` when you use Cursor. The entry looks like:
 
 ```json
 {
@@ -21,7 +23,7 @@ After `npx @work-graph/cli init .`, `.cursor/mcp.json` includes:
 }
 ```
 
-Reload MCP in Cursor after init.
+Reload MCP in your IDE after init. For Claude Desktop / Claude Code and other clients, use the same command and env — see [workgraph-mcp-clients.md](https://github.com/bvc-lang/work-graph/blob/main/docs/workgraph-mcp-clients.md) in the monorepo.
 
 ## Standalone
 

package/vendor/packages/workgraph-mcp/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@work-graph/mcp",
-  "version": "0.2.4",
+  "version": "0.2.5",
   "description": "MCP server for Work Graph — work items in intent/**/*.work.bvc",
   "type": "module",
   "bin": {
@@ -16,7 +16,7 @@
     "access": "public"
   },
   "dependencies": {
-    "@work-graph/cli": "^0.2.4",
+    "@work-graph/cli": "^0.2.8",
     "@modelcontextprotocol/sdk": "^1.29.0",
     "zod": "^3.25.76"
   },

package/vendor/packages/workgraph-mcp/src/index.mjs

@@ -340,10 +340,10 @@ server.tool(
 
 server.tool(
   'record_work_item_analysis',
-  'Write pre-execution feasibility analysis into WorkItem «Анализ» (стоит ли делать; not post-factum review). Text must come from Cursor LLM — server does not call models.',
+  'Write pre-execution feasibility analysis into WorkItem «Анализ» (стоит ли делать; not post-factum review). Text must come from the connected agent LLM — server does not call models.',
   {
     workId: z.string().describe('WorkItem id'),
-    analysis: z.string().describe('Full analysis text produced in Cursor'),
+    analysis: z.string().describe('Full analysis text produced by the connected agent'),
   },
   async (args) => jsonText(await recordWorkItemAnalysisFromMcp(args, rootOptions())),
 );

package/vendor/packages/workgraph-mcp/src/prompts.mjs

@@ -8,7 +8,7 @@ const TOOL_RULES = [
   'New WorkItem prose (Базис/Вектор/Цель/Проверки/title): Russian, min lengths per work-item-bvc-quality; forbidden jargon: closing analysis, Canon:, evidence, upstream, Track A, feeds_epics, depends_on=, «Стоит завести «…» в бэклог».',
   'Analysis is pre-execution only: feasibility (стоит ли делать), scope, deps, risks, alternatives — NOT a post-factum report of what was built, tests run, or evidence already in the atom.',
   'Write analysis in present/decision tense («Стоит брать», «Не стоит», «Можно стартовать»), never past retrospective («было оправдано», «можно было») even if work.status is done.',
-  'Analysis and decision are written only from Cursor: you (connected LLM) read the task, reason, then call record_work_item_analysis / record_work_item_decision. WorkGraph server never calls LLM.',
+  'Analysis and decision are written only from the connected agent (MCP client LLM): you read the task, reason, then call record_work_item_analysis / record_work_item_decision. WorkGraph server never calls LLM.',
   'Do not mark a WorkItem done without concrete evidence.',
   'Keep dashboard/kanban work in WorkGraph UI; MCP is the agent client bridge.',
 ].join('\n');
@@ -26,7 +26,7 @@ export const workgraphPrompts = {
   analyze_work_item: {
     description: 'Pre-execution feasibility analysis for a WorkItem (not post-factum review).',
     argsSchema: { workId: 'WorkItem id to analyze' },
-    text: ({ workId }) => `Analyze WorkGraph item ${workId || '<workId>'} in Cursor — **before execution**.
+    text: ({ workId }) => `Analyze WorkGraph item ${workId || '<workId>'} — **before execution** (pre-execution feasibility, not a post-mortem).
 
 This is a feasibility review (стоит ли делать), NOT a summary of work already done. Do NOT list implemented files, passing tests, or evidence from «Свидетельства» unless you judge future verification risk.
 

package/vendor/src/publicSiteServer.mjs

@@ -219,12 +219,12 @@ function renderRelatedTemplates(locale, theme) {
     ? [
       ['Контракт задачи', 'BVC-атом с Базисом, Вектором, Целью и проверками.', '/docs/bvc-spec'],
       ['Матрица проверок', 'Tier A/B/C readiness для работы агентов.', '/docs/verification-matrix'],
-      ['MCP-инструменты', 'Контракты tools для Cursor и Claude Code.', '/docs/mcp-tools'],
+      ['MCP-инструменты', 'Контракты tools для MCP-клиентов (Cursor, Claude Code, …).', '/docs/mcp-tools'],
     ]
     : [
       ['Work contract', 'BVC atom with Basis, Vector, Goal and checks.', '/docs/bvc-spec'],
       ['Verification matrix', 'Tier A/B/C readiness for agent work.', '/docs/verification-matrix'],
-      ['MCP tools', 'Tool contracts for Cursor and Claude Code.', '/docs/mcp-tools'],
+      ['MCP tools', 'Tool contracts for MCP clients (Cursor, Claude Code, …).', '/docs/mcp-tools'],
     ];
   return `<section class="related-templates">
     <div class="related-inner">
@@ -390,7 +390,7 @@ function renderInstallInstructions(locale) {
     <div>
       <p class="eyebrow">${escapeHtml(locale === 'ru' ? 'Установка' : 'Installation')}</p>
       <h2>${escapeHtml(locale === 'ru' ? 'Как установить Work Graph' : 'How to install Work Graph')}</h2>
-      <p>${escapeHtml(locale === 'ru' ? 'Быстрый путь — подключить Work Graph как MCP-сервер к Cursor или Claude Code. Данные остаются локально в git, сайт собирается в dist/public-site без базы данных.' : 'The fastest path is to connect Work Graph as an MCP server to Cursor or Claude Code. Data stays local in git, and the site exports to dist/public-site without a database.')}</p>
+      <p>${escapeHtml(locale === 'ru' ? 'Быстрый путь — подключить Work Graph как MCP-сервер к вашему агенту (Cursor, Claude Code или другой MCP-клиент). Данные остаются локально в git.' : 'The fastest path is to connect Work Graph as an MCP server to your agent IDE (Cursor, Claude Code, or another MCP client). Data stays local in git.')}</p>
     </div>
     <ol>${steps.map(([title, command]) => `<li>
       <strong>${escapeHtml(title)}</strong>

package/vendor/src/workGraphProjectInit.mjs

@@ -20,8 +20,8 @@ export {
 
 const CONFIG_SCHEMA_V1 = 'workgraph.project.config.v1';
 const CONFIG_SCHEMA_V2 = 'workgraph.project.config.v2';
-const DEFAULT_CLI_VERSION = '0.2.3';
-const DEFAULT_MCP_VERSION = '0.2.3';
+const DEFAULT_CLI_VERSION = '0.2.8';
+const DEFAULT_MCP_VERSION = '0.2.5';
 
 const INDEX_STUB = `#Index<[
 WorkItems:
@@ -322,12 +322,12 @@ export async function initWorkGraphProject(options = {}) {
       'npm install',
       'npm run workgraph:ui',
       'Открыть http://127.0.0.1:4177/',
-      'Перезагрузить MCP в Cursor (workgraph)',
+      'Перезагрузить MCP в IDE (сервер workgraph)',
     ]
     : [
       'npm run workgraph:ui',
       'Открыть http://127.0.0.1:4177/',
-      'Перезагрузить MCP в Cursor (workgraph)',
+      'Перезагрузить MCP в IDE (сервер workgraph)',
     ];
 
   return {