From 6bc16dd0b4c251f3573c0b91cd47936fdffefdfa Mon Sep 17 00:00:00 2001 From: Janne Lammi Date: Fri, 9 Oct 2026 20:57:30 +0300 Subject: [PATCH 1/2] sync(skills): mirror 7b354df2 and pin @pathmode/mcp-server@1.41.0 --- .mcp.json | 2 +- README.md | 2 +- skills/implement-intent/SKILL.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/.mcp.json b/.mcp.json index ed2cf36..1b3cfe3 100644 --- a/.mcp.json +++ b/.mcp.json @@ -2,7 +2,7 @@ "mcpServers": { "pathmode": { "command": "npx", - "args": ["-y", "@pathmode/mcp-server@1.40.0"], + "args": ["-y", "@pathmode/mcp-server@1.41.0"], "env": { "PATHMODE_API_KEY": "${user_config.api_key}" } diff --git a/README.md b/README.md index 98c8f34..6988afe 100644 --- a/README.md +++ b/README.md @@ -72,7 +72,7 @@ For workspace API access without a local intent, you can still create an API key ## What's bundled -**MCP server** — `@pathmode/mcp-server@1.40.0`, pinned so the plugin skills and server tool contract update together. Local mode with no key; cloud mode with one. +**MCP server** — `@pathmode/mcp-server@1.41.0`, pinned so the plugin skills and server tool contract update together. Local mode with no key; cloud mode with one. **Check the gate yourself** — `node scripts/readiness-suite.mjs` runs the pinned server's preflight over 192 labelled field fixtures and a set of whole `intent.md` documents, and prints where it disagrees. Read [CALIBRATION.md](CALIBRATION.md) first: the field score is a regression baseline, not an accuracy claim. diff --git a/skills/implement-intent/SKILL.md b/skills/implement-intent/SKILL.md index 5fa6704..917b59f 100644 --- a/skills/implement-intent/SKILL.md +++ b/skills/implement-intent/SKILL.md @@ -7,7 +7,7 @@ description: Implement the repository's active intent only after running its det If the repository has no `intent.md`, stop implementation and propose an intent for the user's actual request. Never substitute the workspace's most recent intent. Use `intent_save(localDraft: true)` with open `productChoices` for consequential behavior the request leaves undecided; each needs a recommendation, reason, alternative, trade-off, reopen trigger, and contingent claims. Do not copy those claims into required outcomes before a reviewer answers. In keyless mode, the person's explicit answer to each choice is recorded with `answer_product_choice`, which adds the accepted claims itself; never write a choice's state or claims by hand. If the installed server does not support this input, report the version limitation rather than claiming the choices were saved. -For team review of a new local draft, run `npx @pathmode/mcp-server@latest adopt` in the repository and relay its link and code for browser approval. Adoption carries the open choices and establishes repository ownership; an API key or a choice-bearing create does not. If adoption is unavailable, preserve the local draft and stop rather than create an unbound repository intent. After successful adoption, call `attach_original_request` with the verbatim request, then send the review link. If you can run a background command, start `npx @pathmode/mcp-server@latest watch-review` in the background and end the turn: it prints one line when the review needs you, and the line says what to do. Otherwise stop at not ready. A terminal answer is not another person's judgment or workspace authorization. In keyless mode retain the source request alongside the intent and report the open choices; do not invent a cloud handoff. +For team review of a new local draft, run `npx @pathmode/mcp-server@latest adopt` in the repository and relay its link and code for browser approval. Adoption carries the open choices and establishes repository ownership; an API key or a choice-bearing create does not. If adoption is unavailable, preserve the local draft and stop rather than create an unbound repository intent. After successful adoption, call `attach_original_request` with the verbatim request, then send the review link. If you can run a background command, start `npx @pathmode/mcp-server@latest watch-review` in the background, with `--build` if the person asked you to implement the change or `--no-build` if they asked only for a proposal, and end the turn: it prints one line when the review needs you, and the line says what to do. Restart it without either flag after applying answers. If the person changes their mind about building, for example "hold off", leave the listener running and run it once more with `--build --declare` or `--no-build --declare`: that records the change for this review and exits, and the running listener still reports their answers and verdict. After an authorization, build only once `get_agent_prompt` with `mode: execute` succeeds; if it refuses as not ready, show the person the blockers it names and do not implement. An authorization does not accept failed execution checks. Otherwise stop at not ready. A terminal answer is not another person's judgment or workspace authorization. In keyless mode retain the source request alongside the intent and report the open choices; do not invent a cloud handoff. Before applying a repository choice request, use `get_intent` to refresh the current body and read the request. Call `intent_save` using the request's original `changeRequestId` and `baseRepoBodyRevision`. Do not include new choice proposals or unrelated body edits in that apply. Unchanged sibling answers may apply sequentially; a changed target or parent needs renewed human review. Refused applies are not permission to bypass the request. A requested deferral still waits for application and remains a readiness blocker afterward. From d1e5ee7ecb87a83bb7c7233cf3934d5d55067ed0 Mon Sep 17 00:00:00 2001 From: Janne Lammi Date: Fri, 9 Oct 2026 20:57:45 +0300 Subject: [PATCH 2/2] release: 0.1.47, pin @pathmode/mcp-server@1.41.0 --- .claude-plugin/plugin.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.json index 37c3ef7..49cb706 100644 --- a/.claude-plugin/plugin.json +++ b/.claude-plugin/plugin.json @@ -1,7 +1,7 @@ { "name": "pathmode", "displayName": "Pathmode", - "version": "0.1.46", + "version": "0.1.47", "description": "Run a deterministic preflight on your intent before an agent builds: /preflight scores six calibrated gates and names the exact blockers, no model call, no key. Pathmode also interrogates the intent behind a request (compile-intent), writes it to intent.md in your repo, and checks the code that comes back against the outcomes and constraints you agreed to. Free: uses the models you already have access to in Claude Code. Connect a Pathmode workspace to sync intent and evidence across a team.", "author": { "name": "Pathmode",