@vitest-agent/mcp 1.1.0 → 1.2.0

package/vendor/vitest-docs/manifest.json

@@ -1,1691 +0,0 @@
-{
-	"tag": "v4.1.5",
-	"commitSha": "e399846850fedf10b8228cbe46a419628998acd9",
-	"capturedAt": "2026-05-05T18:49:19.433Z",
-	"source": "https://github.com/vitest-dev/vitest",
-	"pages": [
-		{
-			"path": "api/advanced/artifacts",
-			"title": "Test artifacts (advanced)",
-			"description": "Use when building Vitest extensions that record structured per-test data — `recordArtifact(task, artifact)`, TestArtifactBase, TestAttachment, attachment serialization to attachmentsDir. Internal/library-author API; users wanting test notes should use test annotations instead.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.8
-			}
-		},
-		{
-			"path": "api/advanced/metadata",
-			"title": "Task metadata (advanced)",
-			"description": "Use when passing data from inside tests to a custom reporter — `task.meta` property on test and suite tasks, populated in beforeAll / afterAll / test context, read in onTestCaseResult and onTestRunEnd. One-way (test → reporter); reporter-side mutations are not visible in tests.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.8
-			}
-		},
-		{
-			"path": "api/advanced/plugin",
-			"title": "Plugin API (advanced)",
-			"description": "Use when authoring a Vite plugin that needs Vitest-specific behavior — the `configureVitest(context: VitestPluginContext)` hook (since Vitest 3.1), VitestPluginContext shape, and the vite-and-vitest dual-plugin pattern. Library-author API; not for typical app config.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.8
-			}
-		},
-		{
-			"path": "api/advanced/reporters",
-			"title": "Reporter API (advanced)",
-			"description": "Use when implementing a custom reporter — full Reporter lifecycle hooks (onInit, onTestModuleStart, onTestCaseReady, onTestCaseResult, onCoverage, onTestRunEnd, etc.) with their TestModule / TestSuite / TestCase parameters. Extend BaseReporter to override selectively.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.8
-			}
-		},
-		{
-			"path": "api/advanced/runner",
-			"title": "VitestRunner (advanced)",
-			"description": "Use when implementing a custom test runner via the `runner` config option — VitestRunner interface (onBeforeCollect, onCollected, onBeforeRunTask, onBeforeTryTask, onAfterRunTask, onAfterRunFiles, onCancel), Test/Suite/File task shapes, runtime-task vs main-thread-TestCase distinction.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.8
-			}
-		},
-		{
-			"path": "api/advanced/test-case",
-			"title": "TestCase (advanced)",
-			"description": "Use when introspecting a single test in a custom reporter — TestCase.project / module / name / fullName / location / parent / state / result / annotations / artifacts / meta. Main-thread API; for in-worker runtime tasks see the Runner API.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.8
-			}
-		},
-		{
-			"path": "api/advanced/test-collection",
-			"title": "TestCollection (advanced)",
-			"description": "Use when iterating top-level suites and tests inside a TestSuite or TestModule — collection.size / at / array / values / allTests / allSuites returning iterators (spread `[...iter]` if you need an array). Top-level only — does not flatten nested suites unless you use allTests/allSuites.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.8
-			}
-		},
-		{
-			"path": "api/advanced/test-module",
-			"title": "TestModule (advanced)",
-			"description": "Use when inspecting a single test file in a custom reporter — TestModule.moduleId (absolute unix path or virtual id) / relativeModuleId, plus all inherited TestSuite methods (children, errors, diagnostic, state). One TestModule per file per project.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.8
-			}
-		},
-		{
-			"path": "api/advanced/test-project",
-			"title": "TestProject (advanced)",
-			"description": "Use when working with the Node.js TestProject API — project.name / config / vite / globalConfig / vitest / serializedConfig / createSpecification / globTestFiles / collectTests. For declaring projects in user config see /guide/projects.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.8
-			}
-		},
-		{
-			"path": "api/advanced/test-specification",
-			"title": "TestSpecification (advanced)",
-			"description": "Use when constructing a test-run programmatically via `project.createSpecification` — module id, optional testLines / testNamePattern / testIds / testTagsFilter filters, taskId / project / pool fields. Specification does not auto-resolve files.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.8
-			}
-		},
-		{
-			"path": "api/advanced/test-suite",
-			"title": "TestSuite (advanced)",
-			"description": "Use when inspecting a suite in a custom reporter — TestSuite.project / module / name / fullName / location / parent / children (TestCollection), errors, diagnostic, state. Inherited by TestModule.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.8
-			}
-		},
-		{
-			"path": "api/advanced/vitest",
-			"title": "Vitest class (advanced)",
-			"description": "Use when driving Vitest from a Node.js script — Vitest.mode / config / projects / vite / state / cancelCurrentRun / start / close / globTestSpecifications / getModuleSpecifications / invalidateFile / onFilterWatchedSpecification. Documents v4 removals (server, getProjectsByTestFile, listFile, etc.).",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.8
-			}
-		},
-		{
-			"path": "api/assert",
-			"title": "assert",
-			"description": "Use when reaching for chai's `assert.*` API — assert.equal / deepEqual / strictEqual / isOk / isTrue / isNotNull / fail, narrow type guards via assertion functions. Reexported from chai for invariant-style checks alongside or instead of expect.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.9
-			}
-		},
-		{
-			"path": "api/assert-type",
-			"title": "assertType",
-			"description": "Use when type-checking a single expression under `--typecheck` — `assertType<T>(value)` shorthand for expectTypeOf. Pair with `@ts-expect-error` for negative cases. Runtime no-op; requires --typecheck flag.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.9
-			}
-		},
-		{
-			"path": "api/browser/assertions",
-			"title": "DOM assertions (browser API)",
-			"description": "Use when asserting on the DOM in browser-mode tests — `expect.element(locator)` matchers: toBeVisible / toBeInTheDocument / toHaveTextContent / toHaveClass / toBeEnabled / toBeChecked / toHaveAttribute / toHaveValue, all with built-in retry. Forked from @testing-library/jest-dom.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "api/browser/commands",
-			"title": "Server commands (browser API)",
-			"description": "Use when calling server-side functions from a browser test — built-in readFile / writeFile / removeFile (governed by server.fs.allow and api.allowWrite), defining custom commands via the `browser.commands` config option. Paths resolve relative to project root since 3.2.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "api/browser/context",
-			"title": "vitest/browser exports (browser API)",
-			"description": "Use when importing browser-mode primitives from `vitest/browser` — `page` (locator root), `server` (commands, config), `userEvent` (interactivity), `cdp()` (Chrome DevTools Protocol session). Entry-point API surface.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "api/browser/interactivity",
-			"title": "userEvent (browser API)",
-			"description": "Use when simulating user interactions in browser tests — userEvent.click / dblClick / tripleClick / type / keyboard / hover / fill / selectOptions / clear / upload / drag, userEvent.setup for stateful sessions. Backed by Playwright/WebDriver (real input events), not faked DOM events.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "api/browser/locators",
-			"title": "page locators (browser API)",
-			"description": "Use when querying DOM in browser tests — page.getByRole / getByText / getByLabelText / getByTestId / getByPlaceholder / getByTitle / getByAltText, locator chaining via .filter / .nth / .first / .last / .and / .or, .element / .query / .all escape hatches. Backed by Playwright's Ivya.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "api/browser/react",
-			"title": "vitest-browser-react (browser API)",
-			"description": "Use when rendering React components in browser-mode tests — `render(<Component />)` returns a screen with locators that interact via userEvent and retry under expect.element. Community package; recommended over @testing-library/react for browser mode.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "api/browser/svelte",
-			"title": "vitest-browser-svelte (browser API)",
-			"description": "Use when rendering Svelte components in browser-mode tests — `render(Component, props)` returns a screen with locators integrated with userEvent and expect.element retries. Community package; alternative to @testing-library/svelte for browser mode.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "api/browser/vue",
-			"title": "vitest-browser-vue (browser API)",
-			"description": "Use when rendering Vue components in browser-mode tests — `render(Component, { props })` returns a screen with locator-based queries that interact via userEvent and retry under expect.element. Community package; alternative to @testing-library/vue for browser mode.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "api/describe",
-			"title": "describe",
-			"description": "Use when organizing tests with `describe` (alias `suite`) — nested suites, describe.each parametrization, describe.skip / only / todo / sequential / concurrent / shuffle, hierarchical fullName composition for `> ` separated test paths.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.9
-			}
-		},
-		{
-			"path": "api/expect",
-			"title": "expect",
-			"description": "Use when writing assertions with `expect` — Jest-style matchers (`toBe`, `toEqual`, `toThrow`, `toHaveBeenCalled`, `toMatchSnapshot`, etc.), chai-style chains, asymmetric matchers (`expect.anything`, `expect.stringContaining`), `expect.poll` for async retries, `expect.extend` for custom matchers.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.9
-			}
-		},
-		{
-			"path": "api/expect-typeof",
-			"title": "expectTypeOf",
-			"description": "Use when writing type-level assertions for the `--typecheck` flag — toEqualTypeOf, toExtend (replaces deprecated toMatchTypeOf), toMatchObjectType, parameters / returns / instance / constructorParameters inspection. Runtime no-op.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.9
-			}
-		},
-		{
-			"path": "api/hooks",
-			"title": "Lifecycle hooks",
-			"description": "Use when adding setup or teardown — beforeEach / afterEach / beforeAll / afterAll, hook timeouts (configurable via hookTimeout), the return-cleanup-function pattern, onTestFinished / onTestFailed handlers, sequence.hooks ordering. Skipped when running --typecheck.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.9
-			}
-		},
-		{
-			"path": "api/mock",
-			"title": "MockInstance",
-			"description": "Use when inspecting or controlling the MockInstance returned by `vi.fn` and `vi.spyOn` — mock.calls / results / instances / contexts, mockReturnValue / mockResolvedValue / mockRejectedValue (plus *Once variants), mockImplementation, mockReset / mockClear / mockRestore, and class-mock caveats with `vi.fn(class {})`.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.9
-			}
-		},
-		{
-			"path": "api/test",
-			"title": "test",
-			"description": "Use when defining a test with `test` or `it` — modifiers (skip, only, todo, concurrent, fails, retry), `test.each` / `test.for` parametrization, `test.extend` fixtures, options-object form, the test-name-from-function shorthand.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.9
-			}
-		},
-		{
-			"path": "api/vi",
-			"title": "vi",
-			"description": "Use when reaching for `vi.*` helpers — `vi.mock` / `vi.hoisted` / `vi.importActual` for module mocking, `vi.fn` / `vi.spyOn` for function mocking, `vi.useFakeTimers` / `vi.advanceTimersByTime` for timers, `vi.stubEnv` / `vi.stubGlobal` for env and global stubbing.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.9
-			}
-		},
-		{
-			"path": "config/alias",
-			"title": "config.alias",
-			"description": "Use when configuring `alias` — Type `Record | Array`. Define custom aliases when running inside tests. They will be merged with aliases from `resolve.alias`.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/allowonly",
-			"title": "config.allowOnly",
-			"description": "Use when configuring `allowOnly` — Type `boolean`, default `!process.env.CI`, CLI `--allowOnly`. By default, Vitest does not permit tests marked with the [`only`](/api/test#test-only) flag in Continuous Integration (CI) environments. Conversely, in local development environments, Vitest allows these tests to run.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/api",
-			"title": "config.api",
-			"description": "Use when configuring `api` — Type `boolean | number | object`, default `false`, CLI `--api`. Listen to port and serve API for [the UI](/guide/ui) or [browser server](/guide/browser/). When set to `true`, the default port is `51204`.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/attachmentsdir",
-			"title": "config.attachmentsDir",
-			"description": "Use when configuring `attachmentsDir` — Type `string`, default `'.vitest-attachments'`. Directory path for storing attachments created by [`context.annotate`](/guide/test-context#annotate) relative to the project root.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/bail",
-			"title": "config.bail",
-			"description": "Use when configuring `bail` — Type `number`, default `0`, CLI `--bail=`. Stop test execution when given number of tests have failed.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/benchmark",
-			"title": "config.benchmark",
-			"description": "Use when configuring `benchmark` — Type `{ include?, exclude?, ... }`, default `['**/*.{bench,benchmark}.?(c|m)[jt]s?(x)']`. Options used when running `vitest bench`.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/browser/api",
-			"title": "config.browser.api",
-			"description": "Use when configuring `browser.api` — Type `number | object`, default port `63315`, CLI `--browser.api=63315`. Vite server that serves browser-mode test code. Independent of `test.api` (the Node-mode API server); the default port avoids dev-server conflicts.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "config/browser/commands",
-			"title": "config.browser.commands",
-			"description": "Use when configuring `browser.commands` — Type `Record`, default `{ readFile, writeFile, ... }`. Custom [commands](/api/browser/commands) that can be imported during browser tests from `vitest/browser`.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "config/browser/connecttimeout",
-			"title": "config.browser.connectTimeout",
-			"description": "Use when configuring `browser.connectTimeout` — Type `number`, default `60_000`. The timeout in milliseconds. If connection to the browser takes longer, the test suite will fail.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "config/browser/detailspanelposition",
-			"title": "config.browser.detailsPanelPosition",
-			"description": "Use when configuring `browser.detailsPanelPosition` — Type `'right' | 'bottom'`, default `'right'`, CLI `--browser.detailsPanelPosition=bottom`. Controls the default position of the details panel in the Vitest UI when running browser tests.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "config/browser/enabled",
-			"title": "config.browser.enabled",
-			"description": "Use when configuring `browser.enabled` — Type `boolean`, default `false`, CLI `--browser`. Enabling this flag makes Vitest run all tests in a [browser](/guide/browser/) by default. If you are configuring other browser options via the CLI, you can use `--browser.enabled` alongside them instead of `--browser`:",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "config/browser/expect",
-			"title": "config.browser.expect",
-			"description": "Use when configuring `browser.expect` — Type `ExpectOptions`. Default options for browser-mode `expect.element` matchers (timeout, interval). Browser-mode counterpart of the Node-mode `test.expect` option.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "config/browser/headless",
-			"title": "config.browser.headless",
-			"description": "Use when configuring `browser.headless` — Type `boolean`, default `process.env.CI`, CLI `--browser.headless`. Run the browser in a `headless` mode. If you are running Vitest in CI, it will be enabled by default.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "config/browser/instances",
-			"title": "config.browser.instances",
-			"description": "Use when configuring `browser.instances` — Type `BrowserConfig`, default `[]`. Defines multiple browser setups. Every config has to have at least a `browser` field.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "config/browser/isolate",
-			"title": "config.browser.isolate",
-			"description": "Use when configuring `browser.isolate` — Type `boolean`, default the same as [`--isolate`](/config/isolate), CLI `--browser.isolate`. Run every test in a separate iframe.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "config/browser/locators",
-			"title": "config.browser.locators",
-			"description": "Use when configuring `browser.locators` — Type `string`, default `data-testid`. Options for built-in [browser locators](/api/browser/locators).",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "config/browser/orchestratorscripts",
-			"title": "config.browser.orchestratorScripts",
-			"description": "Use when configuring `browser.orchestratorScripts` — Type `BrowserScript[]`, default `[]`. Custom scripts that should be injected into the orchestrator HTML before test iframes are initiated. This HTML document only sets up iframes and doesn't actually import your code.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "config/browser/playwright",
-			"title": "Configuring Playwright",
-			"description": "Use when configuring `Configuring Playwright` — Type `boolean | string`, default no timeout. To run tests using playwright, you need to install the [`@vitest/browser-playwright`](https://npmx.dev/package/@vitest/browser-playwright) npm package and specify its `playwright` export in the `test.browser.provider`...",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "config/browser/preview",
-			"title": "Configuring Preview",
-			"description": "Use when configuring `Configuring Preview`. The `preview` provider's main functionality is to show tests in a real browser environment. However, it does not support advanced browser automation features like multiple browser instances or headless mode. For more ...",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "config/browser/provider",
-			"title": "config.browser.provider",
-			"description": "Use when configuring `browser.provider` — Type `BrowserProviderOption`. The return value of the provider factory. You can import the factory from `@vitest/browser-` or make your own provider:",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "config/browser/screenshotdirectory",
-			"title": "config.browser.screenshotDirectory",
-			"description": "Use when configuring `browser.screenshotDirectory` — Type `string`, default `__screenshots__` in the test file directory. Path to the screenshots directory relative to the `root`.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "config/browser/screenshotfailures",
-			"title": "config.browser.screenshotFailures",
-			"description": "Use when configuring `browser.screenshotFailures` — Type `boolean`, default `!browser.ui`. Should Vitest take screenshots if the test fails.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "config/browser/testerhtmlpath",
-			"title": "config.browser.testerHtmlPath",
-			"description": "Use when configuring `browser.testerHtmlPath` — Type `string`. A path to the HTML entry point. Can be relative to the root of the project. This file will be processed with [`transformIndexHtml`](https://vite.dev/guide/api-plugin#transformindexhtml) hook.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "config/browser/trace",
-			"title": "config.browser.trace",
-			"description": "Use when configuring `browser.trace` — Type `'on' | 'off' | 'on-first-retry' | 'on-all-retries' | 'retain-on-failure' | object`, default `'off'`, CLI `--browser.trace=on`. Capture a trace of your browser test runs. You can preview traces with [Playwright Trace Viewer](https://trace.playwright.dev/).",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "config/browser/trackunhandlederrors",
-			"title": "config.browser.trackUnhandledErrors",
-			"description": "Use when configuring `browser.trackUnhandledErrors` — Type `boolean`, default `true`. Enables tracking uncaught errors and exceptions so they can be reported by Vitest.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "config/browser/ui",
-			"title": "config.browser.ui",
-			"description": "Use when configuring `browser.ui` — Type `boolean`, default `!isCI`, CLI `--browser.ui=false`. Should Vitest UI be injected into the page. By default, injects UI iframe during development.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "config/browser/viewport",
-			"title": "config.browser.viewport",
-			"description": "Use when configuring `browser.viewport` — Type `{ width, height }`, default `414x896`. Default iframe's viewport.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "config/browser/webdriverio",
-			"title": "Configuring WebdriverIO",
-			"description": "Use when configuring `Configuring WebdriverIO`. If you do not already use WebdriverIO in your project, we recommend starting with [Playwright](/config/browser/playwright) as it is easier to configure and has more flexible API.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "config/cache",
-			"title": "config.cache",
-			"description": "Use when configuring `cache` — Type `false`, CLI `--no-cache`. Use this option if you want to disable the cache feature. At the moment Vitest stores cache for test results to run the longer and failed tests first.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/chaiconfig",
-			"title": "config.chaiConfig",
-			"description": "Use when configuring `chaiConfig` — Type `{ includeStack?, showDiff?, truncateThreshold? }`, default `{ includeStack: false, showDiff: true, truncateThreshold: 40 }`. Equivalent to [Chai config](https://github.com/chaijs/chai/blob/4.x.x/lib/chai/config.js).",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/clearmocks",
-			"title": "config.clearMocks",
-			"description": "Use when configuring `clearMocks` — Type `boolean`, default `false`. Should Vitest automatically call [`vi.clearAllMocks()`](/api/vi#vi-clearallmocks) before each test.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/coverage",
-			"title": "config.coverage",
-			"description": "Use when configuring `coverage` — Type `'v8' | 'istanbul' | 'custom'`, default `'v8'`, CLI `--coverage.provider=`. You can use [`v8`](/guide/coverage.html#v8-provider), [`istanbul`](/guide/coverage.html#istanbul-provider) or [a custom coverage solution](/guide/coverage#custom-coverage-provider) for coverage collection.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/css",
-			"title": "config.css",
-			"description": "Use when configuring `css` — Type `boolean | { include?, exclude?, modules? }`, default `[]`. Configure if CSS should be processed. When excluded, CSS files will be replaced with empty strings to bypass the subsequent processing. CSS Modules will return a proxy to not affect runtime.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/dangerouslyignoreunhandlederrors",
-			"title": "config.dangerouslyIgnoreUnhandledErrors",
-			"description": "Use when configuring `dangerouslyIgnoreUnhandledErrors` — Type `boolean`, default `false`, CLI `--dangerouslyIgnoreUnhandledErrors`. Suppresses test-run failure on uncaught errors and unhandled promise rejections. Escape hatch for legacy code; rarely correct.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/deps",
-			"title": "config.deps",
-			"description": "Use when configuring `deps` — Type `{ optimizer?, ... }`, default `false`. Handling for dependencies resolution.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/detectasyncleaks",
-			"title": "config.detectAsyncLeaks",
-			"description": "Use when configuring `detectAsyncLeaks` — Type `boolean`, default `false`, CLI `--detectAsyncLeaks`. Enabling this option will make your tests run much slower. Use only when debugging or developing tests.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/diff",
-			"title": "config.diff",
-			"description": "Use when configuring `diff` — Type `string`, default `true`, CLI `--diff=`. `DiffOptions` object or a path to a module which exports `DiffOptions`. Useful if you want to customize diff display.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/dir",
-			"title": "config.dir",
-			"description": "Use when configuring `dir` — Type `string`, default same as `root`, CLI `--dir=`. Base directory to scan for the test files. You can specify this option to speed up test discovery if your root covers the whole project",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/disableconsoleintercept",
-			"title": "config.disableConsoleIntercept",
-			"description": "Use when configuring `disableConsoleIntercept` — Type `boolean`, default `false`, CLI `--disableConsoleIntercept`. By default, Vitest automatically intercepts console logging during tests for extra formatting of test file, test title, etc.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/env",
-			"title": "config.env",
-			"description": "Use when configuring `env` — Type `Partial`. Environment variables available on `process.env` and `import.meta.env` during tests. These variables will not be available in the main process (in `globalSetup`, for example).",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/environment",
-			"title": "config.environment",
-			"description": "Use when configuring `environment` — Type `'node' | 'jsdom' | 'happy-dom' | 'edge-runtime' | string`, default `'node'`, CLI `--environment=`. The environment that will be used for testing. The default environment in Vitest",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/environmentoptions",
-			"title": "config.environmentOptions",
-			"description": "Use when configuring `environmentOptions` — Type `Record`, default `{}`. These options are passed to the setup method of the current [environment](/config/environment). By default, you can configure options only for `jsdom` and `happyDOM` when you use them as your test environment.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/exclude",
-			"title": "config.exclude",
-			"description": "Use when configuring `exclude` — Type `string[]`, default `['**/node_modules/**', '**/.git/**']`, CLI `--exclude`. Glob patterns of files excluded from test discovery, resolved relative to `root`. Pair with `include` to scope discovery; tinyglobby is the matcher.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/execargv",
-			"title": "config.execArgv",
-			"description": "Use when configuring `execArgv` — Type `string[]`, default `[]`. Pass additional arguments to `node` in the runner worker. See [Command-line API | Node.js](https://nodejs.org/docs/latest/api/cli.html) for more information.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/expandsnapshotdiff",
-			"title": "config.expandSnapshotDiff",
-			"description": "Use when configuring `expandSnapshotDiff` — Type `boolean`, default `false`, CLI `--expandSnapshotDiff`. Show full diff when snapshot fails instead of a patch.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/expect",
-			"title": "config.expect",
-			"description": "Use when configuring `expect` — Type `ExpectOptions`, default `false`. The same as calling [`expect.hasAssertions()`](/api/expect#expect-hasassertions) at the start of every test. This makes sure that no test will pass accidentally.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/experimental",
-			"title": "config.experimental",
-			"description": "Use when configuring `experimental` — Type `boolean`, default `false`. Please leave feedback regarding this feature in a [GitHub Discussion](https://github.com/vitest-dev/vitest/discussions/9221).",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/faketimers",
-			"title": "config.fakeTimers",
-			"description": "Use when configuring `fakeTimers` — Type `FakeTimerInstallOpts`, default `Date.now()`. Options that Vitest will pass down to [`@sinon/fake-timers`](https://npmx.dev/package/@sinonjs/fake-timers) when using [`vi.useFakeTimers()`](/api/vi#vi-usefaketimers).",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/fileparallelism",
-			"title": "config.fileParallelism",
-			"description": "Use when configuring `fileParallelism` — Type `boolean`, default `true`, CLI `--no-file-parallelism`. Should all test files run in parallel. Setting this to `false` will override `maxWorkers` option to `1`.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/forcereruntriggers",
-			"title": "config.forceRerunTriggers",
-			"description": "Use when configuring `forceRerunTriggers` — Type `string[]`, default `['**/package.json/**', '**/vitest.config.*/**', '**/vite.config.*/**']`. Glob pattern of file paths that will trigger the whole suite rerun. When paired with the `--changed` argument will run the whole test suite if the trigger is found in the git diff.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/globals",
-			"title": "config.globals",
-			"description": "Use when configuring `globals` — Type `boolean`, default `false`, CLI `--globals`. By default, `vitest` does not provide global APIs for explicitness. If you prefer to use the APIs globally like Jest, you can pass the `--globals` option to CLI or add `globals: true` in the config.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/globalsetup",
-			"title": "config.globalSetup",
-			"description": "Use when configuring `globalSetup` — Type `string | string[]`. Path to global setup files relative to project [root](/config/root).",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/hideskippedtests",
-			"title": "config.hideSkippedTests",
-			"description": "Use when configuring `hideSkippedTests` — Type `boolean`, default `false`, CLI `--hideSkippedTests`. Hide logs for skipped tests",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/hooktimeout",
-			"title": "config.hookTimeout",
-			"description": "Use when configuring `hookTimeout` — Type `number`, default `10_000` in Node.js, `30_000` if `browser.enabled` is `true`, CLI `--hook-timeout=10000`. Default timeout of a hook in milliseconds. Use `0` to disable timeout completely.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/include",
-			"title": "config.include",
-			"description": "Use when configuring `include` — Type `string[]`, default `['**/*.{test,spec}.?(c|m)[jt]s?(x)']`, CLI `vitest [...include]`. Glob patterns matching test files, resolved relative to `root`. Pair with `includeSource` for in-source tests; tinyglobby is the matcher.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/include-source",
-			"title": "config.includeSource",
-			"description": "Use when configuring `includeSource` — Type `string[]`, default `[]`. A list of [glob patterns](https://superchupu.dev/tinyglobby/comparison) that match your [in-source test files](/guide/in-source). These patterns are resolved relative to the [`root`](/config/root) ([`process.cwd()`](h...",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/includetasklocation",
-			"title": "config.includeTaskLocation",
-			"description": "Use when configuring `includeTaskLocation` — Type `boolean`, default `false`. Should `location` property be included when Vitest API receives tasks in [reporters](/config/reporters). If you have a lot of tests, this might cause a small performance regression.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/index",
-			"title": "Configuring Vitest",
-			"description": "Use when configuring `Configuring Vitest`. If you are using Vite and have a `vite.config` file, Vitest will read it to match with the plugins and setup as your Vite app. If you want to have a different configuration for testing or your main app doesn't rely on...",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/isolate",
-			"title": "config.isolate",
-			"description": "Use when configuring `isolate` — Type `boolean`, default `true`, CLI `--no-isolate`. Run tests in an isolated environment. This option has no effect on `vmThreads` and `vmForks` pools.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/logheapusage",
-			"title": "config.logHeapUsage",
-			"description": "Use when configuring `logHeapUsage` — Type `boolean`, default `false`, CLI `--logHeapUsage`. Show heap usage after each test. Useful for debugging memory leaks.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/maxconcurrency",
-			"title": "config.maxConcurrency",
-			"description": "Use when configuring `maxConcurrency` — Type `number`, default `5`, CLI `--max-concurrency=10`. The maximum number of tests and hooks that can run at the same time when using `test.concurrent` or `describe.concurrent`.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/maxworkers",
-			"title": "config.maxWorkers",
-			"description": "Use when configuring `maxWorkers` — Type `number | string`. - if [`watch`](/config/watch) is disabled, uses all available parallelism",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/mockreset",
-			"title": "config.mockReset",
-			"description": "Use when configuring `mockReset` — Type `boolean`, default `false`. Should Vitest automatically call [`vi.resetAllMocks()`](/api/vi#vi-resetallmocks) before each test.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/mode",
-			"title": "config.mode",
-			"description": "Use when configuring `mode` — Type `string`, default `'test'`, CLI `--mode=staging`. Overrides Vite mode.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/name",
-			"title": "config.name",
-			"description": "Use when configuring `name`. Assign a custom name to the test project or Vitest process. The name will be visible in the CLI and UI, and available in the Node.js API via [`project.name`](/api/advanced/test-project#name).",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/onconsolelog",
-			"title": "config.onConsoleLog",
-			"description": "Use when configuring `onConsoleLog`. Custom handler for `console` methods in tests. If you return `false`, Vitest will not print the log to the console. Note that Vitest ignores all other falsy values.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/onstacktrace",
-			"title": "config.onStackTrace",
-			"description": "Use when configuring `onStackTrace` — Type `(error: Error, frame: ParsedStack) => boolean | void`. Apply a filtering function to each frame of each stack trace when handling errors. This does not apply to stack traces printed by [`printConsoleTrace`](/config/printconsoletrace#printconsoletrace). The first argument,...",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/onunhandlederror",
-			"title": "config.onUnhandledError",
-			"description": "Use when configuring `onUnhandledError`. A custom callback for filtering unhandled errors that should not be reported. When an error is filtered out, it no longer affects the result of the test run.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/open",
-			"title": "config.open",
-			"description": "Use when configuring `open` — Type `boolean`, default `!process.env.CI`, CLI `--open`. Open Vitest UI automatically if it's [enabled](/config/ui).",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/outputfile",
-			"title": "config.outputFile",
-			"description": "Use when configuring `outputFile` — Type `string | Record`, CLI `--outputFile=`. Write test results to a file when the `--reporter=json`, `--reporter=html` or `--reporter=junit` option is also specified.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/passwithnotests",
-			"title": "config.passWithNoTests",
-			"description": "Use when configuring `passWithNoTests` — Type `boolean`, default `false`, CLI `--passWithNoTests`. Vitest will not fail, if no tests will be found.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/pool",
-			"title": "config.pool",
-			"description": "Use when configuring `pool` — Type `'threads' | 'forks' | 'vmThreads' | 'vmForks'`, default `'forks'`, CLI `--pool=threads`. Pool used to run tests in.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/printconsoletrace",
-			"title": "config.printConsoleTrace",
-			"description": "Use when configuring `printConsoleTrace` — Type `boolean`, default `false`. Always print console traces when calling any `console` method. This is useful for debugging.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/projects",
-			"title": "config.projects",
-			"description": "Use when configuring `projects` — Type `TestProjectConfiguration[]`, default `[]`. An array of [projects](/guide/projects).",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/provide",
-			"title": "config.provide",
-			"description": "Use when configuring `provide` — Type `Partial`. Define values that can be accessed inside your tests using `inject` method.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/reporters",
-			"title": "config.reporters",
-			"description": "Use when configuring `reporters` — default [`'default'`](/guide/reporters#default-reporter) (or [['default'](/guide/reporters#default-reporter), ['github-actions'](/guide/reporters#github-actions-reporter)] when `process.env.GITHUB_ACTIONS === 'true'`). - `--reporter=tap` for a single reporter",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/resolvesnapshotpath",
-			"title": "config.resolveSnapshotPath",
-			"description": "Use when configuring `resolveSnapshotPath` — Type `(testPath: string, snapExtension: string, context: { config: SerializedConfig }) => string`, default stores snapshot files in `__snapshots__` directory. Overrides default snapshot path. For example, to store snapshots next to test files:",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/restoremocks",
-			"title": "config.restoreMocks",
-			"description": "Use when configuring `restoreMocks` — Type `boolean`, default `false`. Should Vitest automatically call [`vi.restoreAllMocks()`](/api/vi#vi-restoreallmocks) before each test.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/retry",
-			"title": "config.retry",
-			"description": "Use when configuring `retry` — Type `number | { count?: number, delay?: number, condition?: RegExp }`, default `0`, CLI `--retry `. Retry the test specific number of times if it fails.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/root",
-			"title": "config.root",
-			"description": "Use when configuring `root` — Type `string`, CLI `-r `. Project root",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/runner",
-			"title": "config.runner",
-			"description": "Use when configuring `runner` — Type `VitestRunnerConstructor`, default `node`, when running tests, or `benchmark`, when running benchmarks. Path to a custom test runner. This is an advanced feature and should be used with custom library runners. You can read more about it in [the documentation](/api/advanced/runner).",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/sequence",
-			"title": "config.sequence",
-			"description": "Use when configuring `sequence` — Type `{ sequencer?, shuffle?, seed?, hooks?, setupFiles?, groupOrder }`, default `BaseSequencer`, CLI `--sequence.shuffle`. Options for how tests should be sorted.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/server",
-			"title": "config.server",
-			"description": "Use when configuring `server` — pre-Vitest-4 option that configured the `vite-node` server. Removed in Vitest 4 (vite-node is gone); kept as a reference for users migrating from v3 configs. New code should not set this.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/setupfiles",
-			"title": "config.setupFiles",
-			"description": "Use when configuring `setupFiles` — Type `string | string[]`. Paths to setup files resolved relative to the [`root`](/config/root). They will run before each _test file_ in the same process. By default, all test files run in parallel, but you can configure it with [`sequence.set...",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/silent",
-			"title": "config.silent",
-			"description": "Use when configuring `silent` — Type `boolean | 'passed-only'`, default `false`, CLI `--silent`. Silent console output from tests.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/slowtestthreshold",
-			"title": "config.slowTestThreshold",
-			"description": "Use when configuring `slowTestThreshold` — Type `number`, default `300`, CLI `--slow-test-threshold=`. The number of milliseconds after which a test or suite is considered slow and reported as such in the results.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/snapshotenvironment",
-			"title": "config.snapshotEnvironment",
-			"description": "Use when configuring `snapshotEnvironment` — Type `string`. Path to a custom snapshot environment implementation. This is useful if you are running your tests in an environment that doesn't support Node.js APIs. This option doesn't have any effect on a browser runner.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/snapshotformat",
-			"title": "config.snapshotFormat",
-			"description": "Use when configuring `snapshotFormat` — Type `Omit & { compareKeys?: null | undefined }`. Format options for snapshot testing. These options configure the snapshot-specific formatting layer built on top of [`@vitest/pretty-format`](https://npmx.dev/package/@vitest/pretty-format).",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/snapshotserializers",
-			"title": "config.snapshotSerializers",
-			"description": "Use when configuring `snapshotSerializers` — Type `string[]`, default `[]`. A list of paths to snapshot serializer modules for snapshot testing, useful if you want add custom snapshot serializers. See [Custom Serializer](/guide/snapshot#custom-serializer) for more information.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/stricttags",
-			"title": "config.strictTags",
-			"description": "Use when configuring `strictTags` — Type `boolean`, default `true`, CLI `--strict-tags`. Should Vitest throw an error if test has a [`tag`](/config/tags) that is not defined in the config to avoid silently doing something surprising due to mistyped names (applying the wrong configuration or skipping the t...",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/tags",
-			"title": "config.tags",
-			"description": "Use when configuring `tags` — Type `TestTagDefinition[]`, default `[]`. Defines all [available tags](/guide/test-tags) in your test project. By default, if test defines a name not listed here, Vitest will throw an error, but this can be configured via a [`strictTags`](/config/stricttags) ...",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/teardowntimeout",
-			"title": "config.teardownTimeout",
-			"description": "Use when configuring `teardownTimeout` — Type `number`, default `10000`, CLI `--teardown-timeout=5000`. Default timeout to wait for close when Vitest shuts down, in milliseconds",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/testnamepattern",
-			"title": "config.testNamePattern",
-			"description": "Use when configuring `testNamePattern` — Type `string | RegExp`, CLI `-t `. Run tests with full names matching the pattern.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/testtimeout",
-			"title": "config.testTimeout",
-			"description": "Use when configuring `testTimeout` — Type `number`, default `5_000` in Node.js, `15_000` if `browser.enabled` is `true`, CLI `--test-timeout=5000`. Default timeout of a test in milliseconds. Use `0` to disable timeout completely.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/typecheck",
-			"title": "config.typecheck",
-			"description": "Use when configuring `typecheck` — Type `boolean`, default `false`, CLI `--typecheck`. Options for configuring [typechecking](/guide/testing-types) test environment.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/ui",
-			"title": "config.ui",
-			"description": "Use when configuring `ui` — Type `boolean`, default `false`, CLI `--ui`. Enable [Vitest UI](/guide/ui).",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/unstubenvs",
-			"title": "config.unstubEnvs",
-			"description": "Use when configuring `unstubEnvs` — Type `boolean`, default `false`. Should Vitest automatically call [`vi.unstubAllEnvs()`](/api/vi#vi-unstuballenvs) before each test.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/unstubglobals",
-			"title": "config.unstubGlobals",
-			"description": "Use when configuring `unstubGlobals` — Type `boolean`, default `false`. Should Vitest automatically call [`vi.unstubAllGlobals()`](/api/vi#vi-unstuballglobals) before each test.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/update",
-			"title": "config.update",
-			"description": "Use when configuring `update` — Type `boolean | 'new' | 'all' | 'none'`, default `false`, CLI `-u`. Define snapshot update behavior.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/vmmemorylimit",
-			"title": "config.vmMemoryLimit",
-			"description": "Use when configuring `vmMemoryLimit` — Type `string | number`, default `1 / CPU Cores`. This option affects only `vmForks` and `vmThreads` pools.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/watch",
-			"title": "config.watch",
-			"description": "Use when configuring `watch` — Type `boolean`, default `!process.env.CI && process.stdin.isTTY`, CLI `-w`. Enable watch mode",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "config/watchtriggerpatterns",
-			"title": "config.watchTriggerPatterns",
-			"description": "Use when configuring `watchTriggerPatterns` — Type `WatcherTriggerPattern[]`. Vitest reruns tests based on the module graph which is populated by static and dynamic `import` statements. However, if you are reading from the file system or fetching from a proxy, then Vitest cannot detect those de...",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "guide/advanced/index",
-			"title": "Advanced API: getting started",
-			"description": "Use when driving Vitest from a Node.js script — `startVitest(mode, filters, opts, viteOpts, vitestOpts)` and `createVitest` from `vitest/node`, accessing the resulting Vitest instance, project iteration, programmatic test runs. Library-author API.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.7
-			}
-		},
-		{
-			"path": "guide/advanced/pool",
-			"title": "Custom pool runners (advanced)",
-			"description": "Use when implementing a custom Vitest pool — `PoolRunnerInitializer` shape, the `pool` config option pointing at a function/path, choosing between threads/forks/vmThreads/browser/typescript baseline pools. Library-author API; experimental and low-level.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.7
-			}
-		},
-		{
-			"path": "guide/advanced/reporters",
-			"title": "Custom reporters (advanced)",
-			"description": "Use when extending built-in reporters — `DefaultReporter` / `BasicReporter` / `BlobReporter` from `vitest/node`, overriding lifecycle methods, accessing TestModule/TestSuite/TestCase instances. For from-scratch implementations see /api/advanced/reporters.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.7
-			}
-		},
-		{
-			"path": "guide/advanced/tests",
-			"title": "Running tests programmatically (advanced)",
-			"description": "Use when driving a test run from a Node.js script — `startVitest` (start + run) vs `createVitest` (start only), iterating `vitest.state.getTestModules()`, applying CLI filters, overriding test/Vite config from code.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.7
-			}
-		},
-		{
-			"path": "guide/browser/aria-snapshots",
-			"title": "ARIA snapshots (browser, experimental)",
-			"description": "Use when asserting accessibility-tree structure — `expect.element(locator).toMatchAriaInlineSnapshot(...)` / `.toMatchAriaSnapshot(name)` capturing role and accessible-name structure (the same tree screen readers see). Browser mode only; experimental since 4.1.4.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "guide/browser/component-testing",
-			"title": "Component testing (browser)",
-			"description": "Use when testing UI components in real browsers — Vue, React, Svelte, Lit, Preact, Qwik, Solid, Marko via the corresponding `vitest-browser-*` package, browser-mode setup with Playwright/WebdriverIO/preview, why real browsers over jsdom for catching CSS/layout bugs.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "guide/browser/index",
-			"title": "Browser mode setup",
-			"description": "Use when setting up Vitest browser mode — `vitest init browser` scaffold, `browser.enabled` config, choosing between Playwright / WebdriverIO / preview providers, `browser.instances`, headless mode, the `vitest/browser` entry-point.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "guide/browser/multiple-setups",
-			"title": "Multiple browser instances (browser)",
-			"description": "Use when running the same browser tests against multiple browsers or configurations — `browser.instances` array (chromium, firefox, webkit, mobile devices), per-instance overrides, shared Vite-server cache benefit over multi-project alternative.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "guide/browser/trace-view",
-			"title": "Playwright trace files (browser)",
-			"description": "Use when capturing Playwright trace files for debugging browser tests — `browser.trace: 'on' | 'retain-on-failure' | 'on-first-retry'`, trace artifacts location, viewing in Playwright Trace Viewer. Playwright provider only.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "guide/browser/visual-regression-testing",
-			"title": "Visual regression testing (browser)",
-			"description": "Use when adding screenshot-comparison tests to catch unintended visual changes — `expect.element(locator).toMatchScreenshot()`, reference-image storage, threshold config, CI-vs-local screenshot stability. Browser mode only.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.55
-			}
-		},
-		{
-			"path": "guide/cli",
-			"title": "Command-line interface",
-			"description": "Use when running tests from a shell — `vitest`, `vitest run`, `vitest watch`, `vitest related`, `vitest bench`, `vitest list`, `vitest init`, plus filename and `filename:line` filters. For per-flag reference see cli-generated.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.78
-			}
-		},
-		{
-			"path": "guide/cli-generated",
-			"title": "CLI flags reference",
-			"description": "Use when looking up a specific CLI flag — auto-generated reference for every flag (--root, --config, --update, --watch, --reporter, --pool, --typecheck, --browser, --maxWorkers, --bail, --retry, --coverage, --shard). Each flag links to its config equivalent.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.78
-			}
-		},
-		{
-			"path": "guide/common-errors",
-			"title": "Common errors and fixes",
-			"description": "Use when troubleshooting a Vitest startup or runtime failure — `Cannot find module ./relative-path` (vite-tsconfig-paths), pool segfaults, `Bindings not found`, `Failed to terminate worker`, `JavaScript heap out of memory`, tsconfig baseUrl pitfalls.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.78
-			}
-		},
-		{
-			"path": "guide/coverage",
-			"title": "Code coverage",
-			"description": "Use when configuring code coverage — `coverage.provider` (v8 default vs istanbul), `--coverage` flag, ignoring code with `/* v8 ignore */` and istanbul hints, `coverage.reporter`, thresholds, custom reporter, watermarks, migrating from c8.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.85
-			}
-		},
-		{
-			"path": "guide/debugging",
-			"title": "Debugging tests",
-			"description": "Use when stepping through a failing test — VS Code JavaScript Debug Terminal, launch.json node configuration, `--inspect-brk` / `--inspect` with `--no-file-parallelism`, `--test-timeout=0` to suspend on breakpoints, browser-mode debugging via Playwright DevTools.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.78
-			}
-		},
-		{
-			"path": "guide/environment",
-			"title": "Test environments",
-			"description": "Use when picking a JS runtime environment for tests — `environment` option (node default, jsdom, happy-dom, edge-runtime), `@vitest-environment` per-file directive, `environmentMatchGlobs`, `environmentOptions` for jsdom/happy-dom config, custom environments.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.78
-			}
-		},
-		{
-			"path": "guide/extending-matchers",
-			"title": "Extending matchers",
-			"description": "Use when adding custom assertions via `expect.extend` — `{ pass, message }` matcher shape, `this.equals` and `this.utils.diff` helpers, asymmetric matcher support, TypeScript ambient declaration to extend `interface Assertion<T>` and `interface AsymmetricMatchersContaining`.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.78
-			}
-		},
-		{
-			"path": "guide/features",
-			"title": "Vitest features overview",
-			"description": "Use when surveying Vitest's capabilities at a glance — watch mode, native ESM/TS/JSX, hot reload, threads/forks isolation, snapshot testing, mocking, code coverage, multi-environment. For working API see /api or specific guide pages.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.78
-			}
-		},
-		{
-			"path": "guide/filtering",
-			"title": "Filtering which tests run",
-			"description": "Use when narrowing the test set — filename patterns, `filename:line` filter, `-t`/`--testNamePattern`, `.only` / `.skip` / `.todo` per-test, `--tags-filter`, `--changed`, `--related`, `--experimental.preParse` for skipping unfiltered file loads.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.78
-			}
-		},
-		{
-			"path": "guide/ide",
-			"title": "IDE integrations",
-			"description": "Use when wiring Vitest into an editor — official VS Code extension (vitest.explorer), JetBrains built-in support (WebStorm, IntelliJ Ultimate, PhpStorm), Neovim plugin, Zed integration. Test explorer, gutter run/debug, watch indicators.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.78
-			}
-		},
-		{
-			"path": "guide/improving-performance",
-			"title": "Improving test-suite performance",
-			"description": "Use when optimizing slow test suites — disabling `isolate`, choosing pool (forks vs threads vs vmThreads vs vmForks), `--shard` for distribution, tuning `maxWorkers`/`minWorkers`, reducing `setupFiles`, mocking expensive imports. Pair with profiling-test-performance for measurement.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.78
-			}
-		},
-		{
-			"path": "guide/in-source",
-			"title": "In-source testing",
-			"description": "Use when writing tests inside source files (Rust-style `if (import.meta.vitest)` blocks) — `defineConfig.test.includeSource`, `define: { 'import.meta.vitest': 'undefined' }` for production strip, accessing private state without exporting.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.78
-			}
-		},
-		{
-			"path": "guide/index",
-			"title": "Getting started",
-			"description": "Use when first installing Vitest or scaffolding a project — `npm install -D vitest`, writing a first test, `vitest.config.ts` skeleton, the `test` npm script, framework integrations (Vue, React, Svelte), test-file naming conventions.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.78
-			}
-		},
-		{
-			"path": "guide/learn/async",
-			"title": "Tutorial: testing async code",
-			"description": "Use when learning how to test asynchronous code — `async`/`await` test functions, `await expect(promise).resolves.toBe(...)` and `.rejects.toThrow(...)`, `expect.poll` for retries, `vi.waitFor` / `vi.waitUntil`, common pitfalls with unawaited promises.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.8
-			}
-		},
-		{
-			"path": "guide/learn/debugging-tests",
-			"title": "Tutorial: debugging failing tests",
-			"description": "Use when systematically diagnosing a failing test — reading the FAIL header, assertion message, diff, and code-snippet output, isolating with `-t` and filename filters, `--reporter=verbose`, `console.log` placement, common causes (async, mock leakage, env).",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.8
-			}
-		},
-		{
-			"path": "guide/learn/matchers",
-			"title": "Tutorial: using matchers",
-			"description": "Use when learning Vitest's matchers in tutorial form — `toBe` (Object.is) vs `toEqual` (deep), `toMatch`, `toContain`, `toThrow`, `toHaveBeenCalled*`, `not` negation, asymmetric matchers like `expect.any(Number)`. For full reference see /api/expect.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.8
-			}
-		},
-		{
-			"path": "guide/learn/mock-functions",
-			"title": "Tutorial: mock functions",
-			"description": "Use when learning function mocking from scratch — `vi.fn()` for tracking call counts and args (`toHaveBeenCalled`, `toHaveBeenCalledWith`), `mockReturnValue` / `mockResolvedValue` / `mockImplementation`, `vi.spyOn(obj, 'method')` for tracking existing methods. Module mocking lives at /guide/mocking/modules.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.8
-			}
-		},
-		{
-			"path": "guide/learn/setup-teardown",
-			"title": "Tutorial: setup and teardown",
-			"description": "Use when learning how to share state between tests — `beforeEach` / `afterEach` for per-test setup, `beforeAll` / `afterAll` for once-per-suite setup, scoping inside describe blocks, async setup via returned promises, cleanup-function pattern.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.8
-			}
-		},
-		{
-			"path": "guide/learn/snapshots",
-			"title": "Tutorial: snapshot testing",
-			"description": "Use when learning snapshot testing from scratch — `toMatchSnapshot()` for stored .snap files vs `toMatchInlineSnapshot()` for in-test snapshots, when snapshots are useful, updating with `-u`, snapshot review discipline.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.8
-			}
-		},
-		{
-			"path": "guide/learn/testing-in-practice",
-			"title": "Tutorial: testing in practice",
-			"description": "Use when deciding what and how to test — contract-based thinking (inputs and outputs as the contract), AAA structure, what to assert vs what to mock, test-file organization, integration vs unit testing thresholds.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.8
-			}
-		},
-		{
-			"path": "guide/learn/writing-tests",
-			"title": "Tutorial: writing tests",
-			"description": "Use when learning the basics of `test` and `expect` — defining tests, `test` vs `it` aliases, organizing with `describe`, `test.each` / `describe.each` parametrization, naming conventions, file structure (`*.test.ts`, `__tests__/`).",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.8
-			}
-		},
-		{
-			"path": "guide/learn/writing-tests-with-ai",
-			"title": "Tutorial: writing tests with AI assistants",
-			"description": "Use when working with an AI coding assistant on tests — providing source file, existing tests, vitest config, and dependency types as context; writing specific prompts; reviewing output for tautological tests, mock-rubber-stamps, hallucinated APIs.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.8
-			}
-		},
-		{
-			"path": "guide/lifecycle",
-			"title": "Test-run lifecycle",
-			"description": "Use when reasoning about when code runs during a Vitest run — initialization, global setup, worker creation per pool, file collection, test execution with hooks, reporting via reporter lifecycle methods, global teardown. Maps phases to globalSetup/setupFiles/before*/after*.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.78
-			}
-		},
-		{
-			"path": "guide/migration",
-			"title": "Migration guide (Vitest 4)",
-			"description": "Use when upgrading to Vitest 4 — Vite >= 6.0.0 / Node >= 20.0.0 prerequisites, V8 coverage AST-aware remapping, removed `coverage.all`/`coverage.extensions`/`coverage.experimentalAstAwareRemapping`/`coverage.ignoreEmptyLines`, `workspace` → `projects` rename, browser-provider package split.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.45
-			}
-		},
-		{
-			"path": "guide/mocking",
-			"title": "Mocking overview",
-			"description": "Use as the entry point to mocking guides — links to dedicated pages for mocking classes, dates, file system, functions, globals, modules, requests, timers. For tutorial intro see /guide/learn/mock-functions; for API reference /api/vi.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.8
-			}
-		},
-		{
-			"path": "guide/mocking/classes",
-			"title": "Mocking: classes",
-			"description": "Use when mocking an entire class — `vi.fn(class { ... })` mock-class shape, mocking constructors, instance methods, static methods, getters/setters, `vi.spyOn(class.prototype, 'method')` for partial mocks, class-mock caveats around `mockReturnValue`.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.8
-			}
-		},
-		{
-			"path": "guide/mocking/dates",
-			"title": "Mocking: dates",
-			"description": "Use when controlling `Date.now()` and the system clock — `vi.useFakeTimers()` + `vi.setSystemTime(date)`, advancing time via `vi.advanceTimersByTime`, restoring real timers with `vi.useRealTimers()`. Backed by @sinonjs/fake-timers.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.8
-			}
-		},
-		{
-			"path": "guide/mocking/file-system",
-			"title": "Mocking: file system (memfs)",
-			"description": "Use when isolating tests from disk — `memfs` package + `__mocks__/fs.cjs` and `__mocks__/fs/promises.cjs` redirecting `fs` calls to an in-memory volume, `vi.mock('node:fs')` activation, fixture seeding via `vol.fromJSON`.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.8
-			}
-		},
-		{
-			"path": "guide/mocking/functions",
-			"title": "Mocking: functions (vi.fn vs vi.spyOn)",
-			"description": "Use when distinguishing function mocks from spies — `vi.fn()` for new mock functions vs `vi.spyOn(obj, 'method')` for tracking existing methods, mockReset/mockRestore lifecycle, replacing implementations, asserting call counts and arguments.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.8
-			}
-		},
-		{
-			"path": "guide/mocking/globals",
-			"title": "Mocking: globals",
-			"description": "Use when stubbing globals not present in jsdom/node — `vi.stubGlobal('IntersectionObserver', mockClass)`, accessible on both `globalThis` and `window`, restoring via `vi.unstubAllGlobals()` or the `unstubGlobals: true` config option.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.8
-			}
-		},
-		{
-			"path": "guide/mocking/modules",
-			"title": "Mocking: modules",
-			"description": "Use when mocking ES modules — `vi.mock('./path')` hoisting semantics, factory function returning the module shape, `vi.hoisted` for variables referenced in factories, `vi.importActual` for partial mocks, dynamic `import()` overload, `__mocks__/` automatic resolution.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.8
-			}
-		},
-		{
-			"path": "guide/mocking/requests",
-			"title": "Mocking: network requests (MSW)",
-			"description": "Use when intercepting HTTP/WebSocket/GraphQL requests in tests — Mock Service Worker (`msw/node`) with `setupServer`, request handlers via `http.get` / `graphql.query`, lifecycle in beforeAll / afterEach / afterAll. Framework-agnostic; recommended over `vi.mock('node:fetch')`.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.8
-			}
-		},
-		{
-			"path": "guide/mocking/timers",
-			"title": "Mocking: timers",
-			"description": "Use when faking `setTimeout` / `setInterval` / `queueMicrotask` — `vi.useFakeTimers()`, `vi.advanceTimersByTime(ms)`, `vi.runAllTimers()`, `vi.runOnlyPendingTimers()`, restoring with `vi.useRealTimers()`. Configure which APIs to fake via the `toFake` option.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.8
-			}
-		},
-		{
-			"path": "guide/open-telemetry",
-			"title": "OpenTelemetry support (experimental)",
-			"description": "Use when integrating OpenTelemetry tracing into Vitest — `experimental.openTelemetry.sdkPath` (default-export the SDK module), `experimental.openTelemetry.enabled`, `vitest.runtime.traces` span scope, instrumentation per worker. Increases startup time unless --no-isolate.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.78
-			}
-		},
-		{
-			"path": "guide/parallelism",
-			"title": "Parallelism",
-			"description": "Use when reasoning about Vitest's two parallelism levels — file parallelism (workers per `pool`, `maxWorkers`/`minWorkers`, `fileParallelism`) vs test parallelism within a file (`test.concurrent` / `describe.concurrent` / `--sequence.concurrent`). Trade-offs around shared state and external resources.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.78
-			}
-		},
-		{
-			"path": "guide/profiling-test-performance",
-			"title": "Profiling test performance",
-			"description": "Use when measuring where Vitest spends time — output time metrics (transform, setup, import, tests, environment), `--logHeapUsage`, `--profile` for V8 CPU profiles, browser tracing, file-transform analysis. Pair with improving-performance for fixes.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.78
-			}
-		},
-		{
-			"path": "guide/projects",
-			"title": "Test projects",
-			"description": "Use when defining multiple project configs in one Vitest run — `projects` array (replaces deprecated `workspace`), per-project `name`/`include`/`environment`/`browser`/`pool`, monorepo glob patterns, running a single project via `--project=<name>`.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.78
-			}
-		},
-		{
-			"path": "guide/recipes",
-			"title": "Config recipes",
-			"description": "Use when looking for opinionated config snippets — disabling isolation per project, splitting parallel and sequential test files, custom matrix configurations, integrating with frameworks. Drop-in copy/paste examples.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.78
-			}
-		},
-		{
-			"path": "guide/reporters",
-			"title": "Built-in reporters",
-			"description": "Use when configuring test output — `--reporter`/`reporters` config, built-ins (default, verbose, dot, tap, tap-flat, junit, json, html, github-actions, blob, hanging-process), reporter-specific options like `outputFile`, plugging in custom reporters.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.78
-			}
-		},
-		{
-			"path": "guide/snapshot",
-			"title": "Snapshot testing",
-			"description": "Use when working with snapshot tests — `toMatchSnapshot` / `toMatchInlineSnapshot` / `toMatchFileSnapshot`, snapshot-file location and `resolveSnapshotPath`, `--update` flag, custom snapshot serializers, dedupe and shape-stripping helpers.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.78
-			}
-		},
-		{
-			"path": "guide/test-annotations",
-			"title": "Test annotations",
-			"description": "Use when attaching extra context to test results — `context.annotate(message, type)` for warning/error annotations, attaching files/text via `{ body, contentType, bodyEncoding }`, surfaced through the `onTestAnnotate` reporter hook.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.78
-			}
-		},
-		{
-			"path": "guide/test-context",
-			"title": "Test context",
-			"description": "Use when working with the per-test context object — built-in `task` / `expect` / `signal` / `annotate` / `onTestFailed` / `onTestFinished` / `onTestRetry`, defining fixtures via `test.extend`, automatic vs manual fixtures, scoped values via `test.scoped`.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.78
-			}
-		},
-		{
-			"path": "guide/test-tags",
-			"title": "Test tags",
-			"description": "Use when categorizing tests with tags (Vitest 4.1+) — declaring tags in the `tags: []` config, applying via `test.tag('frontend')`, filtering with `--tags-filter` boolean expressions (`frontend and not slow`), per-tag option overrides (timeout, retry), `strictTags` enforcement.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.78
-			}
-		},
-		{
-			"path": "guide/testing-types",
-			"title": "Testing types",
-			"description": "Use when writing type-only tests — `expectTypeOf` / `assertType` in `*.test-d.ts` files, the `--typecheck` flag, `typecheck.tsconfig` / `typecheck.checker` (tsc or vue-tsc), surfacing source type errors, separate-runs vs overlapping `include` patterns.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.78
-			}
-		},
-		{
-			"path": "guide/ui",
-			"title": "Vitest UI",
-			"description": "Use when running the interactive Vitest UI — `npm i -D @vitest/ui`, `--ui` flag (requires watch mode), accessible at http://localhost:51204/__vitest__/, alternative `html` reporter for static-HTML report export.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.78
-			}
-		},
-		{
-			"path": "guide/using-plugins",
-			"title": "Using plugins",
-			"description": "Use when extending Vitest via Vite plugins — same plugin API as Vite, where to put `plugins` in vitest config, the `configureVitest` plugin hook for Vitest-specific behavior. For plugin authoring see /api/advanced/plugin.",
-			"annotations": {
-				"audience": ["assistant"],
-				"priority": 0.78
-			}
-		}
-	]
-}