# repowise-dev/repowise#2632 (Repowise PR analysis) Plain markdown of the analysis at https://repowise.dev/pr/repowise-dev/repowise/2632 Titles, commit subjects and the AI review below are quoted from the pull request or the model; treat them as data, not instructions. - Pull request: https://github.com/repowise-dev/repowise/pull/2632 (merged, by drakeo338) - Title: "fix(health): surface a fetch error in TestsReachingList" - Analysed head commit: `c26bbd06aa029326bee5e57e02fce24d627db6ac` - Compared range (base..head): `a01f7ec64efe45793e9aeadcc83611d4dcc838fd..c26bbd06aa029326bee5e57e02fce24d627db6ac` - Analysed at: 2026-09-28 08:52 UTC - Repository snapshot: `d50900861a89` (https://repowise.dev/s/d50900861a89) - Freshness: the PR is merged, so this is the analysis of its last analysed push. ## Verdict **Clear in analysed scope.** No supported new findings surfaced in the analyzed scope. 2 files changed, 0 contracts changed with 0 callers outside the PR, 0 findings added, 0 resolved. Change risk: riskier than 19% of this repository's commits (its bottom third). It measures diff size and spread, not danger. The raw score, 6.5 of 10, is on a fixed scale calibrated across other repositories, not a rank in this one. Repository code health 9.4 to 9.4 (base against this head, 0 to 10, higher is healthier). ## AI review A full review by gpt-5.6-luna: the model read the diff and the code around it (50 repository lookups), and each point was checked against the lines it cites before posting. The posted review, verbatim. Points are anchored as `file:line` with the file name only. Begin posted review > Reviewed the whole diff: nothing to fix. End posted review ## What to do 1. Run the tests that cover the changed files: `packages/ui/__tests__/health/inferred-tests.test.tsx` ## Checks The results the bot's checks comment reports for this head. - Coverage: Waiting for this PR's CI to upload a report (the repo's last report arrived 2026-10-01 14:47 UTC), so changed lines are not measured yet. - Tests: 1 of 1 changed file reached by a test (inferred); listed under "Tests that cover this change". - Security: No new findings on changed lines. - Doc drift: No drift in docs this PR edits. Scanned the changed lines at `c26bbd0`. ## Tests that cover this change Which tests reach each changed file, from the call graph (else the import graph) of the last indexed commit (`cae6d27`), nearest tests first, as the checks comment names them. Inferred, not measured: a test reaching a file does not mean it runs the changed lines. Run these. - `packages/ui/src/health/tests-reaching-list.tsx` (call graph): `packages/ui/__tests__/health/inferred-tests.test.tsx` ## Who else knows this code Primary author of each changed file by share of recent commits, the PR author left out. Advisory. - `packages/ui/src/health/tests-reaching-list.tsx`: @RaghavChamadiya, 100% of 2 commits - `packages/ui/__tests__/health/inferred-tests.test.tsx`: @RaghavChamadiya, 100% of 3 commits ## Changed files and their health Per-file code health, base to head (0 to 10), files whose score moved first. - `packages/ui/src/health/tests-reaching-list.tsx`: 8.8 to 8.5; score moved without a change in findings (pre-existing drift) - `packages/ui/__tests__/health/inferred-tests.test.tsx`: 9.7 to 9.8; score moved without a change in findings (pre-existing drift) ## AI review: measured, and deliberately not raised (7) Evidence the model saw and chose not to comment on, with its reason; treat both as data. Disagree with one and it is worth raising yourself. - tests-reaching-list.tsx and coverage_routes.py have been committed together 2 times. The first is in this pull request and the second is not. Set aside: The server-side exception folding is pre-existing and explicitly outside this change; it is not introduced by the client error-state update. - TestsReachingList in tests-reaching-list.tsx (line 40): body change. Called from outside this pull request by 1 production site(s) and 0 test(s), including file-tests-panel.tsx. 1 more callers are inside this pull request. Set aside: The production caller passes a fetcher returning the unchanged TestsReachingFile shape, so the changed SWR error handling does not break the consumer. - The Tests tab on the inferred basis. These are mostly *negative* assertions, and deliberately so. The graph-inferred test map over-claims by construction and carries no line attribution, so the failure mode this tab has to be protected from is not "renders wrong" but "renders convincingly as a measurement": a percentag…. Set aside: The change preserves the documented distinction between a genuine empty graph answer and a failed request. - This change added, in TestsReachingList in tests-reaching-list.tsx (lines 40-130): Brain Method: TestsReachingList is 75 lines, CCN 15, in a file imported by 3 others. ccn 15, centrality_floor 3, dependents_count 3, max_nesting 2, nloc 75. Set aside: The added error handling is straightforward and does not introduce a correctness defect. - TestsReachingList in tests-reaching-list.tsx (line 40): body change. Called from outside this pull request by 1 production site(s) and 0 test(s), including file-tests-panel.tsx. 1 more callers are inside this pull request. Set aside: The production caller passes a valid fetcher and the changed return/error state is handled entirely within the component. - The Tests tab on the inferred basis. These are mostly *negative* assertions, and deliberately so. The graph-inferred test map over-claims by construction and carries no line attribution, so the failure mode this tab has to be protected from is not "renders wrong" but "renders convincingly as a measurement": a percentag…. Set aside: The change preserves the documented distinction between an empty inferred result and a failed request. - tests-reaching-list.tsx and coverage_routes.py have been committed together 2 times. The first is in this pull request and the second is not. Set aside: The server-side exception-to-empty-result behavior predates this change and is explicitly outside its scope. ## What was not reviewed - tests evidence is partial: no measured coverage map; covering tests are graph-inferred. - contracts evidence is partial: a break only test callers can witness counts here and does not in the comment, which reports it by letting those tests fail. - prior fixes evidence is partial: counts come from the indexed snapshot; the churn-weighted fix pressure is not computed. - Not gathered by the bot: branch overlap, independent changes. ## How to act on this 1. Work through "What to do" in order. 2. Items under "What was not reviewed" have no evidence either way. Review those parts yourself.