feat(explain): add --limit so connections past the top 20 are readable - #2563
feat(explain): add --limit so connections past the top 20 are readable#2563lucadepascale wants to merge 1 commit into
Graphify — worth a look
Worth a look — the grounded gate found no coupling regressions or blocking issues, but 1 advisory finding(s) below merit a look before merge.
Details
Graphify reviewed this change.
Worth a look — the grounded gate found no coupling regressions or blocking issues, but 1 advisory finding(s) below merit a look before merge.
Graphify review — findings
This PR adds a --limit N option (also accepting --limit=N) to the graphify explain CLI command, letting users control how many connections are printed before the grouped-by-file summary, with 0 meaning print all and a default of 20. The change introduces a limit-parsing helper with validation for non-integer and negative values, applies the limit to both the connection list and the grouped-by-file summary, and updates the usage string and "more" message. A new test suite covers the default behavior, raising/lowering the cut, the 0 case, and the error paths, and the CHANGELOG notes the addition.
Worth a look
--limitwithout a value is silently ignored —graphify/cli.py:1465· Escalate · medium- agreed by 2 of 2 members but NOT verified (no proof, no reproducing execution) — consensus is not a verdict; needs human review
Analysis details — impact, health, verification
Impact & health
Graphify review
Impact — 416 functions depend on the 270 functions this change touches.
Health — this change adds coupling hotspots:
- worse:
dispatch_command()— 2 callers, 120 callees
Verification — 416 functions in the blast radius were not formally verified this run (proofs are advisory here).
Gate & verification
graphify gate
PASS — objectively clean (no health regressions, tests not run — proofs not run this pass (advisory)). Grounded, not self-assessed.
Advisory (not blocking):
- verification_scope: 387 function(s) in the blast radius were not formally verified this run