@createsomething/ground-mcp 0.3.4 → 0.3.6

package/README.md

@@ -3,9 +3,9 @@
 [![npm version](https://img.shields.io/npm/v/@createsomething/ground-mcp.svg)](https://www.npmjs.com/package/@createsomething/ground-mcp)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
 
-**Grounded claims for code.** An MCP server that prevents AI hallucination in code analysis.
+**Grounded claims for code.** An MCP server that computes evidence before code-analysis claims.
 
-Works with Claude Code, Cursor, Windsurf, VS Code Copilot, Claude Desktop, and any MCP-compatible AI coding assistant.
+The verified setup contract covers Claude Code, Codex, Cursor, and Windsurf.
 
 **[View Landing Page →](https://createsomething.agency/products/ground)**
 
@@ -13,12 +13,12 @@ Works with Claude Code, Cursor, Windsurf, VS Code Copilot, Claude Desktop, and a
 
 | Capability | Without Ground | With Ground |
 |------------|---------------|-------------|
-| Duplicate detection | "These look 95% similar" | Computed 87.3% similarity via AST + token analysis |
+| Duplicate detection | "These look similar" | Computed AST + token similarity evidence |
 | Dead code claims | "This appears unused" | Verified: 0 imports, 0 type references |
 | Orphan detection | "Nothing imports this" | Checked: not a Worker entry point, not framework-implicit |
-| Design drift | "Colors look hardcoded" | Adoption ratio: 73% tokens, 27% violations |
+| Design drift | "Colors look hardcoded" | Token usage and violation counts |
 
-**The difference**: Ground requires computation before claims. No hallucinated analysis.
+**The difference**: Ground requires computation before its claim tools accept a claim.
 
 ## Recommended agent path
 
@@ -55,7 +55,7 @@ check in `check_coverage.<check>.status`. The contract is explicit:
 - `PASS`: the check completed for the relevant supported files and found no issue.
 - `FAIL`: the check found an issue or could not complete because of a read/parse failure.
 - `NOT_APPLICABLE`: no changed file needs that check.
-- `UNSUPPORTED`: relevant source exists, but the requested check cannot analyze its language (including Svelte duplicate-function scans).
+- `UNSUPPORTED`: relevant source exists, but the requested check cannot analyze its language.
 - `TIMEOUT`: duplicate analysis reached its deadline before a complete result was available.
 
 `ground analyze` and `ground diff` accept `--timeout-ms` (120000 by default).
@@ -67,13 +67,21 @@ view; read `discovered_changed_files`, `analyzable_changed_files`, and
 `unsupported_changed_files` and `excluded_changed_files`, so a clean claim is
 valid only with `PASS`.
 
-Ground 0.3.4 adds source-bearing entry-point evidence to orphan analysis, so
-declarative Promptfoo and manual Ground configurations are recognized alongside
-package scripts. It keeps `ground diff`'s complete changed-file coverage and
-deterministic, cycle-safe source traversal. Diff mode parses the complete corpus
-but only compares pairs involving changed files. Standalone broad duplicate scans
-retain their safety bound and report a non-pass status with `scan_complete: false`
-when the bound is hit.
+Ground 0.3.6 supports TypeScript (`.ts`, `.tsx`), JavaScript (`.js`, `.jsx`,
+`.mjs`), and Svelte (`.svelte`) in the declared analysis lane. Svelte component
+scripts participate in duplicate analysis, while SvelteKit configuration,
+routes, aliases, actions, stores, and framework entry points inform reachability
+and dead-export evidence. Svelte dead-export checks analyze module-context
+scripts only; instance-script exports such as legacy `export let` props are
+component API and are excluded. Inputs outside that contract remain unsupported
+rather than being reported as clean.
+
+Ground 0.3.5 extended source-bearing orphan evidence to nested Cloudflare Worker
+configurations: `wrangler.toml` and `wrangler.json` `main` entries are protected
+with their exact config source. The legacy `ground find orphans` command now
+returns the same verified canonical report as `ground analyze --checks orphans`.
+Promptfoo and manual Ground configurations remain recognized alongside package
+scripts, and broad duplicate scans retain their explicit safety bound.
 
 The release package ships thin command wrappers for every platform. Install
 downloads the matching versioned release asset and verifies its SHA-256 against
@@ -103,9 +111,10 @@ manifest have completed successfully.
 If a release was built successfully but npm publication was blocked (for
 example, during Trusted Publishing setup), rerun **Ground Release** manually
 with its exact `ground-v<version>` tag and **publish only** enabled. That path
-checks out the tag, requires it to match `package.json`, and verifies the
-existing release checksum manifest before publishing; it does not rebuild or
-replace GitHub Release assets.
+checks out the tag, executes the governed calibration fixture suite, binds its
+result to the exact source, recomputes the ledger thresholds, requires the tag
+to match `package.json`, and verifies the existing release checksum manifest
+before publishing; it does not rebuild or replace GitHub Release assets.
 
 ## The Problem
 
@@ -121,8 +130,8 @@ This is hallucination dressed up as analysis.
 
 Ground is an MCP server that:
 - Finds duplicates, dead code, and orphaned modules
-- Requires verification before claims
-- Blocks hallucinated analysis
+- Requires verification before its claim tools record a finding
+- Keeps checked inputs with the recorded claim
 - Provides confidence scores with evidence
 
 ---
@@ -138,8 +147,7 @@ This is the one everyone gets wrong. Claude Code doesn't read `.claude/mcp.json`
 **Option A: User scope (available everywhere)**
 
 ```bash
-npm install @createsomething/ground-mcp
-claude mcp add --scope user --transport stdio ground -- npx @createsomething/ground-mcp
+claude mcp add --scope user --transport stdio ground -- npx --yes -p @createsomething/ground-mcp ground-mcp
 ```
 
 Restart Claude Code, run `/mcp`, and you should see "ground" connected.
@@ -153,7 +161,7 @@ Create `.mcp.json` in your project root:
   "mcpServers": {
     "ground": {
       "command": "npx",
-      "args": ["@createsomething/ground-mcp"]
+      "args": ["--yes", "-p", "@createsomething/ground-mcp", "ground-mcp"]
     }
   }
 }
@@ -161,37 +169,16 @@ Create `.mcp.json` in your project root:
 
 Claude Code will prompt you to approve it on first use.
 
-### Cursor (One-Click)
-
-[**Install in Cursor →**](cursor://anysphere.cursor-deeplink/mcp/install?name=ground&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyJAY3JlYXRlc29tZXRoaW5nL2dyb3VuZC1tY3AiXX0%3D)
+### Cursor
 
-Or add to `.mcp.json` at your project root:
+Add to `.mcp.json` at your project root:
 
 ```json
 {
   "mcpServers": {
     "ground": {
       "command": "npx",
-      "args": ["@createsomething/ground-mcp"]
-    }
-  }
-}
-```
-
-### Claude Desktop
-
-Add to `claude_desktop_config.json`:
-
-- **macOS**: `~/Library/Application Support/Claude/claude_desktop_config.json`
-- **Windows**: `%APPDATA%\Claude\claude_desktop_config.json`
-- **Linux**: `~/.config/Claude/claude_desktop_config.json`
-
-```json
-{
-  "mcpServers": {
-    "ground": {
-      "command": "npx",
-      "args": ["@createsomething/ground-mcp"]
+      "args": ["--yes", "-p", "@createsomething/ground-mcp", "ground-mcp"]
     }
   }
 }
@@ -206,22 +193,16 @@ Settings → MCP → View raw config, add:
   "mcpServers": {
     "ground": {
       "command": "npx",
-      "args": ["@createsomething/ground-mcp"]
+      "args": ["--yes", "-p", "@createsomething/ground-mcp", "ground-mcp"]
     }
   }
 }
 ```
 
-### VS Code + Copilot
-
-1. Open Extensions panel
-2. Filter by "MCP Server"
-3. Search "ground"
-
 ### Codex CLI
 
 ```bash
-codex mcp add ground --command "npx @createsomething/ground-mcp"
+codex mcp add ground -- npx --yes -p @createsomething/ground-mcp ground-mcp
 ```
 
 ### Global Install (When npx Isn't Your Thing)
@@ -269,7 +250,7 @@ Ground needs to know where your code is. For project-specific analysis, run it f
   "mcpServers": {
     "ground": {
       "command": "npx",
-      "args": ["@createsomething/ground-mcp", "--workspace", "/path/to/your/project"]
+      "args": ["--yes", "-p", "@createsomething/ground-mcp", "ground-mcp", "--workspace", "/path/to/your/project"]
     }
   }
 }
@@ -392,7 +373,7 @@ Ground is based on a simple principle: **no claim without evidence**.
 - **Dead code** → You have to count the uses first  
 - **Orphans** → You have to check the connections first
 
-This prevents AI hallucination by requiring computation before synthesis.
+This keeps Ground's recorded claims tied to prerequisite computation.
 
 ## Configuration
 
@@ -416,11 +397,13 @@ entry_points:
 For `ground_find_orphans` and `ground_analyze`, orphan coverage includes
 `entry_point_evidence`: the exact path, entry-point type, and source Ground used
 to protect it. Alongside package, framework, test, and script entry points,
-Ground recognizes exact `entry_points.manual` declarations and local
+Ground recognizes exact `entry_points.manual` declarations, nested
+`wrangler.toml` and `wrangler.json` Worker `main` entries, and local
 `providers[].id`, `prompts[].id`, and assertion-value `file://…` references in
-`promptfooconfig*.yaml`. The Promptfoo adapter accepts only existing source
-files beneath that configuration file; it does not scan arbitrary YAML or
-follow parent/absolute paths.
+`promptfooconfig*.yaml`. The config adapters accept only existing source files
+beneath their configuration file; they do not scan arbitrary YAML or follow
+parent/absolute paths. The legacy `ground find orphans` command returns this
+same canonical orphan evidence.
 
 See [Full Documentation](https://github.com/createsomethingtoday/create-something-monorepo/tree/main/packages/ground) for configuration reference.
 

package/install.js

@@ -17,11 +17,10 @@ const VERSION = require('./package.json').version;
 const SKIP_INSTALL = process.env.GROUND_MCP_SKIP_BINARY_INSTALL === '1';
 const IS_SOURCE_TREE_INSTALL = fs.existsSync(path.resolve(__dirname, '../Cargo.toml'));
 
-// Platform mapping
-// Note: macOS Intel uses arm64 binary via Rosetta 2
+// Platform mapping. Every supported host receives a native archive.
 const PLATFORMS = {
   'darwin-arm64': 'darwin-arm64',
-  'darwin-x64': 'darwin-arm64',  // Rosetta 2 compatibility
+  'darwin-x64': 'darwin-x64',
   'linux-arm64': 'linux-arm64',
   'linux-x64': 'linux-x64',
   'win32-x64': 'win32-x64',
@@ -33,8 +32,8 @@ function getPlatformKey() {
   return `${platform}-${arch}`;
 }
 
-function getBinaryName() {
-  const key = getPlatformKey();
+function getBinaryName(platform = process.platform, arch = process.arch) {
+  const key = `${platform}-${arch}`;
   const name = PLATFORMS[key];
   
   if (!name) {
@@ -205,6 +204,7 @@ if (require.main === module) {
 
 module.exports = {
   download,
+  getBinaryName,
   getDownloadUrl,
   getChecksumsUrl,
   verifyArchiveIntegrity,

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@createsomething/ground-mcp",
-  "version": "0.3.4",
-  "description": "Grounded claims for code. MCP server that prevents AI hallucination in code analysis.",
+  "version": "0.3.6",
+  "description": "Evidence-first code analysis for agents in TypeScript, JavaScript, and Svelte codebases.",
   "author": "CREATE SOMETHING <hello@createsomething.io>",
   "license": "MIT",
   "repository": {