@vitest-agent/mcp 1.0.1 → 1.2.0

package/index.js

@@ -7,13 +7,11 @@ import { startMcpServer } from "./server.js";
 /**
 * The version of this package, inlined at build time from
 * package.json#version via rslib-builder's __PACKAGE_VERSION__ substitution.
-* Compared against CURRENT_SDK_VERSION at MCP bin init to surface
-* partially-upgraded installs as a single stderr warning. See the root
-* CLAUDE.md "Cross-package version drift" section.
+* Exported for version introspection by downstream tooling.
 *
 * @public
 */
-const CURRENT_MCP_VERSION = "1.0.1";
+const CURRENT_MCP_VERSION = "1.2.0";
 
 //#endregion
 export { CURRENT_MCP_VERSION, McpLive, appRouter, createCallerFactory, createCurrentSessionIdRef, createSessionContextRef, startMcpServer };

package/middleware/idempotency.js

@@ -125,4 +125,4 @@ const idempotent = middleware(async (opts) => {
 const idempotentProcedure = publicProcedure.use(idempotent);
 
 //#endregion
-export { idempotentProcedure };
+export { idempotencyKeys, idempotentProcedure };

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@vitest-agent/mcp",
-	"version": "1.0.1",
+	"version": "1.2.0",
 	"private": false,
 	"description": "Model Context Protocol server for vitest-agent. Exposes 53 tools for agent access to test data, TDD lifecycle, and session management.",
 	"keywords": [
@@ -45,7 +45,7 @@
 		"@effect/sql-sqlite-node": "^0.52.0",
 		"@modelcontextprotocol/sdk": "^1.29.0",
 		"@trpc/server": "^11.18.0",
-		"@vitest-agent/sdk": "1.0.1",
+		"@vitest-agent/sdk": "1.1.0",
 		"effect": "^3.21.4",
 		"zod": "^4.4.3"
 	},

package/server.js

@@ -30,7 +30,6 @@ import { TurnSearchAsMarkdown, TurnSearchResult } from "./tools/turn-search.js";
 import { WrapupPromptResult } from "./tools/wrapup-prompt.js";
 import { appRouter } from "./router.js";
 import { registerAllPrompts } from "./prompts/index.js";
-import { registerAllResources } from "./resources/index.js";
 import { effectToZodSchema } from "./utils/effect-to-zod.js";
 import { ChannelEvent, DataReader } from "@vitest-agent/sdk";
 import { Effect, Option, Schema } from "effect";
@@ -123,10 +122,10 @@ function structuredJsonResult(value) {
 	return structuredResult(JSON.stringify(value, null, 2), value);
 }
 /**
-* Starts the MCP server over stdio, registering all tools, resources, and prompts.
+* Starts the MCP server over stdio, registering all tools and prompts.
 *
 * Constructs the MCP server instance, registers all tRPC-backed tools (wired through
-* `ctx.runtime`), calls `registerAllResources` and `registerAllPrompts`, then connects
+* `ctx.runtime`), calls `registerAllPrompts`, then connects
 * a `StdioServerTransport`. Returns when the transport disconnects.
 *
 * @param ctx - the MCP context carrying the shared ManagedRuntime and session refs
@@ -828,7 +827,6 @@ async function startMcpServer(ctx) {
 		const data = await caller.ping();
 		return structuredResult(data.message, data);
 	});
-	registerAllResources(server);
 	registerAllPrompts(server);
 	const transport = new StdioServerTransport();
 	await server.connect(transport);

package/tools/acceptance-metrics.js

@@ -72,4 +72,4 @@ const acceptanceMetrics = publicProcedure.input(Schema.standardSchemaV1(Schema.S
 })));
 
 //#endregion
-export { AcceptanceMetricsAsMarkdown, AcceptanceMetricsResult, acceptanceMetrics };
+export { AcceptanceMetricsAsMarkdown, AcceptanceMetricsResult, acceptanceMetrics, formatAcceptanceMetricsMarkdown };

package/tools/cache-health.js

@@ -80,4 +80,4 @@ const cacheHealth = publicProcedure.query(async ({ ctx }) => ctx.runtime.runProm
 })));
 
 //#endregion
-export { CacheHealthAsMarkdown, CacheHealthResult, cacheHealth };
+export { CacheHealthAsMarkdown, CacheHealthResult, cacheHealth, formatCacheHealthMarkdown };

package/tools/commit-changes.js

@@ -61,4 +61,4 @@ const commitChanges = publicProcedure.input(Schema.standardSchemaV1(Schema.Struc
 })));
 
 //#endregion
-export { CommitChangesAsMarkdown, CommitChangesResult, commitChanges };
+export { CommitChangesAsMarkdown, CommitChangesResult, commitChanges, formatCommitChangesMarkdown };

package/tools/configure.js

@@ -104,4 +104,4 @@ const configure = publicProcedure.input(Schema.standardSchemaV1(Schema.Struct({
 })));
 
 //#endregion
-export { ConfigureAsMarkdown, ConfigureResult, configure };
+export { ConfigureAsMarkdown, ConfigureResult, configure, formatConfigureMarkdown };

package/tools/coverage.js

@@ -73,4 +73,4 @@ const testCoverage = publicProcedure.input(Schema.standardSchemaV1(Schema.Struct
 })));
 
 //#endregion
-export { TestCoverageAsMarkdown, TestCoverageResult, testCoverage };
+export { TestCoverageAsMarkdown, TestCoverageResult, formatTestCoverageMarkdown, testCoverage };

package/tools/errors.js

@@ -148,4 +148,4 @@ const testErrors = publicProcedure.input(Schema.standardSchemaV1(Schema.Struct({
 })));
 
 //#endregion
-export { TestErrorsAsMarkdown, TestErrorsResult, testErrors };
+export { TestErrorRow, TestErrorsAsMarkdown, TestErrorsResult, formatTestErrorsMarkdown, testErrors };

package/tools/failure-signature-get.js

@@ -70,4 +70,4 @@ const failureSignatureGet = publicProcedure.input(Schema.standardSchemaV1(Schema
 })));
 
 //#endregion
-export { FailureSignatureGetAsMarkdown, FailureSignatureGetResult, failureSignatureGet };
+export { FailureSignatureGetAsMarkdown, FailureSignatureGetResult, failureSignatureGet, formatFailureSignatureMarkdown };

package/tools/file-coverage.js

@@ -103,4 +103,4 @@ const fileCoverage = publicProcedure.input(Schema.standardSchemaV1(Schema.Struct
 })));
 
 //#endregion
-export { FileCoverageAsMarkdown, FileCoverageResult, fileCoverage };
+export { FileCoverageAsMarkdown, FileCoverageResult, fileCoverage, formatFileCoverageMarkdown };

package/tools/history.js

@@ -118,4 +118,4 @@ const testHistory = publicProcedure.input(Schema.standardSchemaV1(Schema.Struct(
 })));
 
 //#endregion
-export { TestHistoryAsMarkdown, TestHistoryResult, testHistory };
+export { TestHistoryAsMarkdown, TestHistoryResult, formatTestHistoryMarkdown, testHistory };

package/tools/inventory.js

@@ -374,4 +374,4 @@ const inventory = publicProcedure.input(Schema.standardSchemaV1(InventoryInput))
 });
 
 //#endregion
-export { InventoryAsMarkdown, InventoryResult, inventory };
+export { InventoryAsMarkdown, InventoryResult, formatInventoryMarkdown, inventory };

package/tools/overview.js

@@ -89,4 +89,4 @@ const testOverview = publicProcedure.input(Schema.standardSchemaV1(Schema.Struct
 })));
 
 //#endregion
-export { TestOverviewAsMarkdown, TestOverviewResult, testOverview };
+export { TestOverviewAsMarkdown, TestOverviewResult, formatTestOverviewMarkdown, testOverview };

package/tools/run-tests.js

@@ -1,5 +1,5 @@
 import { publicProcedure } from "../context.js";
-import { AgentReport, DataReader, DataStore, buildAgentReport } from "@vitest-agent/sdk";
+import { AgentReport, DataReader, DataStore, buildAgentReport, buildConsoleLeaks, collectConsoleLeakEntries } from "@vitest-agent/sdk";
 import { Effect, ParseResult, Schema } from "effect";
 import { AsyncLocalStorage } from "node:async_hooks";
 import { Writable } from "node:stream";
@@ -209,6 +209,13 @@ function formatReportMarkdown(report, classifications) {
 	if (summary.skipped > 0) headlineParts.push(`${summary.skipped} skipped`);
 	lines.push(`## ${status} Vitest -- ${headlineParts.join(", ")} (${summary.duration}ms)`);
 	if (report.project) lines.push(`\nProject: ${report.project}`);
+	if (report.consoleLeaks !== void 0) {
+		const cl = report.consoleLeaks;
+		const writes = `${cl.total} stray console write${cl.total === 1 ? "" : "s"}`;
+		const plural = cl.byFile.length !== 1 || cl.truncated === true;
+		const files = `${cl.byFile.length}${cl.truncated === true ? "+" : ""} file${plural ? "s" : ""}`;
+		lines.push(`\n⚠ ${writes} across ${files} (see consoleLeaks)`);
+	}
 	for (const mod of report.failed) {
 		lines.push(`\n### \u274C \`${mod.file}\``);
 		if (mod.errors) for (const err of mod.errors) {
@@ -313,7 +320,12 @@ const runTests = publicProcedure.input(Schema.standardSchemaV1(Schema.Struct({
 				resolvedExpression
 			}
 		};
-		const report = buildAgentReport(testModules, unhandledErrors, unhandledErrors.length > 0 || result.testModules.some((m) => m.state() === "failed") ? "failed" : "passed", { omitPassingTests: true });
+		const baseReport = buildAgentReport(testModules, unhandledErrors, unhandledErrors.length > 0 || result.testModules.some((m) => m.state() === "failed") ? "failed" : "passed", { omitPassingTests: true });
+		const leaks = buildConsoleLeaks(collectConsoleLeakEntries(localVitest.state.getFiles()));
+		const report = leaks !== void 0 ? {
+			...baseReport,
+			consoleLeaks: leaks
+		} : baseReport;
 		let classifications;
 		try {
 			classifications = await ctx.runtime.runPromise(Effect.gen(function* () {
@@ -356,4 +368,4 @@ const runTests = publicProcedure.input(Schema.standardSchemaV1(Schema.Struct({
 }));
 
 //#endregion
-export { RunTestsAsMarkdown, RunTestsResult, runTests };
+export { RunTestsAsMarkdown, RunTestsResult, coerceErrors, composeTagExpression, formatNoMatchMarkdown, formatReportMarkdown, formatRunTestsMarkdown, runTests, sanitizeTestArgs, withStdioCaptured };

package/tools/settings-list.js

@@ -45,4 +45,4 @@ const settingsList = publicProcedure.input(Schema.standardSchemaV1(Schema.Struct
 })));
 
 //#endregion
-export { SettingsListAsMarkdown, SettingsListResult, settingsList };
+export { SettingsListAsMarkdown, SettingsListResult, formatSettingsListMarkdown, settingsList };

package/tools/status.js

@@ -71,4 +71,4 @@ const testStatus = publicProcedure.input(Schema.standardSchemaV1(Schema.Struct({
 })));
 
 //#endregion
-export { TestStatusAsMarkdown, TestStatusResult, testStatus };
+export { TestStatusAsMarkdown, TestStatusResult, formatTestStatusMarkdown, testStatus };

package/tools/tdd-artifact.js

@@ -98,4 +98,4 @@ const tddArtifactList = publicProcedure.input(Schema.standardSchemaV1(TddArtifac
 })));
 
 //#endregion
-export { TddArtifactListAsMarkdown, TddArtifactListResult, tddArtifactList };
+export { TddArtifactListAsMarkdown, TddArtifactListResult, formatTddArtifactListMarkdown, tddArtifactList };

package/tools/tdd-task.js

@@ -275,4 +275,4 @@ const tddTask = idempotentProcedure.input(Schema.standardSchemaV1(TddTaskInput))
 });
 
 //#endregion
-export { TddTaskAsMarkdown, TddTaskResult, tddTask };
+export { TddTaskAsMarkdown, TddTaskResult, formatTddTaskMarkdown, tddTask };

package/tools/test.js

@@ -278,4 +278,4 @@ const test = publicProcedure.input(Schema.standardSchemaV1(TestInput)).query(asy
 });
 
 //#endregion
-export { TestAsMarkdown, TestResult, test };
+export { TestAsMarkdown, TestResult, formatTestMarkdown, test };

package/tools/trends.js

@@ -109,4 +109,4 @@ const testTrends = publicProcedure.input(Schema.standardSchemaV1(Schema.Struct({
 })));
 
 //#endregion
-export { TestTrendsAsMarkdown, TestTrendsResult, testTrends };
+export { TestTrendsAsMarkdown, TestTrendsResult, formatTestTrendsMarkdown, testTrends };

package/tools/turn-search.js

@@ -57,4 +57,4 @@ const turnSearch = publicProcedure.input(Schema.standardSchemaV1(Schema.Struct({
 })));
 
 //#endregion
-export { TurnSearchAsMarkdown, TurnSearchResult, turnSearch };
+export { TurnSearchAsMarkdown, TurnSearchResult, formatTurnSearchMarkdown, turnSearch };

package/public/patterns/_meta.json

@@ -1,67 +0,0 @@
-{
-	"patterns": [
-		{
-			"slug": "testing-effect-services-with-mock-layers",
-			"title": "Testing Effect Services with Mock Layers",
-			"summary": "Compose live and test layers, swap platform layers, assert on accumulated writes via state-container test layers.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.9
-			}
-		},
-		{
-			"slug": "testing-effect-schema-definitions",
-			"title": "Testing Effect Schema Definitions",
-			"summary": "Round-trip Schema.Class and Schema.Struct, branded types, transformations, and decoding error assertions.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.9
-			}
-		},
-		{
-			"slug": "authoring-a-custom-vitest-agent-reporter",
-			"title": "Authoring a Custom vitest-agent Reporter",
-			"summary": "Implement the VitestAgentReporterFactory contract: ReporterKit, RenderedOutput targets, stdOsc8 hyperlinks, composing with the default reporter.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.7
-			}
-		},
-		{
-			"slug": "running-tests-via-mcp",
-			"title": "Running Tests via the MCP run_tests Tool",
-			"summary": "Scope runs with project/files/tags (there is no `filter` param), read the four-variant return shape, and understand why subset runs 'fail' coverage thresholds.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.9
-			}
-		},
-		{
-			"slug": "silencing-leaking-output-in-tests",
-			"title": "Silencing Leaking Log / Build Output in Tests",
-			"summary": "Decision tree mapping each noise source (Effect logger, console.*, rsbuild, tsdown, API Extractor) to its silencing technique, with an assert-on-output guardrail.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.8
-			}
-		},
-		{
-			"slug": "known-issues-and-caveats",
-			"title": "Known Issues & Instrumentation Caveats",
-			"summary": "Distinguishes real vitest-agent issues (DataStoreError UNIQUE race) from upstream Vitest caveats (coverage-dir ENOENT), already-fixed bugs (perf_hooks), and misconceptions (discovery-cache staleness).",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.7
-			}
-		},
-		{
-			"slug": "operating-vitest-agent-as-an-agent",
-			"title": "Operating vitest-agent as an Agent",
-			"summary": "Read first: the front-loaded facts an agent needs (no run_tests filter param, coverage-in-subset behavior, console output is config-driven not env-driven, attribution is auto-recovered) with links to the deeper patterns.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.95
-			}
-		}
-	]
-}

package/public/patterns/authoring-a-custom-vitest-agent-reporter.md

@@ -1,82 +0,0 @@
-# Authoring a Custom vitest-agent Reporter
-
-## When to use
-
-You want output behavior that the named factories in `@vitest-agent/reporter` (`defaultReporter`, `markdownReporter`, `jsonReporter`, etc.) do not provide. Examples: SARIF output for code-scanning ingestion, JUnit XML alongside the default markdown, a side-channel that posts to an internal API.
-
-## The contract
-
-A reporter is a function that takes a `ReporterKit` and returns either a single `VitestAgentReporter` or an array. A reporter has exactly one method: synchronous `render(input)` that returns `RenderedOutput[]`. No I/O, no Vitest lifecycle. The plugin handles persistence, classification, baselines, and trends; reporters render the resulting data and the plugin routes the outputs to their declared targets.
-
-```typescript
-type VitestAgentReporterFactory =
- (kit: ReporterKit) =>
-  VitestAgentReporter | ReadonlyArray<VitestAgentReporter>;
-
-interface VitestAgentReporter {
- readonly render:
-  (input: ReporterRenderInput) => ReadonlyArray<RenderedOutput>;
-}
-```
-
-`ReporterKit` carries `config`, `stdEnv`, and `stdOsc8` (a pre-bound hyperlink helper). `ReporterRenderInput` carries `reports` (one per project), `classifications` (a Map keyed by `TestReport.fullName`), and an optional `trendSummary`.
-
-## Minimal example: a SARIF sidecar
-
-```typescript
-import type { VitestAgentReporterFactory } from "@vitest-agent/sdk";
-
-export const sarifReporter: VitestAgentReporterFactory = (kit) => ({
- render: (input) => {
-  const sarif = buildSarif(input.reports);
-  return [
-   {
-    target: "file",
-    content: JSON.stringify(sarif),
-    contentType: "application/sarif+json",
-   },
-  ];
- },
-});
-```
-
-The `target: "file"` slot is reserved for arbitrary on-disk artifacts; the convention for resolving the path will land in a future minor (currently a no-op routing target). Until then, use `target: "stdout"` for output that should reach the user immediately.
-
-## Composing with the default
-
-If you want your reporter to layer on top of the default rather than replace it, return an array:
-
-```typescript
-import { defaultReporter, type VitestAgentReporterFactory } from "@vitest-agent/reporter";
-
-export const myReporter: VitestAgentReporterFactory = (kit) => {
- const inner = defaultReporter(kit);
- const innerArr = Array.isArray(inner) ? inner : [inner];
- return [...innerArr, sarifReporter(kit)];
-};
-```
-
-## Wiring into the plugin
-
-```typescript
-// vitest.config.ts
-import { defineConfig } from "vitest/config";
-import { agentPlugin } from "@vitest-agent/plugin";
-import { myReporter } from "./my-reporter.js";
-
-export default defineConfig({
- plugins: [agentPlugin({ reporterFactory: myReporter })],
-});
-```
-
-## Anti-patterns
-
-- **Don't reach into Vitest's lifecycle from a reporter.** The plugin owns it. If you need a Vitest hook, you have outgrown this contract — fork the plugin instead.
-- **Don't return Promises from `render`.** The contract is sync. If you have async work, do it ahead of time and pass the resolved data into your factory closure.
-- **Don't use `stdOsc8` outside terminal targets.** OSC-8 escapes only render in capable terminals; `kit.stdOsc8` already gates this for you. Calling it from a `target: "github-summary"` reporter is harmless (it returns the bare label) but signals confused intent.
-
-## See also
-
-- `vitest://docs/api/advanced/reporters` — Vitest's own reporter API (different surface; informative for context)
-- `packages/reporter/src/default.ts` — The composition pattern the default reporter uses
-- `packages/sdk/src/contracts/reporter.ts` — Full type definitions for the contract

package/public/patterns/known-issues-and-caveats.md

@@ -1,52 +0,0 @@
-# Known Issues & Instrumentation Caveats
-
-## When to use
-
-A test run surfaced an error or oddity that looks like a vitest-agent bug.
-Check it against this list first — several are upstream Vitest behavior, an
-already-shipped fix, or a misconception, not something to investigate as a
-consumer-side problem.
-
-## `DataStoreError` on a UNIQUE collision — live, retry
-
-A concurrent agent registration (on `idempotency_key`) or two concurrent turn
-writes (on `(session_id, turn_no)`) can race the persistence layer's
-check-then-insert and surface a `DataStoreError` carrying
-`UNIQUE constraint failed`. It is not a consumer bug and not data corruption —
-retry the operation. The SELECT pre-check narrows but does not close the race.
-
-## `coverage/.tmp … ENOENT coverage-0.json` — inherent Vitest, not a bug
-
-Running Vitest in two processes at once (for example a CLI run alongside the
-`vitest-vscode` extension) makes them share Vitest's default
-`coverage.reportsDirectory`, and one process can delete the temp dir the other
-is writing. vitest-agent never sets `reportsDirectory`, so this is an upstream
-multi-process Vitest caveat. Give each concurrent process its own
-`coverage.reportsDirectory` (or serialize them).
-
-## `MaxPerformanceEntryBufferExceededWarning` — resolved, stop chasing it
-
-This `perf_hooks` warning on long runs was fixed in a shipped
-`@vitest-agent/reporter` release: React 19's development reconciler emits a
-`performance.measure()` per render, and the live renderer now drains Node's
-user-timing buffer after each render cycle. If you still see it, update
-`@vitest-agent/reporter`. Do not investigate it as a fault in your own repo.
-
-## Stale test counts — re-run, there is no warm cache
-
-Moving or adding test files does not require an MCP restart. Discovery is
-re-walked fresh on every Vitest run; the MCP serves counts from the database,
-which only updates when tests are re-run. Stale numbers mean the tests have not
-been re-run — not that a discovery cache is warm. Restarting the MCP would not
-refresh them.
-
-## A run that rebuilds `dist/` mid-run — expected
-
-A host project's Vitest `globalSetup` may call `AgentPlugin.runScript(...)`
-(for example `pnpm turbo run build:dev`), which can transiently tear down and
-rebuild `dist/` during the run. This is the host project's configuration, not a
-broken workspace.
-
-## See also
-
-- `vitest-agent://patterns/running-tests-via-mcp` — why subset runs "fail" coverage thresholds

package/public/patterns/operating-vitest-agent-as-an-agent.md

@@ -1,53 +0,0 @@
-# Operating vitest-agent as an Agent
-
-## When to use
-
-Read this first when you are an agent driving a project that uses
-`@vitest-agent/*`. It front-loads the handful of facts that otherwise cost
-trial-and-error, then points you at the deeper patterns.
-
-## The facts that save the most time
-
-1. **Run tests with `run_tests`, not Bash `vitest`.** `run_tests` persists
-   results, classifications, coverage, and history and fires the post-tool-use
-   hooks. Shelling out to `vitest` bypasses all of that.
-2. **`run_tests` has no `filter` parameter.** Scope with `project` (the Vitest
-   project name), `files` (globs), or `tags`. An unknown key like `filter` is
-   silently dropped, so the whole suite runs.
-3. **Subset runs "fail" coverage thresholds by design.** A single-file run
-   exiting with `ERROR: Coverage … does not meet global threshold` is expected
-   — global thresholds applied to partial coverage. There is no per-run
-   coverage toggle in `run_tests`; it inherits your `vitest.config`. For
-   isolated inspection use the CLI: `vitest run <file> --coverage.enabled=false`.
-4. **You cannot see stray `console.log` through `run_tests`** — it null-routes
-   Vitest's stdout. Console behavior is configured via the plugin's `console`
-   matrix (e.g. `console: { agent: "passthrough" }`), **not** environment
-   variables. To see intercepted output, run Vitest directly with
-   `--disableConsoleIntercept` (a native Vitest flag).
-5. **Session attribution is recovered for you.** The SessionStart hook writes
-   the `VITEST_AGENT_*` identity into the environment and the SDK recovers it —
-   you never set those vars by hand. The only behavioral knobs are
-   `VITEST_REPORTER_LOG_LEVEL`, `VITEST_REPORTER_LOG_FILE`, and `NO_COLOR`.
-6. **Stale counts mean tests were not re-run**, not a warm cache. Discovery
-   re-walks per Vitest run; the MCP serves counts from the database.
-7. **Some "leaks" are guardrail tests** that assert on their own output. Do not
-   silence output a test captures and `expect`s on.
-
-## Environment, briefly
-
-You do not configure vitest-agent through environment variables. The
-`VITEST_AGENT_*` vars (chat id, conversation id, agent ids, project dir,
-sidecar bin) are attribution plumbing written by the Claude Code plugin's
-SessionStart hook and recovered automatically. The only vars you might set for
-diagnostics are `VITEST_REPORTER_LOG_LEVEL` / `VITEST_REPORTER_LOG_FILE` (a
-diagnostic log file, separate from the console reporter) and `NO_COLOR`.
-
-## Where to go next
-
-| You want to… | Read |
-| --- | --- |
-| Scope a run, read the return shape, understand coverage-in-subset | `vitest-agent://patterns/running-tests-via-mcp` |
-| Silence noisy log/build output in tests | `vitest-agent://patterns/silencing-leaking-output-in-tests` |
-| Tell tooling noise apart from real failures | `vitest-agent://patterns/known-issues-and-caveats` |
-| Read the full console-mode matrix (human prose) | <https://vitest-agent.dev/guide/console-modes> |
-| The human-facing version of this page | <https://vitest-agent.dev/guide/operating-as-an-agent> |

package/public/patterns/running-tests-via-mcp.md

@@ -1,58 +0,0 @@
-# Running Tests via the MCP `run_tests` Tool
-
-## When to use
-
-You want to execute the Vitest suite (or a subset) from an agent. Always prefer `run_tests` over shelling out to `vitest` — it persists results, classifications, coverage, and history to the project database and drives the post-tool-use hooks. Re-running `vitest` over Bash bypasses all of that.
-
-## Scoping a run — there is no `filter` parameter
-
-`run_tests` accepts exactly these inputs:
-
-| Field | Type | Default | Scopes by |
-| --- | --- | --- | --- |
-| `files` | `string[]` | `[]` | Vitest file patterns: exact paths or globs |
-| `project` | `string` | unset | The Vitest **project name** from your config |
-| `tags` | `{ all?: string[]; any?: string[]; none?: string[] }` | unset | Vitest tag expression |
-| `passWithNoTests` | `boolean` | config value | Per-call override of `test.passWithNoTests` |
-| `timeout` | `number` (seconds) | `120` | Per-call run timeout |
-
-There is **no** `filter` field. Passing one (`run_tests({ filter: "@my/pkg" })`) is silently dropped — the call then runs with no filters, so the **entire** suite executes. To scope to one package, pass its Vitest project name as `project`; to scope to one file, pass it in `files`.
-
-`project` matches the project **name** defined in `vitest.config.ts`, not the npm package name. They often differ — check your config for the actual project name.
-
-`tags` sub-filters AND together (with each other and with `project`/`files`): `all` → `"a and b"`, `any` → `"(a or b)"`, `none` → `"not a and not b"`.
-
-## Return shape
-
-`run_tests` returns one of four variants — discriminate on `kind`:
-
-| `kind` | Fields | Meaning |
-| --- | --- | --- |
-| `"ok"` | `report`, `classifications` (map of test full-name → `stable`/`new-failure`/`persistent`/`flaky`/`recovered`), optional `project` | The run completed |
-| `"no-match"` | `filter` (the resolved `project`/`files`/`tags`/`resolvedExpression`) | A filter was supplied but matched zero tests |
-| `"timeout"` | `timeoutSeconds` | Exceeded the timeout |
-| `"error"` | `message` | The run errored |
-
-A `no-match` is filter-driven: it fires when you supplied a filter and zero tests matched. Treat it as a finding (typo in `project`/`files`?) rather than a pass.
-
-## Coverage on subset runs reads as a failure — by design
-
-A single-file or single-project run will commonly exit non-zero with:
-
-```text
-ERROR: Coverage for lines (59.91%) does not meet global threshold (70%)
-```
-
-This is expected: your global coverage thresholds are applied to a partial run, so partial coverage "fails" them. It is not a real test failure.
-
-`run_tests` has **no per-run coverage toggle** — it deliberately inherits your `vitest.config` `coverage.enabled` (forcing it off here used to override intentional "coverage on by default" setups). For clean isolated inspection, drop to the CLI:
-
-```bash
-vitest run path/to/one.test.ts --coverage.enabled=false
-```
-
-## See also
-
-- `vitest-agent://patterns/operating-vitest-agent-as-an-agent` — the orientation index
-- `vitest-agent://patterns/known-issues-and-caveats` — coverage-dir races and other instrumentation caveats
-- `vitest://docs/config/index` — Vitest's native config reference

package/public/patterns/silencing-leaking-output-in-tests.md

@@ -1,91 +0,0 @@
-# Silencing Leaking Log / Build Output in Tests
-
-## When to use
-
-A test run is polluted with stray log lines, build-tool banners, or framework
-diagnostics that drown the signal. The fix differs per source — identify the
-source first, then apply the matching technique.
-
-## Guardrail: do not silence output a test asserts on
-
-Before silencing anything, confirm the test does not capture and `expect` on
-the output. Some tests deliberately spy on `process.stdout.write` /
-`process.stderr.write` (or `console.*`) and assert on `.mock.calls` to verify
-what a formatter emits. Silencing those breaks the assertion. If you see a
-`vi.spyOn(process.stdout, "write")` whose `.mock.calls` are asserted, that
-output is the test subject — leave it alone.
-
-## Decision tree
-
-| Source (what the noise looks like) | Technique |
-| --- | --- |
-| Effect default logger (`timestamp=… level=INFO message=…`) | Provide a silent logger layer |
-| Plain `console.log` / `console.warn` / `console.error` | Spy + mock the method |
-| rsbuild (`info build started…`, file-size table) | Set `@rsbuild/core` logger level to silent |
-| tsdown / rolldown (`ℹ entry:`, `✔ Build complete`) | Pass `logLevel: "silent"` to the build |
-| API Extractor (`(ae-missing-release-tag)` to stderr) | Pass an `onMessage` handler that marks messages handled |
-
-## Effect default logger
-
-Provide a silent logger at the run/layer boundary. This mirrors how the SDK's
-own `LoggerLive` builds its silent variant (`packages/sdk/src/layers/LoggerLive.ts`):
-
-```typescript
-import { Effect, Logger } from "effect";
-
-const silent = Logger.replace(Logger.defaultLogger, Logger.none);
-
-await Effect.runPromise(program.pipe(Effect.provide(silent)));
-```
-
-`Logger.minimumLogLevel(LogLevel.None)` is an equivalent gate.
-
-## Plain `console.*`
-
-```typescript
-import { beforeEach, vi } from "vitest";
-
-beforeEach(() => {
- vi.spyOn(console, "warn").mockImplementation(() => {});
- vi.spyOn(console, "error").mockImplementation(() => {});
-});
-```
-
-## rsbuild reporter
-
-rsbuild writes through its own `logger` singleton, **not** `console.*`, so
-console mocks miss it. Set the level and restore it:
-
-```typescript
-import { logger } from "@rsbuild/core";
-
-const prev = logger.level;
-logger.level = "silent";
-try {
- await build();
-} finally {
- logger.level = prev;
-}
-```
-
-## tsdown / rolldown
-
-Pass `logLevel: "silent"` to the build call (or inject a no-op output writer).
-
-## API Extractor
-
-Mark diagnostics handled so they are not printed — this is the production quiet
-path:
-
-```typescript
-extractorResult = Extractor.invoke(config, {
- messageCallback: (message) => {
-  message.handled = true;
- },
-});
-```
-
-## See also
-
-- `vitest-agent://patterns/known-issues-and-caveats` — distinguishing tooling noise from real failures
-- `vitest://docs/api/vi` — the `vi.spyOn` / mock API