react-doctor 0.9.12-dev.a2b460d → 0.9.12-dev.ac87f7d

package/dist/{should-skip-prompts-mXKZBNCz.js → should-skip-prompts-DzzBAamD.js}

@@ -1,10 +1,10 @@
 
-!function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{},n=(new e.Error).stack;n&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[n]="05cde194-2b40-558a-bef8-516987e69a93")}catch(e){}}();
-import { z as isNonInteractiveEnvironment } from "./record-metric-CMe2d1Xv.js";
+!function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{},n=(new e.Error).stack;n&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[n]="f06aa592-3758-5107-8839-c5374c76b1f7")}catch(e){}}();
+import { B as isNonInteractiveEnvironment } from "./record-metric-DVm5sVu2.js";
 //#region src/cli/utils/should-skip-prompts.ts
 const shouldSkipPrompts = (input = {}) => Boolean(input.yes) || Boolean(input.json) || isNonInteractiveEnvironment() || !process.stdin.isTTY;
 //#endregion
 export { shouldSkipPrompts as t };
 
-//# sourceMappingURL=should-skip-prompts-mXKZBNCz.js.map
-//# debugId=05cde194-2b40-558a-bef8-516987e69a93
+//# sourceMappingURL=should-skip-prompts-DzzBAamD.js.map
+//# debugId=f06aa592-3758-5107-8839-c5374c76b1f7

package/dist/should-use-tui-DVrQvWL6.js

@@ -0,0 +1,25 @@
+
+!function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{},n=(new e.Error).stack;n&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[n]="bf1397cc-4b46-5916-b023-686dc1b693e4")}catch(e){}}();
+import { B as isNonInteractiveEnvironment } from "./record-metric-DVm5sVu2.js";
+//#region src/cli/utils/resolve-tui-environment.ts
+const resolveTuiEnvironment = (outputIsTty = process.stdout.isTTY === true) => ({
+	isNonInteractiveEnvironment: isNonInteractiveEnvironment(),
+	nodeMajorVersion: Number(process.versions.node.split(".")[0]),
+	outputIsTty,
+	stdinIsTty: process.stdin.isTTY === true,
+	supportsRawMode: typeof process.stdin.setRawMode === "function",
+	terminalName: process.env.TERM
+});
+//#endregion
+//#region src/cli/utils/should-use-tui.ts
+const isTuiEnvironmentSupported = (input) => !input.isNonInteractiveEnvironment && input.stdinIsTty && input.outputIsTty && input.supportsRawMode && input.nodeMajorVersion >= 22 && input.terminalName !== "dumb";
+const shouldUseTui = (input) => {
+	if (!isTuiEnvironmentSupported(input)) return false;
+	const flags = input.flags;
+	return !(flags.score === true || flags.json === true || flags.jsonCompact === true || flags.jsonOut !== void 0 || flags.staged === true || flags.changedFilesFrom !== void 0);
+};
+//#endregion
+export { shouldUseTui as n, resolveTuiEnvironment as r, isTuiEnvironmentSupported as t };
+
+//# sourceMappingURL=should-use-tui-DVrQvWL6.js.map
+//# debugId=bf1397cc-4b46-5916-b023-686dc1b693e4

package/dist/skills/improve-threejs/SKILL.md

