lema-mcp 0.11.1 → 0.13.0

package/README.md

@@ -76,6 +76,12 @@ analytics over a graph you own.
 
 ## Install
 
+**One click — installs the no-account public demo** (React's recorded decisions, zero setup):
+
+[![Add lema to Cursor](https://cursor.com/deeplink/mcp-install-dark.svg)](https://cursor.com/en/install-mcp?name=lema&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsImxlbWEtbWNwQGxhdGVzdCJdLCJlbnYiOnsiTEVNQV9NQ1BfTU9ERSI6InB1YmxpYyIsIkxFTUFfUFVCTElDX1JFUE8iOiJyZWFjdC1yZmNzIn19)   [![Install lema in VS Code](https://img.shields.io/badge/VS_Code-Install_lema-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://vscode.dev/redirect?url=vscode%3Amcp%2Finstall%3F%257B%2522name%2522%253A%2522lema%2522%252C%2522command%2522%253A%2522npx%2522%252C%2522args%2522%253A%255B%2522-y%2522%252C%2522lema-mcp%2540latest%2522%255D%252C%2522env%2522%253A%257B%2522LEMA_MCP_MODE%2522%253A%2522public%2522%252C%2522LEMA_PUBLIC_REPO%2522%253A%2522react-rfcs%2522%257D%257D)
+
+The button drops you straight into React's public record — ask *"why did React rule out X?"* and get a cited answer, no account. To wire **your own repo** for capture, or point the demo at Kubernetes or Rust, use the per-client setup below.
+
 `npx` needs only Node — no Go toolchain, no account. Two commands cover both ways
 to use lema:
 
@@ -254,9 +260,7 @@ Your agent calls these over MCP.
 
 | Tool | What it does |
 |------|--------------|
-| **`check_approach`** ★ | Name an approach → a three-valued verdict: `ruled_out` (rejected, with the recorded **why**, cited), `settled` (it *is* the project's in-force recorded choice, the governing decision cited), or an honest `no_recorded_ruling`. Every verdict carries a pointer to where the docs cover the how. The Fusion tool. |
-| **`settled`** | **Deprecated — use `check_approach`** (whose `settled` verdict folds this in). Typed `state` (`settled` / `not_settled` / `unsure`) for a direction, plus each governing decision's ref and reasoning. `not_settled` means *not on the record*, **not approved**. |
-| **`why_decided`** | One cited answer to "why did React / Kubernetes / Rust decide X?", surfacing status and ruled-out alternatives — with a machine-readable abstain (`record_silent: true`) when silent. (`why_not_public` is a deprecated alias — use `check_approach`.) |
+| **`check_approach`** ★ | Name an approach → a three-valued verdict: `ruled_out` (rejected, with the recorded **why** synthesized and cited), `settled` (it *is* the project's in-force recorded choice, the governing decision cited), or an honest `no_recorded_ruling`. Every verdict carries a pointer to where the docs cover the how. The one public door — it folds in the cited "why was this decided?" answer (the former `why_decided`) and the `settled` check. |
 
 ### Your own repo
 
@@ -270,7 +274,7 @@ Your agent calls these over MCP.
 | **`ask`** | One cited, synthesized answer over your team's **hosted** decision graph (hosted mode). |
 
 In your own repo the full server registers the read + capture tools (and the public
-tools too); the `npx lema-mcp try` server runs the public subset only.
+`check_approach` too); the `npx lema-mcp try` server runs the public door only.
 
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "lema-mcp",
-  "version": "0.11.1",
+  "version": "0.13.0",
   "mcpName": "io.github.lemahq/lema-mcp",
   "description": "MCP server that gives your coding agent the recorded why behind decisions — and what was already ruled out — cited. Check React, Rust, and Kubernetes out of the box, or capture and enforce never-reopen on your own repo. Local, no account.",
   "bin": {
@@ -13,10 +13,10 @@
     "prepack": "cp ../../README.md ./README.md && cp ../../LICENSE ./LICENSE"
   },
   "optionalDependencies": {
-    "lema-mcp-darwin-arm64": "0.11.1",
-    "lema-mcp-darwin-x64": "0.11.1",
-    "lema-mcp-linux-x64": "0.11.1",
-    "lema-mcp-linux-arm64": "0.11.1"
+    "lema-mcp-darwin-arm64": "0.13.0",
+    "lema-mcp-darwin-x64": "0.13.0",
+    "lema-mcp-linux-x64": "0.13.0",
+    "lema-mcp-linux-arm64": "0.13.0"
   },
   "engines": {
     "node": ">=18"