A complexity skill that stays report-only is exactly the kind of boring boundary I want named before the demo gets pretty. The retained material says it reports file and line findings, risk labels, and expected tests or benchmarks, but there is no actual repo inspection or sample run here, so the click is for the workflow shape more than the proof.