react-doctor 0.8.0 → 0.8.1-dev.0b0b5ac

package/dist/index.d.ts

@@ -8980,6 +8980,84 @@ declare namespace Annotations {
 }
 //#endregion
 //#region ../core/dist/index.d.ts
+/**
+ * A secondary source location attached to a diagnostic (oxlint's
+ * non-primary labels). Editors render these as
+ * `Diagnostic.relatedInformation` so a user can jump from, say, a
+ * `no-derived-state` finding to the originating prop declaration.
+ * Positions mirror `Diagnostic` semantics: `line` / `column` are
+ * 1-indexed, and `offset` / `length` are UTF-8 byte spans from oxlint
+ * when available (preferred for precise ranges).
+ */
+interface DiagnosticRelatedLocation {
+  filePath: string;
+  line: number;
+  column: number;
+  offset?: number;
+  length?: number;
+  endLine?: number;
+  endColumn?: number;
+  message: string;
+}
+type DiagnosticFileContext = "test" | "story" | "production";
+interface Diagnostic {
+  filePath: string;
+  plugin: string;
+  rule: string;
+  severity: "error" | "warning";
+  title?: string;
+  message: string;
+  help: string;
+  url?: string;
+  line: number;
+  column: number;
+  /**
+   * UTF-8 byte offset of the diagnostic's primary span start, straight
+   * from oxlint's label span. Optional because environment / dead-code
+   * diagnostics carry no source span. Editors (LSP) convert this into a
+   * precise range via the in-memory document; non-editor consumers can
+   * ignore it.
+   */
+  offset?: number;
+  /** UTF-8 byte length of the primary span (pairs with `offset`). */
+  length?: number;
+  /** 1-indexed end line of the primary span, when derivable. */
+  endLine?: number;
+  /** 1-indexed end column of the primary span, when derivable. */
+  endColumn?: number;
+  category: string;
+  /**
+   * Set when the finding's identity is the flagged element itself (a missing
+   * attribute, a wrong element) rather than the flagged line's text — every
+   * Accessibility-category finding, plus rules that opt in via their
+   * `matchByOccurrence` metadata flag. After strict evidence matching,
+   * `computeDiagnosticDelta` may match these by same-file `(plugin/rule,
+   * message)` occurrence count, so reformatting the flagged element doesn't
+   * reclassify a pre-existing finding as new. Resolved at diagnostic creation,
+   * where rule metadata is available. Absent means diagnosed-source-sensitive
+   * matching (the default).
+   */
+  matchByOccurrence?: boolean;
+  /**
+   * Set when the file never ships to users (`"test"` / `"story"`), so
+   * renderers can label the site instead of implying production impact.
+   * Omitted for production files (the default).
+   */
+  fileContext?: Exclude<DiagnosticFileContext, "production">;
+  suppressionHint?: string;
+  /** Secondary source locations (oxlint's non-primary labels). */
+  relatedLocations?: DiagnosticRelatedLocation[];
+  /**
+   * Stable id shared by every finding that a single fix resolves together —
+   * e.g. four `useEffect`s that reset state on one prop change all clear with
+   * one `key` prop. Set only when ≥2 findings share a root cause; absent for
+   * standalone findings. A consumer that turns findings into work items should
+   * group by it so one fix reads as one task, not N. Presentation-only and
+   * score-neutral — the score never reads it.
+   */
+  fixGroupId?: string;
+}
+//#endregion
 //#region src/types/config.d.ts
 /**
  * Severity threshold at which a scan blocks CI (exits non-zero). Controlled
@@ -9057,9 +9135,9 @@ interface ReactDoctorIgnoreConfig {
  * Defaults: design rules (tag `"design"`) are excluded from `prComment`,
  * `score`, and `ciFailure` so style cleanup doesn't dilute meaningful
  * React findings. Diagnostics stamped with `fileContext: "test" | "story"`
- * are excluded from `score` and `ciFailure`. Both remain in `cli`, and an
- * explicit rule, category, or tag include promotes a diagnostic back onto
- * the selected surface.
+ * are excluded from `score` and `ciFailure`. Both remain in `cli`. Explicit
+ * rule, category, or tag includes promote matching diagnostics, while
+ * `includeFileContexts` restores a context without bypassing other exclusions.
  */
 type DiagnosticSurface = "cli" | "prComment" | "score" | "ciFailure";
 /**
@@ -9089,6 +9167,11 @@ interface SeverityBuckets {
   "compiler-cleanup"?: RuleSeverityOverride;
 }
 interface SurfaceControls {
+  /**
+   * Non-production file contexts to retain on this surface. This restores
+   * test or story findings without overriding unrelated tag exclusions.
+   */
+  includeFileContexts?: Array<Exclude<DiagnosticFileContext, "production">>;
   /**
    * Tag names whose diagnostics should be force-included on the surface,
    * even if a default or category-level exclusion would otherwise drop
@@ -9353,9 +9436,9 @@ interface ReactDoctorConfig {
    * - `score` and `ciFailure` exclude test/story file contexts unless explicitly included
    *
    * Pass any controls block, including an empty `{}`, to keep the defaults.
-   * Your include/exclude entries layer on top. Includes always win over
-   * excludes. For example, you can promote one high-signal `design-*` rule
-   * back into the score or PR-comment surface.
+   * Your include/exclude entries layer on top. Rule, category, and tag includes
+   * win over their exclusions. Included file contexts still respect unrelated
+   * exclusions, so restoring story findings does not restore every design rule.
    */
   surfaces?: Partial<Record<DiagnosticSurface, SurfaceControls>>;
   /**
@@ -9449,84 +9532,6 @@ interface ReactDoctorConfig {
    */
   plugins?: string[];
 } //#endregion
