@vitest-agent/mcp 1.0.1 → 1.2.0

package/README.md

@@ -6,12 +6,11 @@
 
 > **Part of the [vitest-agent](https://vitest-agent.dev) ecosystem.** Most users want **[@vitest-agent/plugin](https://www.npmjs.com/package/@vitest-agent/plugin)**, which pulls this package in automatically. Install `@vitest-agent/mcp` directly only if you run the MCP server standalone.
 
-The `vitest-agent-mcp` MCP server bin. Exposes action-keyed tools over stdio that give LLM agents structured access to test data, coverage, history, failure signatures, TDD lifecycle state and more. Also surfaces four MCP resources (vendored Vitest docs and curated testing patterns) and six framing-only prompts.
+The `vitest-agent-mcp` MCP server bin. Exposes action-keyed tools over stdio that give LLM agents structured access to test data, coverage, history, failure signatures, TDD lifecycle state and more. Also surfaces six framing-only prompts.
 
 ## Features
 
 - **29 action-keyed tools** — per-CRUD families collapse into single tools dispatching on an `action` discriminator; covers `test_status`, `test_overview`, `test_coverage`, `test_errors`, `run_tests`, `note`, `hypothesis`, `tdd_task`, `tdd_goal`, `tdd_behavior` and more
-- **Four MCP resources** — vendored Vitest documentation (`vitest://docs/`) and curated testing patterns (`vitest-agent://patterns/`) with per-page titles, descriptions and `audience`/`priority` annotations
 - **Six framing prompts** — `triage`, `why-flaky`, `regression-since-pass`, `explain-failure`, `tdd-resume`, `wrapup`
 - **Idempotency middleware** — `tdd_task`, `tdd_goal`, `tdd_behavior` and `hypothesis` create-actions are idempotent on derived keys
 

package/bin/vitest-agent-mcp.js

@@ -2,27 +2,12 @@
 import { createCurrentSessionIdRef, createSessionContextRef, sessionContextFromEnv } from "../context.js";
 import { McpLive } from "../layers/McpLive.js";
 import { startMcpServer } from "../server.js";
-import { CURRENT_MCP_VERSION } from "../index.js";
 import { NodeContext } from "@effect/platform-node";
-import { CURRENT_SDK_VERSION, PathResolutionLive, formatFatalError, resolveDataPath, resolveLogFile, resolveLogLevel } from "@vitest-agent/sdk";
+import { PathResolutionLive, formatFatalError, resolveDataPath, resolveLogFile, resolveLogLevel } from "@vitest-agent/sdk";
 import { Effect, ManagedRuntime } from "effect";
 
 //#region src/bin.ts
 /**
-* Cross-package version drift check. Compares this MCP package's version
-* against @vitest-agent/sdk and writes a single stderr line on mismatch.
-* Observation-only — never throws. The `"0.0.0"` fallback marks a dev
-* build (rslib-builder did not substitute the literal); skip the check
-* to avoid spurious warnings during local source-loaded runs. See the
-* root CLAUDE.md "Cross-package version drift" section.
-*
-* @internal
-*/
-function checkVersionDrift() {
-	if ("1.0.1" === "0.0.0") return;
-	if (CURRENT_SDK_VERSION !== "1.0.1") process.stderr.write(`[@vitest-agent/mcp] version drift: @vitest-agent/mcp@${CURRENT_MCP_VERSION} with @vitest-agent/sdk@${CURRENT_SDK_VERSION}. Reinstall @vitest-agent/* packages so versions match.\n`);
-}
-/**
 * Resolve the user's project directory.
 *
 * Precedence (most explicit wins):
@@ -63,7 +48,6 @@ function resolveInitialSessionId() {
 }
 async function main() {
 	const projectDir = resolveProjectDir();
-	checkVersionDrift();
 	const initialSessionId = resolveInitialSessionId();
 	const dbPath = await Effect.runPromise(resolveDataPath(projectDir).pipe(Effect.provide(PathResolutionLive(projectDir)), Effect.provide(NodeContext.layer)));
 	const logLevel = resolveLogLevel();