CI Environment Notice & Benchmark Methodology
These latency benchmarks run automatically on shared GitHub Actions runners under virtualized CPU scheduling and thermal contention.
Consequently, the raw numbers recorded here are considerably slower than real-world developer workstations (e.g. ~83 ms on M3 Air).
The primary purpose of this telemetry is relative historical tracking—safeguarding against architectural regressions over time across commits—rather than establishing absolute execution speed.