@createsomething/ground-mcp 0.3.3 → 0.3.4

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 +50 -5
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -67,11 +67,13 @@ 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.4 adds source-bearing entry-point evidence to orphan analysis, so
71
+ declarative Promptfoo and manual Ground configurations are recognized alongside
72
+ package scripts. It keeps `ground diff`'s complete changed-file coverage and
73
+ deterministic, cycle-safe source traversal. Diff mode parses the complete corpus
74
+ but only compares pairs involving changed files. Standalone broad duplicate scans
75
+ retain their safety bound and report a non-pass status with `scan_complete: false`
76
+ when the bound is hit.
75
77
 
76
78
  The release package ships thin command wrappers for every platform. Install
77
79
  downloads the matching versioned release asset and verifies its SHA-256 against
@@ -82,6 +84,29 @@ that produced a receipt with:
82
84
  ground build-info --json
83
85
  ```
84
86
 
87
+ ### Maintainers: trusted publishing
88
+
89
+ Ground tags publish through npm Trusted Publishing rather than a local
90
+ one-time-password or a long-lived write token. Configure the package's
91
+ **Trusted Publisher** in npm with:
92
+
93
+ - Provider: **GitHub Actions**
94
+ - Organization or user: `createsomethingtoday`
95
+ - Repository: `create-something-monorepo`
96
+ - Workflow filename: `ground-release.yml`
97
+ - Allowed action: **npm publish**
98
+
99
+ Do not configure an environment unless the release workflow adds one. The
100
+ workflow publishes only after its matching GitHub Release and `SHA256SUMS`
101
+ manifest have completed successfully.
102
+
103
+ If a release was built successfully but npm publication was blocked (for
104
+ example, during Trusted Publishing setup), rerun **Ground Release** manually
105
+ with its exact `ground-v<version>` tag and **publish only** enabled. That path
106
+ checks out the tag, requires it to match `package.json`, and verifies the
107
+ existing release checksum manifest before publishing; it does not rebuild or
108
+ replace GitHub Release assets.
109
+
85
110
  ## The Problem
86
111
 
87
112
  AI agents are confident. Too confident.
@@ -375,8 +400,28 @@ Ground loads `.ground.yml` from your project root for:
375
400
  - Ignore patterns (functions, files, directories)
376
401
  - Known drift exceptions with documented reasons
377
402
  - Context declarations for intentional exclusions
403
+ - Explicit manual CLI entry points for orphan review
378
404
  - Similarity thresholds
379
405
 
406
+ Declare a documented operator CLI by exact path relative to the directory you
407
+ pass to `ground diff`. Ground keeps it in duplicate coverage, excludes it only
408
+ from orphan findings, and records `manual_entry_point` in check coverage:
409
+
410
+ ```yaml
411
+ entry_points:
412
+ manual:
413
+ - "scripts/rebuild-search-index.mjs"
414
+ ```
415
+
416
+ For `ground_find_orphans` and `ground_analyze`, orphan coverage includes
417
+ `entry_point_evidence`: the exact path, entry-point type, and source Ground used
418
+ to protect it. Alongside package, framework, test, and script entry points,
419
+ Ground recognizes exact `entry_points.manual` declarations and local
420
+ `providers[].id`, `prompts[].id`, and assertion-value `file://…` references in
421
+ `promptfooconfig*.yaml`. The Promptfoo adapter accepts only existing source
422
+ files beneath that configuration file; it does not scan arbitrary YAML or
423
+ follow parent/absolute paths.
424
+
380
425
  See [Full Documentation](https://github.com/createsomethingtoday/create-something-monorepo/tree/main/packages/ground) for configuration reference.
381
426
 
382
427
  ## 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.4",
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",