@@ -0,0 +1,102 @@
+---
+name: improve-threejs
+description: Audit and fix Three.js and React Three Fiber apps for frame-loop performance, GPU memory leaks, scene-graph correctness, and visual defects like z-fighting, shadow acne, wrong color space, and broken resize handling. Uses React Doctor as the scanning engine plus a visual rubric checked against rendered output. Use when the user asks to improve, audit, scan, or clean up a Three.js, R3F, react-three-fiber, drei, or WebGL app, or types `/improve-threejs`.
+---
+
+# Improve Three.js
+
+Audits a Three.js or React Three Fiber (R3F) codebase and fixes what hurts most: work that runs every frame, GPU resources that never get disposed, scene-graph objects rebuilt on every render, and visual defects the user can see. React Doctor supplies the machine-verified code scan; this skill supplies the frame-loop judgment and the visual inspection a general React scanner lacks.
+
+The core principle: severity follows the render loop. Code inside `useFrame` or a `requestAnimationFrame` callback runs 60 times per second, so a minor inefficiency there outweighs a major one in a settings panel. Rank every finding by where it runs, not by the rule's default severity.
+
+## Workflow
+
+### Step 1: Recon
+
+Identify the stack before scanning: plain Three.js or R3F, which helper libraries are in use (drei, postprocessing, rapier), and where the render loop lives (`useFrame` hooks, `requestAnimationFrame`, the `<Canvas frameloop>` setting).
+
+Build a hot-path map: every `useFrame` body, every RAF callback, every pointer-move handler. These files get the strictest review in Step 3.
+
+### Step 2: Scan
+
+Run React Doctor read-only to collect structured evidence:
+
+```bash
+npx react-doctor@latest --verbose
+```
+
+For a regression check after making changes, run with `--scope changed` and confirm the score did not drop.
+
+### Step 3: Triage by frame-loop leverage
+
+Re-rank the scanner's findings using the hot-path map, then hunt for the Three.js-specific problems the scanner cannot see. Confirm every finding at its `file:line` before reporting it.
+
+**HIGH severity, runs every frame or leaks GPU memory:**
+
+- **Allocation inside `useFrame`**: `new Vector3()`, `new Color()`, or fresh arrays passed to Three.js APIs each frame. Fix: hoist a scratch object to module scope or `useMemo`, then mutate it in place
+- **`setState` inside `useFrame`**: re-renders the React tree on every frame. Fix: mutate refs directly; reserve state for discrete changes like selection or visibility
+- **Missing disposal**: geometries, materials, textures, or render targets created imperatively and never disposed. Fix: call `dispose()` in the cleanup function, or move the object into R3F's declarative tree so it owns the lifecycle
+- **Object reconstruction in render**: geometry or material instances created without `useMemo`, or inline `args` arrays whose identity changes each render, forcing R3F to rebuild the underlying object
+
+**MEDIUM severity, per-render or per-interaction waste:**
+
+- **Unstable scene-graph props**: inline `new THREE.Vector3()` or fresh material objects as props (plain arrays like `position={[x, y, z]}` are fine; R3F handles them)
+- **Missing instancing**: hundreds of identical meshes rendered individually instead of through `<Instances>` or `InstancedMesh`
+- **Wasted frames**: `frameloop="always"` on a scene that only changes on interaction. Fix: `frameloop="demand"` plus `invalidate()`
+- **Uncached asset loading**: textures and models loaded outside `useLoader`, `useTexture`, or `useGLTF`, losing caching and Suspense integration
+
+**LOW severity, hygiene:** React Doctor findings on non-canvas UI code, missing `<Preload>`, oversized textures.
+
+### Step 4: Visual audit
+
+Inspect what the scene actually renders. Every visual finding needs evidence: a screenshot, a frame capture, or a reproduced observation, never a guess from reading source. When a dev server and browser are available, load the app, capture the first stable frame, then capture again after moving the camera and interacting. When no browser is available, check the code-level causes listed below and label each finding as inferred from source.
+
+Apply the mini rubric. A row fails only when the evidence shows the failure condition:
+
+| Area                   | Check                                                                  | Fail when                                                                                          |
+| ---------------------- | ---------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
+| Render sanity          | The scene reaches a stable frame after load                            | Black canvas, WebGL context errors, or content that never appears                                  |
+| Geometry               | Move the camera along seams, edges, and boundaries                     | Gaps, missing faces, visible backfaces, or two surfaces flickering at the same depth (z-fighting)  |
+| Transparency and depth | Cross depth-order boundaries with overlapping or transmissive surfaces | Wrong sort order, halos, opaque surfaces that should transmit, or flicker at grazing angles        |
+| Textures               | View mapped surfaces close, far, and at grazing angles                 | Missing textures, stretching, seams, moiré, shimmer, or washed-out colors from a wrong color space |
+| Materials and lighting | Change light and view direction on lit surfaces                        | Surfaces that ignore light direction, or reflective metals with no environment to reflect          |
+| Shadows                | Move casters, receivers, and the light through their range             | Acne, detached or floating shadows, flicker at rest, or shadows that outlive their caster          |
+| Camera                 | Follow the primary subject through movement and transitions            | Subject leaves frame, camera clips into geometry, or foreground blocks the play area               |
+| Scale and contact      | Compare object scale and resting contact against surroundings          | Objects float above, sink into, or intersect their support surface, or sit at implausible scale    |
+| Image stability        | Pan the camera slowly at supported resolutions                         | Silhouettes, thin geometry, or highlights that crawl, sparkle, or ghost                            |
+| Resize and DPR         | Change viewport size, zoom, and device pixel ratio                     | Distortion, blur, stretched output, or content leaving the viewport                                |
+
+Each rubric row has a small set of usual code-level causes. Check these first when a row fails:
+
+- **Washed-out or too-dark colors**: `renderer.outputColorSpace` not set to `SRGBColorSpace`, color textures missing `texture.colorSpace = SRGBColorSpace`, or a data texture (normal, roughness) wrongly marked sRGB
+- **Z-fighting**: coplanar geometry needing `polygonOffset` or a position nudge, or a near plane set far too small for the scene scale
+- **Shadow acne or floating shadows**: `shadow.bias` and `shadow.normalBias` untuned, or a shadow camera frustum far larger than the scene
+- **Blurry or stretched canvas**: renderer size not synced to canvas CSS size, `setPixelRatio` never called, or a resize handler that forgets `camera.updateProjectionMatrix()`
+- **Black metals**: `metalness: 1` with no `scene.environment` set
+- **Transparency sorting glitches**: large transparent meshes needing `depthWrite: false`, manual `renderOrder`, or a split into smaller meshes
+- **Shimmer and crawl**: missing texture anisotropy, antialiasing disabled, or thin geometry needing thicker forms
+
+### Step 5: Fix
+
+Fix in severity order: HIGH performance findings and failed visual rows first. When a finding maps to a React Doctor rule, fetch the canonical recipe instead of improvising:
+
+```text
+https://www.react.doctor/prompts/rules/<plugin>/<rule>.md
+```
+
+For Three.js-specific findings, apply the fix named in the triage list or the cause list above.
+
+### Step 6: Validate
+
+Run `npx react-doctor@latest --verbose --scope changed` and confirm the score did not regress. Re-check every visual rubric row that failed, using the same viewpoint and interaction as the original evidence, and confirm it now passes. Then verify behavior: the scene renders, animations play, and interactions respond. If browser dev tools are available, watch the memory profile while orbiting an idle scene; a rising heap during idle means a disposal leak survived.
+
+## Checks the scanner always misses
+
+Review these by hand on every audit:
+
+- `dispose()` coverage for every imperatively created GPU resource
+- Allocations and `setState` inside `useFrame` and RAF callbacks
+- Event listeners and `ResizeObserver`s on the canvas or window without cleanup
+- Raycasting against the full scene on every pointer move instead of a filtered target list
+- Shadows or postprocessing enabled globally when one part of the scene needs them
+- Color space configuration on the renderer and every color texture

