perf(ci): bring the Numeric Ranges job from 5.6 min to about 1 min
Summary
The Numeric Ranges gate (fr) classifies every function parameter's declared type before it analyzes a function. src/cli-command-dispatch.test.ts typed its parameters with oxc-parser's Expression union — every AST kind, each a record of further such unions. That one file cost more analysis time than the rest of the repository combined. The reader now declares the node fields it reads.
Check numeric ranges also gets its own timeout-minutes: 3, so a range-analysis regression fails the lane instead of passing as slow green. The job keeps timeout-minutes: 20; a cold install runs in Setup toolchain and cannot trip the step budget.
Check numeric ranges step:
- Before: 245–455 s over six recent main runs, p50 ≈ 350 s (44140160645 = 335 s)
- After: 63 s (44177798121), 54 s (44168413376)
The job falls from 362 s to 87 s. Numeric Ranges is no longer the slowest CI job. Locally, the same command went 146 s → 21 s.
Validation
- Tested SHA: 90ba157 — run 44177798121 is green across Numeric Ranges, Coverage, Lint/Typecheck/Package, Integration Tests, and Repo Guards.
- Gate verdict unchanged:
frreports0 findingsand identical project-wide coverage counts before and after; a plantedconsole.assertviolation in a production file still fails the gate with exit 1. - Test verdict unchanged: the reader collects the same 18 command literals from
src/cli.ts, now pinned by a deep-equal. A reader that stops collecting fails it. Renaming a dispatch comparison insrc/cli.tsstill fails the test. - Risks: this file's own per-function detail shifts (two helpers move between "partially supported" and "unsupported"); no finding is gained or lost.
🤖 Generated with Claude Code