-//#region src/types/diagnostic.d.ts
-/**
- * A secondary source location attached to a diagnostic (oxlint's
- * non-primary labels). Editors render these as
- * `Diagnostic.relatedInformation` so a user can jump from, say, a
- * `no-derived-state` finding to the originating prop declaration.
- * Positions mirror `Diagnostic` semantics: `line` / `column` are
- * 1-indexed, and `offset` / `length` are UTF-8 byte spans from oxlint
- * when available (preferred for precise ranges).
- */
-interface DiagnosticRelatedLocation {
-  filePath: string;
-  line: number;
-  column: number;
-  offset?: number;
-  length?: number;
-  endLine?: number;
-  endColumn?: number;
-  message: string;
-}
-type DiagnosticFileContext = "test" | "story" | "production";
-interface Diagnostic {
-  filePath: string;
-  plugin: string;
-  rule: string;
-  severity: "error" | "warning";
-  title?: string;
-  message: string;
-  help: string;
-  url?: string;
-  line: number;
-  column: number;
-  /**
-   * UTF-8 byte offset of the diagnostic's primary span start, straight
-   * from oxlint's label span. Optional because environment / dead-code
-   * diagnostics carry no source span. Editors (LSP) convert this into a
-   * precise range via the in-memory document; non-editor consumers can
-   * ignore it.
-   */
-  offset?: number;
-  /** UTF-8 byte length of the primary span (pairs with `offset`). */
-  length?: number;
-  /** 1-indexed end line of the primary span, when derivable. */
-  endLine?: number;
-  /** 1-indexed end column of the primary span, when derivable. */
-  endColumn?: number;
-  category: string;
-  /**
-   * Set when the finding's identity is the flagged element itself (a missing
-   * attribute, a wrong element) rather than the flagged line's text — every
-   * Accessibility-category finding, plus rules that opt in via their
-   * `matchByOccurrence` metadata flag. `computeDiagnosticDelta` matches these
-   * by `(filePath, plugin/rule)` occurrence count, so reformatting the flagged
-   * line doesn't reclassify a pre-existing finding as new. Resolved at
-   * diagnostic creation, where rule metadata is available. Absent means
-   * line-text-sensitive matching (the default).
-   */
-  matchByOccurrence?: boolean;
-  /**
-   * Set when the file never ships to users (`"test"` / `"story"`), so
-   * renderers can label the site instead of implying production impact.
-   * Omitted for production files (the default).
-   */
-  fileContext?: Exclude<DiagnosticFileContext, "production">;
-  suppressionHint?: string;
-  /** Secondary source locations (oxlint's non-primary labels). */
-  relatedLocations?: DiagnosticRelatedLocation[];
-  /**
-   * Stable id shared by every finding that a single fix resolves together —
-   * e.g. four `useEffect`s that reset state on one prop change all clear with
-   * one `key` prop. Set only when ≥2 findings share a root cause; absent for
-   * standalone findings. A consumer that turns findings into work items should
-   * group by it so one fix reads as one task, not N. Presentation-only and
-   * score-neutral — the score never reads it.
-   */
-  fixGroupId?: string;
-}
-//#endregion
 //#region src/types/project-info.d.ts
 type Framework = FrameworkToken;
 interface ProjectInfo {
@@ -9538,11 +9543,38 @@ interface ProjectInfo {
   zodVersion: string | null;
   /** Parsed major from `zodVersion`, or `null` when absent/unparseable. Mirrors `reactMajorVersion`. */
   zodMajorVersion: number | null;
+  /** Declared MobX core version spec. Optional so existing `ProjectInfo` consumers remain source-compatible. */
+  mobxVersion?: string | null;
+  /** Parsed major from `mobxVersion`, or `null` when absent/unparseable. */
+  mobxMajorVersion?: number | null;
+  hasMobxReact?: boolean;
+  hasMobxReactLite?: boolean;
+  hasMobxStateTree?: boolean;
+  hasMobxReactObserver?: boolean;
+  /** Declared Zustand version spec. Optional so existing `ProjectInfo` consumers remain source-compatible. */
+  zustandVersion?: string | null;
+  /** Parsed major from `zustandVersion`, or `null` when absent/unparseable. */
+  zustandMajorVersion?: number | null;
   framework: Framework;
   hasTypeScript: boolean;
   hasReactCompiler: boolean;
   hasReactCompilerLintPlugin?: boolean;
   hasTanStackQuery: boolean;
+  hasRemotion?: boolean;
+  remotionVersion?: string | null;
+  remotionMajorVersion?: number | null;
+  hasI18nLibrary?: boolean;
+  tanstackQueryVersion?: string | null;
+  styledComponentsVersion?: string | null;
+  /**
+   * The declared `valtio` version spec, or `null` when no package in the
+   * analyzed project declares Valtio. `useSnapshot` has kept the same
+   * render-read contract across Valtio 1 and 2, so presence alone drives the
+   * `valtio` capability and its parsed major-version ladder.
+   */
+  valtioVersion: string | null;
+  /** Parsed major from `valtioVersion`, or `null` when absent/unparseable. */
+  valtioMajorVersion: number | null;
   /**
    * `true` when the project or a workspace declares a Vite-based SSR runtime
    * such as React Router's Node adapter, Vike, or vite-plugin-ssr.
@@ -9843,7 +9875,8 @@ interface InspectResult {
   baselineDelta?: {
     /** The commit the base content was read from (resolved merge-base). */baseRef: string; /** Findings present at base but gone at head — resolved by the change. */
     fixedCount: number; /** Total findings at base (over the same files), for context. */
-    baseTotalCount: number;
+    baseTotalCount: number; /** Pre-existing findings matched after moving to a different file. */
+    crossFileMatchCount?: number;
   };
 }
 /**
@@ -10259,15 +10292,7 @@ declare const buildJsonReport: (input: BuildJsonReportInput) => JsonReportV3$1;
  * `GitBaseBranchMissing`) as clean user errors instead of crashes.
  */
 declare const getDiffInfo: (directory: string, explicitBaseBranch?: string, includeUntracked?: boolean) => Promise<DiffInfo | null>;
-declare const filterSourceFiles: (filePaths: string[]) => string[];
-/**
- * Programmatic façade over `Git.changedLineRanges` (the `lines` scope). Diffs
- * `files` with `--unified=0` against `baseRef` (or the index when `cached`),
- * returning per-file changed line ranges relative to `directory`. Returns
- * `null` when the ranges can't be computed (git unavailable / unsafe ref /
- * non-zero exit) so the caller degrades to file-level scope; an empty array
- * means git succeeded but the files added no lines.
- */
+declare const filterSourceFiles: (filePaths: ReadonlyArray<string>) => string[];
 //#endregion
 //#region src/summarize-diagnostics.d.ts
 declare const summarizeDiagnostics: (diagnostics: Diagnostic[], worstScore?: number | null, worstScoreLabel?: string | null) => JsonReportSummary; //#endregion