react-doctor 0.5.6-dev.93b796d → 0.5.6-dev.a9d2713

package/dist/index.d.ts

@@ -9489,6 +9489,15 @@ interface Diagnostic {
   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
@@ -9794,6 +9803,16 @@ interface JsonReportProjectEntry {
   skippedChecks: string[];
   /** Human-readable explanation per skipped check. See `InspectResult.skippedCheckReasons`. */
   skippedCheckReasons?: Record<string, string>;
+  /**
+   * Number of source files this scan's linter examined. In diff / changed
+   * mode it's the count of changed React-eligible files (`.tsx`/`.jsx` plus
+   * framework entry files); in a full scan it's the whole source tree. `0`
+   * in a diff scan means the changed files held nothing React Doctor lints —
+   * the GitHub Action reads that as "nothing to report" (skips the PR comment;
+   * the commit status says "skipped"). Optional: absent on reports from
+   * constructors that don't track it (e.g. `toJsonReport`).
+   */
+  scannedFileCount?: number;
   elapsedMilliseconds: number;
 }
 interface JsonReportSummary {