package/dist/skills/performance/SKILL.md

@@ -0,0 +1,113 @@
+---
+name: performance
+description: Diagnose React runtime performance with React Doctor traces, live render outlines, Long Animation Frames, interaction timing, and component render evidence. Use when invoked as `/performance` for a slow interaction, unexpected re-renders, or a measured before-and-after comparison.
+disable-model-invocation: true
+---
+
+# Diagnose React runtime performance
+
+Measure one reproducible interaction, connect browser work to React renders, and report only conclusions supported by the trace.
+
+## Define the interaction
+
+Before recording:
+
+1. Identify the target URL
+2. Write the exact actions to reproduce
+3. Choose the expected result
+4. Confirm whether authentication is required
+
+Use a production build when available. Development builds add framework work that can distort render and script timings. If you must measure a development build, label that limitation in the report.
+
+## Record the trace
+
+Run the scan in an interactive terminal:
+
+```bash
+npx react-doctor@latest scan http://localhost:3000 --format json
+```
+
+React Doctor opens an isolated Chrome profile. Perform the planned interaction while purple outlines identify rendered components. Press Enter after the interaction settles; recordings stop automatically after five minutes.
+
+Interactive users can omit the URL and choose a detected localhost app or enter another URL. Agents must always pass the explicit URL so automated runs never wait for input.
+
+For an authenticated session, connect through the Chrome DevTools Protocol (CDP):
+
+```bash
+npx react-doctor@latest scan https://app.example.com \
+  --cdp http://127.0.0.1:9222 \
+  --format json
+```
+
+Use a dedicated debug profile for CDP because Chrome tracing is browser-wide. Sign in, close every non-blank tab, and then start the scan. React Doctor closes leftover blank tabs before tracing. Never request cookies, copy a browser profile, or close an externally managed browser.
+
+The compressed `.json.gz` trace can contain URLs, source paths, and application behavior. Keep it local unless an upload is explicitly approved.
+
+## Read the report
+
+Evaluate the report in this order:
+
+1. **Capture support**: confirm React detection, build type, React tracks, and Long Animation Frame support
+2. **User impact**: inspect the worst interaction, total blocking duration, Largest Contentful Paint (LCP), and Cumulative Layout Shift (CLS)
+3. **Browser work**: inspect long frames and script hotspots for event handling, JavaScript, style, layout, and paint cost
+4. **React work**: inspect component render count, total self time, and maximum self time
+5. **Capture limits**: read every warning, especially dropped event counts
+
+Follow these interpretation rules:
+
+- A high render count is evidence, not a defect. Pair it with duration and user impact
+- Generated chunk names identify browser work, not the owning source component
+- A slow interaction can be browser-bound even when every component render is cheap
+- Repeated Event Timing records with one interaction identifier represent one interaction
+- Dropped component events make hotspot totals incomplete
+- Use purple labels to identify the active subtree, then use recorded timings to set severity
+
+## Connect measurements to source
+
+Search the repository for measured component display names and event handlers. Confirm that each candidate runs in the recorded flow before reporting it.
+
+Open the DevTools trace when the summary cannot explain a long frame. Correlate the interaction timestamp with script tasks, style or layout work, React tracks, and paint. Do not infer causality from neighboring timestamps alone.
+
+## Report findings
+
+Use this structure:
+
+```markdown
+## Flow tested
+
+tested_url, build_type, and exact_interaction
+
+## Verdict
+
+one_evidence_backed_paragraph
+
+## Evidence
+
+| Signal            |                  Measurement | Interpretation  |
+| ----------------- | ---------------------------: | --------------- |
+| Worst interaction |                  duration_ms | measured_cause  |
+| Total blocking    |                  duration_ms | measured_scope  |
+| Top component     | render_count and duration_ms | measured_impact |
+
+## Findings
+
+1. `path/to/component.tsx:42`: measured_problem, evidence, and smallest_fix
+
+## Limits
+
+capture_warnings, missing_support, or environmental_caveats
+```
+
+Do not pad the report with static lint findings. Include source findings only when runtime evidence connects them to the tested flow.
+
+## Validate a fix
+
+Do not edit code unless code changes are requested. After a fix:
+
+1. Rebuild with the same mode
+2. Record the same interaction at the same viewport
+3. Run three before and three after samples when timing variance could change the conclusion
+4. Compare medians for interaction, blocking, and component duration
+5. Confirm behavior and accessibility did not regress
+
+Reject improvements that only move work outside the recorded window or disable useful behavior.

