lema-mcp 0.11.0 → 0.12.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +2 -4
  2. package/package.json +5 -5
package/README.md CHANGED
@@ -254,9 +254,7 @@ Your agent calls these over MCP.
254
254
 
255
255
  | Tool | What it does |
256
256
  |------|--------------|
257
- | **`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. |
258
- | **`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**. |
259
- | **`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`.) |
257
+ | **`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. |
260
258
 
261
259
  ### Your own repo
262
260
 
@@ -270,7 +268,7 @@ Your agent calls these over MCP.
270
268
  | **`ask`** | One cited, synthesized answer over your team's **hosted** decision graph (hosted mode). |
271
269
 
272
270
  In your own repo the full server registers the read + capture tools (and the public
273
- tools too); the `npx lema-mcp try` server runs the public subset only.
271
+ `check_approach` too); the `npx lema-mcp try` server runs the public door only.
274
272
 
275
273
  ---
276
274
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lema-mcp",
3
- "version": "0.11.0",
3
+ "version": "0.12.0",
4
4
  "mcpName": "io.github.lemahq/lema-mcp",
5
5
  "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.",
6
6
  "bin": {
@@ -13,10 +13,10 @@
13
13
  "prepack": "cp ../../README.md ./README.md && cp ../../LICENSE ./LICENSE"
14
14
  },
15
15
  "optionalDependencies": {
16
- "lema-mcp-darwin-arm64": "0.11.0",
17
- "lema-mcp-darwin-x64": "0.11.0",
18
- "lema-mcp-linux-x64": "0.11.0",
19
- "lema-mcp-linux-arm64": "0.11.0"
16
+ "lema-mcp-darwin-arm64": "0.12.0",
17
+ "lema-mcp-darwin-x64": "0.12.0",
18
+ "lema-mcp-linux-x64": "0.12.0",
19
+ "lema-mcp-linux-arm64": "0.12.0"
20
20
  },
21
21
  "engines": {
22
22
  "node": ">=18"