@capxul/mcp 4.1.4 → 4.2.0-rc.10

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.
package/README.md CHANGED
@@ -104,9 +104,12 @@ vp run --filter @capxul/mcp build
104
104
 
105
105
  The tests are hermetic: a real HTTP server, a fake token exchange, and a fake
106
106
  SDK client. They do not prove a live OAuth flow against a deployed backend, a
107
- chain path, or settlement. The published CLI still lacks an isolated
108
- packed-install smoke; [#922](https://github.com/Xelmar-tech/infrastructure/issues/922)
109
- owns that gap.
107
+ chain path, or settlement.
108
+ [#922](https://github.com/Xelmar-tech/infrastructure/issues/922) records the
109
+ historical packed-install gap. The current
110
+ `scripts/__tests__/pack-install-smoke.test.mjs` installs MCP and Sandbox
111
+ tarballs in a clean project and invokes their bins with `--help`. Run it
112
+ against the current artifacts before claiming installed-bin proof.
110
113
 
111
114
  A live staging run in #1812 proves browser login, `account:write` consent,
112
115
  Person onboarding, a ready Account, OAuth scope step-up, and the Account tools. A
@@ -0,0 +1,11 @@
1
+ {
2
+ "source": {
3
+ "commit": "a7e55e5f1c2af5567a8b285a4ef70b8b5a3289f6",
4
+ "tree": "91bf1b080c0006fe30131711c13c843afd627158",
5
+ "branch": "codex/programme-rc",
6
+ "repository": "https://github.com/Xelmar-tech/infrastructure",
7
+ "lockfileSha256": "5870f53b72706d103220c1bcf733cb4fb71196aea32a9cfbdc277d73cc959264"
8
+ },
9
+ "name": "@capxul/mcp",
10
+ "version": "4.2.0-rc.10"
11
+ }