# 2233admin/code-intel-pipeline#407 (Repowise PR analysis) Plain markdown of the analysis at https://repowise.dev/pr/2233admin/code-intel-pipeline/407 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/2233admin/code-intel-pipeline/pull/407 (merged, by 2233admin) - Title: "fix(evidence): bound the duplicate-key JSON scanner to each contract's own max_bytes (#123)" - Analysed head commit: `460cba01ff3768c41fd03208ab33200673b74d0f` - Compared range (base..head): `b17d4013afbc7e638ac04c65a2139944e2c9e26b..460cba01ff3768c41fd03208ab33200673b74d0f` - Analysed at: 2026-10-01 17:10 UTC - Repository snapshot: `a705f53705f1` (https://repowise.dev/s/a705f53705f1) - 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. - 23 changed files were not analysed, so this is not a clean bill. 31 files changed, 0 contracts changed with 0 callers outside the PR, 0 findings added, 0 resolved. Change risk: riskier than 65% of this repository's commits (its middle third). It measures diff size and spread, not danger. The raw score, 8.8 of 10, is on a fixed scale calibrated across other repositories, not a rank in this one. Repository code health 3.2 to 3.3 (base against this head, 0 to 10, higher is healthier). ## What to do 1. No measured test map; run the suite covering the changed files. 2. Review the skipped files by hand; they were not compared: `orchestration/integrations.json`, `orchestration/internalization/ast-grep.json`, `orchestration/internalization/codenexus.json`, `orchestration/internalization/graph.json`, `orchestration/internalization/rg.json`, `orchestration/retirements/e04-codenexus-direct/compatibility-retirement-deletion-diff.json`, `orchestration/retirements/e04-codenexus-direct/compatibility-retirement-manifest.json`, `orchestration/retirements/e04-codenexus-direct/compatibility-retirement-ticket.json`, `orchestration/retirements/e04-codenexus-direct/e00-request.json`, `orchestration/retirements/e04-codenexus-direct/e01-request.json`, `orchestration/retirements/e04-codenexus-direct/e01-stderr.txt`, `orchestration/retirements/e04-codenexus-direct/evidence/c00-necessity.json`, `orchestration/retirements/e04-codenexus-direct/evidence/compatibility-window.json`, `orchestration/retirements/e04-codenexus-direct/evidence/contract-parity.json`, `orchestration/retirements/e04-codenexus-direct/evidence/dependency-b05.json`, `orchestration/retirements/e04-codenexus-direct/evidence/effect-parity.json`, `orchestration/retirements/e04-codenexus-direct/evidence/golden-parity.json`, `orchestration/retirements/e04-codenexus-direct/evidence/independent-approval.json`, `orchestration/retirements/e04-codenexus-direct/evidence/registry-reconciliation.json`, `orchestration/retirements/e04-codenexus-direct/evidence/replacement-atom.json`, `orchestration/retirements/e04-codenexus-direct/evidence/rollback-execution.json`, `orchestration/retirements/e04-codenexus-direct/evidence/usage-observation.json`, `orchestration/retirements/e04-codenexus-direct/gate-out/compatibility-retirement-decision.json` ## Checks The results the bot's checks comment reports for this head. - Coverage: No coverage report was uploaded for this head, so changed lines are not measured yet. - Tests: 0 of 6 changed files 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 `460cba0`. 1 changed file not scanned (no diff, binary, too large, or past the file cap). ## Tests that cover this change Which tests reach each changed file, from the call graph (else the import graph) of the last indexed commit (`9cb3670`), 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. - `crates/code-intel-cli/src/admissibility.rs`: no test signal - `crates/code-intel-cli/src/artifact_ref.rs`: no test signal - `crates/code-intel-cli/src/budget_dispatch.rs`: no test signal - `crates/code-intel-cli/src/budget_dispatch_oversize.rs`: no test signal - `crates/code-intel-cli/src/capability.rs`: no test signal - `crates/code-intel-cli/src/content_contract.rs`: no test signal ## Who else knows this code Primary author of each changed file by share of recent commits, the PR author left out. Advisory. - `crates/code-intel-cli/src/content_contract.rs`: Curry, 83% of 3 commits - `crates/code-intel-cli/src/admissibility.rs`: Curry, 100% of 1 commit - `crates/code-intel-cli/tests/graph_adapter.rs`: Curry, 96% of 8 commits 2 other files are mostly the PR author's own. ## Changed files and their health Per-file code health, base to head (0 to 10), files whose score moved first. - `crates/code-intel-cli/tests/graph_adapter.rs`: 4.4 to 4.2; score moved without a change in findings (pre-existing drift) - 7 files unchanged. ## What was not reviewed - 23 of 31 changed files were not measured, so nothing here speaks for them (`orchestration/integrations.json`: unsupported language, `orchestration/internalization/rg.json`: unsupported language, `orchestration/internalization/graph.json`: unsupported language, `orchestration/internalization/ast-grep.json`: unsupported language, `orchestration/internalization/codenexus.json`: unsupported language, `orchestration/retirements/e04-codenexus-direct/e01-stderr.txt`: unsupported language, `orchestration/retirements/e04-codenexus-direct/e00-request.json`: unsupported language, `orchestration/retirements/e04-codenexus-direct/e01-request.json`: unsupported language, `orchestration/retirements/e04-codenexus-direct/evidence/c00-necessity.json`: unsupported language, `orchestration/retirements/e04-codenexus-direct/evidence/effect-parity.json`: unsupported language, `orchestration/retirements/e04-codenexus-direct/evidence/golden-parity.json`: unsupported language, `orchestration/retirements/e04-codenexus-direct/evidence/dependency-b05.json`: unsupported language, `orchestration/retirements/e04-codenexus-direct/evidence/contract-parity.json`: unsupported language, `orchestration/retirements/e04-codenexus-direct/evidence/replacement-atom.json`: unsupported language, `orchestration/retirements/e04-codenexus-direct/evidence/usage-observation.json`: unsupported language, `orchestration/retirements/e04-codenexus-direct/evidence/rollback-execution.json`: unsupported language, `orchestration/retirements/e04-codenexus-direct/evidence/compatibility-window.json`: unsupported language, `orchestration/retirements/e04-codenexus-direct/evidence/independent-approval.json`: unsupported language, `orchestration/retirements/e04-codenexus-direct/compatibility-retirement-ticket.json`: unsupported language, `orchestration/retirements/e04-codenexus-direct/evidence/registry-reconciliation.json`: unsupported language, `orchestration/retirements/e04-codenexus-direct/compatibility-retirement-manifest.json`: unsupported language, `orchestration/retirements/e04-codenexus-direct/compatibility-retirement-deletion-diff.json`: unsupported language, `orchestration/retirements/e04-codenexus-direct/gate-out/compatibility-retirement-decision.json`: unsupported language). - 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. - File history was not compared for this snapshot. - No AI review ran on this push. Everything above is deterministic analysis. ## 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.