@createsomething/ground-mcp 0.3.3 → 0.3.5

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 +51 -5
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -67,11 +67,12 @@ view; read `discovered_changed_files`, `analyzable_changed_files`, and
67
67
  `unsupported_changed_files` and `excluded_changed_files`, so a clean claim is
68
68
  valid only with `PASS`.
69
69
 
70
- Ground 0.3.3 keeps `ground diff`'s complete changed-file coverage and makes
71
- source traversal deterministic and cycle-safe. Diff mode parses the complete
72
- corpus but only compares pairs involving changed files. Standalone broad
73
- duplicate scans retain their safety bound and report their non-pass status with
74
- `scan_complete: false` when the bound is hit.
70
+ Ground 0.3.5 extends source-bearing orphan evidence to nested Cloudflare Worker
71
+ configurations: `wrangler.toml` and `wrangler.json` `main` entries are protected
72
+ with their exact config source. The legacy `ground find orphans` command now
73
+ returns the same verified canonical report as `ground analyze --checks orphans`.
74
+ Promptfoo and manual Ground configurations remain recognized alongside package
75
+ scripts, and broad duplicate scans retain their explicit safety bound.
75
76
 
76
77
  The release package ships thin command wrappers for every platform. Install
77
78
  downloads the matching versioned release asset and verifies its SHA-256 against
@@ -82,6 +83,29 @@ that produced a receipt with:
82
83
  ground build-info --json
83
84
  ```
84
85
 
86
+ ### Maintainers: trusted publishing
87
+
88
+ Ground tags publish through npm Trusted Publishing rather than a local
89
+ one-time-password or a long-lived write token. Configure the package's
90
+ **Trusted Publisher** in npm with:
91
+
92
+ - Provider: **GitHub Actions**
93
+ - Organization or user: `createsomethingtoday`
94
+ - Repository: `create-something-monorepo`
95
+ - Workflow filename: `ground-release.yml`
96
+ - Allowed action: **npm publish**
97
+
98
+ Do not configure an environment unless the release workflow adds one. The
99
+ workflow publishes only after its matching GitHub Release and `SHA256SUMS`
100
+ manifest have completed successfully.
101
+
102
+ If a release was built successfully but npm publication was blocked (for
103
+ example, during Trusted Publishing setup), rerun **Ground Release** manually
104
+ with its exact `ground-v<version>` tag and **publish only** enabled. That path
105
+ checks out the tag, requires it to match `package.json`, and verifies the
106
+ existing release checksum manifest before publishing; it does not rebuild or
107
+ replace GitHub Release assets.
108
+
85
109
  ## The Problem
86
110
 
87
111
  AI agents are confident. Too confident.
@@ -375,8 +399,30 @@ Ground loads `.ground.yml` from your project root for:
375
399
  - Ignore patterns (functions, files, directories)
376
400
  - Known drift exceptions with documented reasons
377
401
  - Context declarations for intentional exclusions
402
+ - Explicit manual CLI entry points for orphan review
378
403
  - Similarity thresholds
379
404
 
405
+ Declare a documented operator CLI by exact path relative to the directory you
406
+ pass to `ground diff`. Ground keeps it in duplicate coverage, excludes it only
407
+ from orphan findings, and records `manual_entry_point` in check coverage:
408
+
409
+ ```yaml
410
+ entry_points:
411
+ manual:
412
+ - "scripts/rebuild-search-index.mjs"
413
+ ```
414
+
415
+ For `ground_find_orphans` and `ground_analyze`, orphan coverage includes
416
+ `entry_point_evidence`: the exact path, entry-point type, and source Ground used
417
+ to protect it. Alongside package, framework, test, and script entry points,
418
+ Ground recognizes exact `entry_points.manual` declarations, nested
419
+ `wrangler.toml` and `wrangler.json` Worker `main` entries, and local
420
+ `providers[].id`, `prompts[].id`, and assertion-value `file://…` references in
421
+ `promptfooconfig*.yaml`. The config adapters accept only existing source files
422
+ beneath their configuration file; they do not scan arbitrary YAML or follow
423
+ parent/absolute paths. The legacy `ground find orphans` command returns this
424
+ same canonical orphan evidence.
425
+
380
426
  See [Full Documentation](https://github.com/createsomethingtoday/create-something-monorepo/tree/main/packages/ground) for configuration reference.
381
427
 
382
428
  ## Native service pilot
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@createsomething/ground-mcp",
3
- "version": "0.3.3",
3
+ "version": "0.3.5",
4
4
  "description": "Grounded claims for code. MCP server that prevents AI hallucination in code analysis.",
5
5
  "author": "CREATE SOMETHING <hello@createsomething.io>",
6
6
  "license": "MIT",
@@ -62,7 +62,7 @@
62
62
  "pilot:verify": "pnpm run pilot:check && pnpm run pilot:test && pnpm run pilot:benchmark && pnpm run pilot:receipt:validate -- pilot/evidence/ground-native-benchmark-receipt.v1.json"
63
63
  },
64
64
  "devDependencies": {
65
- "@modelcontextprotocol/sdk": "^1.25.3",
65
+ "@modelcontextprotocol/sdk": "^1.26.0",
66
66
  "@types/node": "^24.10.9",
67
67
  "ajv": "^8.17.1",
68
68
  "tsx": "^4.21.0",