package/dist/skills/react-doctor/SKILL.md

@@ -22,6 +22,12 @@ Run `npx react-doctor@latest --verbose` (the default `--scope full`) to scan the
 
 Run `npx react-doctor@latest design --verbose`. This selects only design-tagged UI composition, typography, interaction, accessibility, and motion rules, including focused rules that remain opt-in during a general health scan.
 
+## For runtime performance problems:
+
+Run `npx react-doctor@latest scan <url> --format json` in an interactive terminal. React Doctor opens an isolated system Chrome profile, records a DevTools trace while the user reproduces the slow interaction, and flashes purple outlines with component names as React renders. It stops when they press Enter. Read the structured summary first, then inspect the returned local `.json.gz` trace for CPU, browser, and React component evidence.
+
+If the user needs their authenticated browser state, use `--cdp <remote-debugging-url>`. This requires Chrome to already be running with remote debugging. Never ask for cookies or copy the user's browser profile. Treat the trace as sensitive local application data and never upload it without explicit permission.
+
 ## /doctor — full local triage workflow
 
 When the user types `/doctor`, says "run react doctor", or asks for a full triage / cleanup pass (not just a regression check), fetch the canonical local-triage playbook and follow every step in it:

package/dist/{unref-stdin-Cxhw67r6.js → telemetry-runtime-B45Ns9aS.js}

@@ -1,6 +1,6 @@
 
