@strixgov/mcp-proxy 0.1.5 → 0.1.6

package/CHANGELOG.md

@@ -5,6 +5,32 @@ All notable changes to `@strixgov/mcp-proxy` are documented here.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.1.6]
+
+Documentation + license-fidelity patch. No functional change to the proxy,
+the receipt format, the signing flow, or any runtime behavior.
+
+### Fixed
+- **`LICENSE` corrected to canonical Elastic License 2.0.** The Limitations
+  clause read "provide the software to **others** as a hosted or managed
+  service"; the canonical ELv2 wording is "to **third parties**." Corrected
+  byte-for-byte against Elastic's published license. The `0.1.0` release note
+  flagged this exact verification ("verify the bundled LICENSE against
+  canonical ELv2 before tagging") — the deviation shipped anyway in 0.1.0 and
+  0.1.5. Legal-text fidelity only; no change to intent or the MIT/ELv2 split.
+  **Counsel should confirm before publish.**
+- **README version labels.** Notes describing *current* behavior were tagged
+  `v0.1.0` (the floor where they were first true); a reader on npm sees
+  `0.1.5+`. Relabeled the current-behavior notes (transport scope, env-var
+  substitution, feature-table column, Mode-3 seam, single-tenant boundary) to
+  `v0.1.x`. Genuinely historical references (the `v0.1.0–v0.1.3` ephemeral-key
+  known issue, `v0.1.4+` default `storagePath`) are unchanged.
+
+### Note
+- Closes findings F-3 and F-4 of
+  `docs/reviews/mcp-proxy-publish-readiness-2026-06-07.md`. Repeatable
+  publish gate: `scripts/mcp-proxy-preflight.mjs`.
+
 ## [0.1.5]
 
 Documentation-hygiene patch. No functional change to the proxy, the

package/LICENSE

@@ -13,7 +13,7 @@ to the limitations and conditions below.
 
 Limitations
 
-You may not provide the software to others as a hosted or managed service,
+You may not provide the software to third parties as a hosted or managed service,
 where the service provides users with access to any substantial set of the
 features or functionality of the software.
 

package/README.md

@@ -35,7 +35,7 @@ Tool implementations are untouched. The MCP client (Claude Desktop, mcp-cli,
 IDE integration, your own code) doesn't need to know Strix exists — it just
 spawns this proxy in place of the upstream server.
 
-> **Transport scope (v0.1.0):** the proxy wraps MCP servers that speak
+> **Transport scope (v0.1.x):** the proxy wraps MCP servers that speak
 > the **stdio transport** — the `command` / `args` pattern in
 > `claude_desktop_config.json`. It does **not** intercept HTTP-based
 > hosted MCP servers (e.g. Notion's `https://mcp.notion.com/mcp`
@@ -121,7 +121,7 @@ for a complete example.
 
 ### Where the upstream's secrets should live
 
-v0.1.0 does **no env-var substitution inside the config file** — there
+v0.1.x does **no env-var substitution inside the config file** — there
 is no `${NOTION_TOKEN}` template syntax. Two supported patterns for
 upstream secrets:
 
@@ -217,7 +217,7 @@ Run `strix-mcp-proxy --help` for the full flag list.
 
 ## What ships with the proxy
 
-| Feature | v0.1.0 | v0.2.0 (planned) |
+| Feature | v0.1.x (shipped) | v0.2.0 (planned) |
 |---|---|---|
 | MCP stdio transport (consumer side) | ✓ | — |
 | MCP stdio transport (upstream side) | ✓ | — |
@@ -241,7 +241,7 @@ at each enforcement strength.
 ## The upgrade path to Mode 3
 
 Mode 3 — Capability-Enforced — is the upgrade, not a rewrite. The
-v0.1.0 proxy already routes every outbound call through a single
+v0.1.x proxy already routes every outbound call through a single
 `buildUpstreamIface()` seam in `src/proxy.mjs`. In v0.2.0 a new option
 (`mode: "enforced"`) will wrap that seam with the
 `execution_authorization_v1` token mint + transport step per
@@ -254,7 +254,7 @@ refuse to act on sensitive tools unless the token is present.
 
 The cryptographic primitive is already shipped — see
 [`@strixgov/mcp-token-validator`](https://www.npmjs.com/package/@strixgov/mcp-token-validator).
-v0.1.0 of the proxy does not mint these tokens yet; what it does is
+v0.1.x of the proxy does not mint these tokens yet; what it does is
 make sure the *seam* exists so v0.2.0 plugs in cleanly.
 
 ## Listening to receipts (programmatic embedding)
@@ -357,7 +357,7 @@ keys are strictly better in every dimension that isn't a one-off demo.
   the library; the proxy is the standalone process. They share the
   same governance core (`@strixgov/tool-gateway`) and produce
   byte-identical receipts.
-- **Not an interceptor of HTTP-transport MCP servers.** v0.1.0 wraps
+- **Not an interceptor of HTTP-transport MCP servers.** v0.1.x wraps
   the stdio transport only. Hosted HTTP MCP servers (the Claude
   Desktop "Add Connector" URL pattern, e.g.
   `https://mcp.notion.com/mcp`) are not in scope — the client talks
@@ -365,7 +365,7 @@ keys are strictly better in every dimension that isn't a one-off demo.
   Use the upstream's local stdio server in the meantime; the
   HTTP-transport story is Posture B in
   [`docs/architecture/mcp-mode-3-enforcement-v1.md`](https://github.com/Strixgov/strix/tree/main/docs/architecture/mcp-mode-3-enforcement-v1.md).
-- **Not Mode 3 today.** v0.1.0 ships Mode 1 + Mode 2. Mode 3
+- **Not Mode 3 today.** v0.1.x ships Mode 1 + Mode 2. Mode 3
   enforcement is the v0.2.0 upgrade path, designed for, but not
   implemented in, this release.
 - **Not a credential vault.** Upstream tokens (`NOTION_TOKEN`,
@@ -405,7 +405,7 @@ posture, including:
 - **Process model** — what happens on crash / mid-approval / disk
   full. Fail-closed at every boundary; the proxy will not start
   without a loadable signing key.
-- **Multi-tenant boundary** — single-tenant by design in v0.1.0;
+- **Multi-tenant boundary** — single-tenant by design in v0.1.x;
   run one proxy process per tenant for isolation.
 - **What the proxy does NOT govern** — out-of-wrapper traffic, the
   agent's internal state, the upstream's own argument handling

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@strixgov/mcp-proxy",
-  "version": "0.1.5",
+  "version": "0.1.6",
   "description": "Strix MCP Proxy — the distribution wedge for governed agent tool execution. Point your MCP client at the proxy instead of the underlying server; every callTool is intercepted, evaluated against policy, and emits a signed Ed25519 receipt. Designed so Mode 3 (capability-enforced) is the v0.2.0 upgrade path, not a rewrite.",
   "license": "Elastic-2.0",
   "type": "module",