crosscheck-mcp 0.2.27 → 0.2.28

package/README.md

@@ -5,10 +5,9 @@ orchestrate them, audit them, or rubric-grade their work — all from a single
 MCP tool surface that drops into Claude Desktop / Claude Code / Cursor /
 Continue / any other MCP host.
 
-This is the **TypeScript** implementation. There is also a Python implementation
-in [`../python/`](../python/) — both ship the same tool surface; pick whichever
-fits your stack. The TypeScript build runs natively in Node 18.17+ and has
-**no Python dependency at runtime**.
+Runs in Node 18.17+. Users install it through `crosscheck-cli`
+(`npx -y crosscheck-cli@latest install`), which supplies the activation the
+published bundle requires.
 
 ## What it does
 
@@ -137,27 +136,12 @@ Environment variables:
 | `CROSSCHECK_PRICING_PATH`         | Path to `pricing.json` (used by cheap-mode tier picker).                                      |
 | `CROSSCHECK_REPO_ROOT`            | Override repo-root detection (used by `fetch` for evidence paths).                            |
 | `CROSSCHECK_REJECT_CONFIG_DRIFT=1`| Reject pinned-config drift instead of warning.                                                |
-| `CROSSCHECK_BRIDGE_PYTHON=1`      | OPT-IN: spawn the Python server as a parity-testing backstop (see below). |
+| `CROSSCHECK_RECORD_SESSIONS=0`    | Don't record usage to the local db unless the caller passes a `session_id` (crosscheck-enterprise sets this). |
 | `CROSSCHECK_EVENTS`               | Structured event emitter: `stderr` (default), `off`, `file`, `both`. See [Observability](#observability). |
 | `CROSSCHECK_EVENTS_PATH`          | Path for the `file` / `both` event sinks (ND-JSON, one event per line).                       |
 | `<PROVIDER>_API_KEY`              | At least one is required for LLM-using tools. Optional for `verify`-only flows.               |
 | `<PROVIDER>_MODEL`                | Override a provider's default model.                                                          |
 
-The Python backstop is OPTIONAL. **Every v1 feature path on every
-tool runs natively in TypeScript.** The bridge is useful for:
-1. Cross-language parity testing (the `test/parity/` fixtures check
-   that the TS implementation produces byte-equal output against
-   the Python oracle).
-2. The `reactive` opt on `orchestrate` (mid-flight DAG mutation),
-   which still defers to bridge.
-3. A few remaining advanced opts that no longer have a Node-side
-   implementation but kept the bridge as a fallback when host
-   integrations aren't wired (e.g. `worker_tools` without
-   `innerCallers`).
-
-Everything in the [Tools](#what-it-does) list above works without
-\`CROSSCHECK_BRIDGE_PYTHON\` being set.
-
 ## Observability
 
 Every `tools/call` request emits one structured `tool_invoke` event