-!function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{},n=(new e.Error).stack;n&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[n]="f3b95338-df70-58f8-b5df-3a1090942531")}catch(e){}}();
-import { En as messageFromUnknown, R as CliInputError, Yn as make, ar as runSync, g as VERSION, gn as isReactDoctorError, gr as void_, hn as isProjectDiscoveryError, i as isTelemetryEnabled, ir as runPromise, lr as buildWithScope, mr as makeUnsafe, pr as close, un as isErrnoException, yn as layerObservability } from "./record-metric-CMe2d1Xv.js";
+!function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{},n=(new e.Error).stack;n&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[n]="64a6738f-28f7-548a-a501-c85862cab36f")}catch(e){}}();
+import { $t as layerObservability, Cr as messageFromUnknown, Jn as makeUnsafe, Rn as runPromise, Un as buildWithScope, Xn as void_, Xt as isReactDoctorError, Yt as isProjectDiscoveryError, _ as VERSION, br as isErrnoException, i as isTelemetryEnabled, kn as make, qn as close, z as CliInputError, zn as runSync } from "./record-metric-DVm5sVu2.js";
 //#region src/cli/utils/is-environment-error.ts
 const ENVIRONMENT_ERROR_CODES = new Set([
 	"EACCES",
@@ -61,6 +61,51 @@ const formatEnvironmentError = (error) => {
 	}
 };
 //#endregion
+//#region src/cli/utils/is-npm-cache-corruption-error.ts
+const MISSING_AJV_META_SCHEMA_MESSAGES = new Set(["Cannot find module './meta/unevaluated.json'", "Cannot find module './meta/validation.json'"]);
+const NPX_AJV_META_SCHEMA_REQUIRE_PATH_PATTERN = /(?:^|\/)_npx\/(?<cacheKey>[a-f0-9]{16})\/node_modules\/ajv\/dist\/refs\/json-schema-2020-12\/index\.js$/;
+const isModuleNotFoundError = (error) => error instanceof Error && "code" in error && error.code === "MODULE_NOT_FOUND";
+const findNpmCacheCorruptionError = (error) => {
+	const pendingErrors = [error];
+	const visitedErrors = /* @__PURE__ */ new Set();
+	while (pendingErrors.length > 0) {
+		const currentError = pendingErrors.pop();
+		if (typeof currentError !== "object" || currentError === null) continue;
+		if (visitedErrors.has(currentError)) continue;
+		visitedErrors.add(currentError);
+		if (isModuleNotFoundError(currentError)) {
+			const [message] = currentError.message.split("\n");
+			if (message && MISSING_AJV_META_SCHEMA_MESSAGES.has(message)) {
+				const requireStack = Array.isArray(currentError.requireStack) ? currentError.requireStack : [];
+				for (const requirePath of requireStack) {
+					if (typeof requirePath !== "string") continue;
+					const cacheKey = requirePath.replaceAll("\\", "/").match(NPX_AJV_META_SCHEMA_REQUIRE_PATH_PATTERN)?.groups?.cacheKey;
+					if (cacheKey !== void 0) return {
+						cacheKey,
+						moduleNotFoundError: currentError
+					};
+				}
+			}
+		}
+		if (currentError instanceof Error && currentError.cause !== void 0) pendingErrors.push(currentError.cause);
+	}
+	return null;
+};
+const isNpmCacheCorruptionError = (error) => findNpmCacheCorruptionError(error) !== null;
+const formatNpmCacheCorruptionError = (error) => {
+	const corruptionMatch = findNpmCacheCorruptionError(error);
+	if (!corruptionMatch) return messageFromUnknown(error);
+	return [
+		"The npx cache has an incomplete Ajv installation.",
+		"",
+		"Remove this cache entry, then run React Doctor again:",
+		`  npm cache npx rm ${corruptionMatch.cacheKey}`,
+		"  npx react-doctor@latest",
+		"",
+		`Original error: ${corruptionMatch.moduleNotFoundError.message}`
+	].join("\n");
+};
+//#endregion
 //#region src/cli/utils/is-expected-user-error.ts
 /**
 * Whether `error` is an expected, user-actionable failure — the user's project
@@ -69,7 +114,7 @@ const formatEnvironmentError = (error) => {
 * `handleUserError` (a plain message — no "Something went wrong", prefilled
 * issue, Discord link, or Sentry reference), since there is no bug to report.
 *
-* Four distinct shapes reach the CLI's catch blocks:
+* Five distinct shapes reach the CLI's catch blocks:
 *
 * - **Project-discovery failures** (`NoReactDependencyError`,
 *   `ProjectNotFoundError`, `PackageJsonNotFoundError`, `NotADirectoryError`,
@@ -89,12 +134,15 @@ const formatEnvironmentError = (error) => {
 *   actionable message instead of crashing. See `is-environment-error.ts` for
 *   why the set stays narrow (codes that usually mean our bug keep reaching
 *   Sentry).
+* - **npm cache corruption** (missing Ajv meta-schema files inside `_npx`) —
+*   an incomplete npx package installation that the user can remove and
+*   reinstall.
 *
 * This composes the existing core narrowers rather than introducing a new
 * error-shape helper (AGENTS.md): it encodes CLI-layer reporting policy, not
 * knowledge of the `ReactDoctorError` shape.
 */
-const isExpectedUserError = (error) => error instanceof CliInputError || isProjectDiscoveryError(error) || isEnvironmentError(error) || isReactDoctorError(error) && (error.reason._tag === "GitBaseBranchInvalid" || error.reason._tag === "GitBaseBranchMissing");
+const isExpectedUserError = (error) => error instanceof CliInputError || isProjectDiscoveryError(error) || isEnvironmentError(error) || isNpmCacheCorruptionError(error) || isReactDoctorError(error) && (error.reason._tag === "GitBaseBranchInvalid" || error.reason._tag === "GitBaseBranchMissing");
 //#endregion
 //#region src/cli/utils/resolve-axiom-telemetry-options.ts
 /**
@@ -153,11 +201,8 @@ let pendingShutdown = null;
 *
 * Returns `null` when telemetry is disabled or unconfigured, which is what keeps
 * `--no-telemetry` and unconfigured builds from opening a scope at all.
-*
-* `exportIntervalMs` lets a long-running process (the language server) ship
-* telemetry periodically instead of only at shutdown.
 */
-const getTelemetryContext = (overrides = {}) => {
+const getTelemetryContext = () => {
 	if (isBuilt) return telemetryContext;
 	isBuilt = true;
 	if (!isTelemetryEnabled()) return null;
@@ -165,10 +210,7 @@ const getTelemetryContext = (overrides = {}) => {
 	if (options === null && !isUserOtlpConfigured()) return null;
 	try {
 		const scope = makeUnsafe();
-		telemetryContext = runSync(buildWithScope(layerObservability(options === null ? null : {
-			...options,
-			...overrides
-		}), scope));
+		telemetryContext = runSync(buildWithScope(layerObservability(options), scope));
 		telemetryScope = scope;
 	} catch {
 		telemetryContext = null;
@@ -203,25 +245,7 @@ const shutdownTelemetry = async () => {
 	return pendingShutdown;
 };
 //#endregion
-//#region src/cli/utils/active-run-trace.ts
-let activeRunTrace = null;
-const setActiveRunTrace = (trace) => {
-	activeRunTrace = trace;
-};
-const getActiveRunTrace = () => activeRunTrace;
-let lastRunTraceId = null;
-const recordRunTraceId = (traceId) => {
-	lastRunTraceId = traceId;
-};
-const getLastRunTraceId = () => lastRunTraceId;
-//#endregion
-//#region src/cli/utils/unref-stdin.ts
-const unrefStdin = () => {
-	if (process.stdin.isTTY) return;
-	process.stdin.unref?.();
-};
-//#endregion
-export { setActiveRunTrace as a, isExpectedUserError as c, recordRunTraceId as i, formatEnvironmentError as l, getActiveRunTrace as n, getTelemetryContext as o, getLastRunTraceId as r, shutdownTelemetry as s, unrefStdin as t, isEnvironmentError as u };
+export { isNpmCacheCorruptionError as a, formatNpmCacheCorruptionError as i, shutdownTelemetry as n, formatEnvironmentError as o, isExpectedUserError as r, isEnvironmentError as s, getTelemetryContext as t };
 
-//# sourceMappingURL=unref-stdin-Cxhw67r6.js.map
-//# debugId=f3b95338-df70-58f8-b5df-3a1090942531
+//# sourceMappingURL=telemetry-runtime-B45Ns9aS.js.map
+//# debugId=64a6738f-28f7-548a-a501-c85862cab36f

package/dist/unref-stdin-BKT_s38a.js

@@ -0,0 +1,12 @@
+//#region src/cli/utils/unref-stdin.ts
+
+!function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{},n=(new e.Error).stack;n&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[n]="bb265729-ea99-5b37-b53e-561ac78da6ac")}catch(e){}}();
+const unrefStdin = () => {
+	if (process.stdin.isTTY) return;
+	process.stdin.unref?.();
+};
+//#endregion
+export { unrefStdin as t };
+
+//# sourceMappingURL=unref-stdin-BKT_s38a.js.map
+//# debugId=bb265729-ea99-5b37-b53e-561ac78da6ac

package/dist/{version-CnvVY2VD.js → version-Cad39N0q.js}

@@ -1,6 +1,6 @@
 
-!function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{},n=(new e.Error).stack;n&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[n]="5516ea52-a2ad-5c86-9ba7-80fb01a79cd1")}catch(e){}}();
-import { g as VERSION, t as recordCount, w as METRIC } from "./record-metric-CMe2d1Xv.js";
+!function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{},n=(new e.Error).stack;n&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[n]="ddcace85-66bc-501f-b435-7a8d479f5a13")}catch(e){}}();
+import { T as METRIC, _ as VERSION, t as recordCount } from "./record-metric-DVm5sVu2.js";
 //#region src/cli/commands/version.ts
 /**
 * oclif-style version line. 12-factor CLI Apps (#3, "What version am I
@@ -17,5 +17,5 @@ const versionAction = () => {
 //#endregion
 export { versionAction };
 
-//# sourceMappingURL=version-CnvVY2VD.js.map
-//# debugId=5516ea52-a2ad-5c86-9ba7-80fb01a79cd1
+//# sourceMappingURL=version-Cad39N0q.js.map
+//# debugId=ddcace85-66bc-501f-b435-7a8d479f5a13

package/dist/{why-BktDEhhH.js → why-DIEM7rdZ.js}

@@ -1,6 +1,6 @@
 
-!function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{},n=(new e.Error).stack;n&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[n]="94e8d580-22e7-5305-b9ab-885f6ebaa525")}catch(e){}}();
-import { t as inspectAction } from "./inspect-kkvDHKDE.js";
+!function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{},n=(new e.Error).stack;n&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[n]="e58602c5-9e3c-58ac-be89-9055d0de41a0")}catch(e){}}();
+import { t as inspectAction } from "./inspect-B9H_IT4O.js";
 //#region src/cli/commands/why.ts
 /**
 * `why <file:line>` — explains why a rule fired (or why a suppression didn't
@@ -17,5 +17,5 @@ const whyAction = async (location, options) => {
 //#endregion
 export { whyAction };
 
-//# sourceMappingURL=why-BktDEhhH.js.map
-//# debugId=94e8d580-22e7-5305-b9ab-885f6ebaa525
+//# sourceMappingURL=why-DIEM7rdZ.js.map
+//# debugId=e58602c5-9e3c-58ac-be89-9055d0de41a0

package/dist/with-run-span-B9ScJJx3.js

@@ -0,0 +1,110 @@
+
+!function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{},n=(new e.Error).stack;n&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[n]="c4d80bbb-61a2-538c-a5bb-27fc0fd5641d")}catch(e){}}();
+import { D as NANOSECONDS_PER_MILLISECOND, In as provideContext, Xn as void_, Yn as fail, c as setSentryProjectInfo, jn as makeSpan, o as buildSentryScope, r as toSpanAttributes, s as buildSentryProjectContext, zn as runSync } from "./record-metric-DVm5sVu2.js";
+import { t as getTelemetryContext } from "./telemetry-runtime-B45Ns9aS.js";
+import { i as setActiveRunTrace, r as recordRunTraceId } from "./active-run-trace-dlIZeEvb.js";
+//#region src/cli/utils/with-run-span.ts
+/**
+* Ends the run span without letting a telemetry failure change the run's
+* outcome — the invariant every other emit site here already holds.
+*
+* The failure path is the reason this matters most: a throw from `end` there
+* would replace the user's original scan error, so a project-config mistake
+* could surface as an exporter stack trace, be reclassified as a crash, and get
+* reported as one.
+*/
+const endSpanSafely = (span, exit) => {
+	try {
+		span.end(BigInt(Date.now()) * NANOSECONDS_PER_MILLISECOND, exit);
+	} catch {}
+};
+/**
+* Clears the module-level run-scoped telemetry state — the current scanned
+* project and the active run trace. `inspect()` calls this at the start of every
+* run and again after a clean one, so a prior or just-finished scan can't attach
+* its project tags / trace to a later run or to a non-scan error (e.g.
+* inspectAction's post-loop finalize/handoff steps). A thrown scan error skips
+* the post-run reset, leaving the state for the command catch to attribute and
+* link the crash. Concurrent batch members (`concurrentScan`) never touch this
+* state — they neither write nor reset it. Safe to call when telemetry is off
+* (the refs are read only when an event is built).
+*/
+const resetSentryRunState = () => {
+	setSentryProjectInfo(null);
+	setActiveRunTrace(null);
+};
+/**
+* Runs an inspect invocation inside a root span so each `react-doctor` run is a
+* first-class trace with timing and the run snapshot as attributes. The span is
+* handed to `run` so the scan's Effect spans parent under it and so the wide
+* event can be stamped onto it once the outcome is known.
+*
+* A no-op pass-through when telemetry is off (`--no-telemetry`, tests, or an
+* unconfigured build) — `run` receives `undefined` and no span is created, so
+* there's no added exit latency.
+*
+* The span is created against the shared telemetry context rather than a
+* freshly-provided layer, so it lives in the same tracer as the scan program's
+* spans; see `telemetry-runtime.ts` for why that matters. It is started and
+* ended manually because the body it wraps is a promise-returning imperative
+* function, not an Effect — the same shape the Sentry inactive span had.
+*
+* While the span runs, its trace context is recorded as the active run trace so
+* `reportErrorToSentry` can attach a crash thrown during the scan back to this
+* trace (errors surface in the command catch, after the span has ended).
+*
+* A `concurrentScan` (one member of the CLI's multi-project pool) still gets its
+* own root span, but skips recording the active run trace — the module-level
+* handle has single-scan semantics, and overlapping writers would link a crash
+* to an arbitrary sibling's trace.
+*/
+const withRunSpan = async (run, options = {}) => {
+	const telemetryContext = getTelemetryContext();
+	if (telemetryContext === null) return run(void 0);
+	const { tags } = buildSentryScope();
+	const command = typeof tags.command === "string" ? tags.command : "inspect";
+	let rootSpan;
+	try {
+		rootSpan = runSync(makeSpan(`react-doctor ${command}`, { attributes: toSpanAttributes(tags) }).pipe(provideContext(telemetryContext)));
+	} catch {
+		return run(void 0);
+	}
+	recordRunTraceId(rootSpan.traceId);
+	if (options.concurrentScan !== true) setActiveRunTrace({
+		traceId: rootSpan.traceId,
+		spanId: rootSpan.spanId,
+		sampled: rootSpan.sampled
+	});
+	try {
+		const result = await run(rootSpan);
+		endSpanSafely(rootSpan, void_);
+		return result;
+	} catch (error) {
+		endSpanSafely(rootSpan, fail(options.mapErrorForSpan?.(error) ?? error));
+		throw error;
+	}
+};
+/**
+* Records the scanned project (discovered in the `beforeLint` hook): remembers
+* it for the lazy Sentry error-capture path (`buildSentryScope` folds it into
+* exception events) and for per-emit metric attributes, and sets it on the run's
+* root span so the trace carries the project shape too. Always cheap — the span
+* attributes are skipped when `rootSpan` is absent (telemetry off), and storing
+* the info is a plain assignment.
+*
+* A `concurrentScan` only sets the span attributes: the module-level project ref
+* has single-scan semantics, and overlapping writers would stamp events and
+* metrics with an arbitrary sibling's project. Wide events keep full attribution
+* (they ride the span); per-emit metrics simply omit the project shape during a
+* concurrent batch (absent, never wrong).
+*/
+const recordSentryProjectContext = (projectInfo, rootSpan, options = {}) => {
+	if (options.concurrentScan !== true) setSentryProjectInfo(projectInfo);
+	if (rootSpan === void 0) return;
+	for (const [key, value] of Object.entries(toSpanAttributes(buildSentryProjectContext(projectInfo).tags))) rootSpan.attribute(key, value);
+};
+//#endregion
+export { resetSentryRunState as n, withRunSpan as r, recordSentryProjectContext as t };
+
+//# sourceMappingURL=with-run-span-B9ScJJx3.js.map
+//# debugId=c4d80bbb-61a2-538c-a5bb-27fc0fd5641d

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "react-doctor",
-  "version": "0.9.12-dev.a2b460d",
+  "version": "0.9.12-dev.ac87f7d",
   "description": "Your agent writes bad React. This catches it",
   "keywords": [
     "accessibility",
@@ -53,22 +53,22 @@
     "@astrojs/compiler": "^4.0.0",
     "@sentry/node": "^10.54.0",
     "agent-install": "0.0.5",
+    "bippy": "^0.6.1",
     "conf": "^15.1.0",
     "confbox": "^0.2.4",
     "eslint-plugin-react-hooks": "^7.1.1",
+    "is-unicode-supported": "^2.1.0",
     "jiti": "^2.7.0",
     "magicast": "^0.5.3",
+    "oxc-parser": "^0.146.0",
     "oxc-resolver": "^11.24.2",
-    "oxlint": ">=1.77.0 <1.78.0",
+    "oxlint": ">=1.79.0 <1.80.0",
+    "playwright-core": "^1.62.1",
     "prompts": "^2.4.2",
     "typescript": ">=5.0.4 <6",
-    "vscode-languageserver": "^9.0.1",
-    "vscode-languageserver-textdocument": "^1.0.12",
-    "vscode-uri": "^3.1.0",
     "yaml": "^2.9.0",
     "yoga-layout": "~3.2.1",
-    "deslop-js": "0.9.12",
-    "oxlint-plugin-react-doctor": "0.9.12-dev.a2b460d"
+    "oxlint-plugin-react-doctor": "0.9.12-dev.ac87f7d"
   },
   "devDependencies": {
     "@types/babel__code-frame": "^7.27.0",
@@ -82,8 +82,7 @@
     "react": "19.2.5",
     "react-devtools-core": "^7.0.1",
     "@react-doctor/api": "0.9.12",
-    "@react-doctor/core": "0.9.12",
-    "@react-doctor/language-server": "0.9.12"
+    "@react-doctor/core": "0.9.12"
   },
   "engines": {
     "node": "^20.19.0 || >=22.13.0"