fix: ensure bounds vmaps properly and behaves correctly within JIT

[beckermr]

As it says on the tin...

[codspeed-hq]

Merging this PR will improve performance by 39.1%

⚠️ Unknown Walltime execution environment detected

Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.

For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.

⚠️ Different runtime environments detected

Some benchmarks with significant performance changes were compared across different runtime environments,
which may affect the accuracy of the results.

Open the report in CodSpeed to investigate

⚡ 2 improved benchmarks
✅ 34 untouched benchmarks

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
⚡	WallTime	test_benchmarks_lanczos_interp[xval-conserve_dc-run]	141.6 µs	105.3 µs	+34.46%
⚡	WallTime	test_benchmark_moffat_init[run]	71.4 µs	49.6 µs	+43.91%

Tip

Curious why this is faster? Comment @codspeedbot explain why this is faster on this PR, or directly use the CodSpeed MCP with your agent.

---

_{Comparing bounds-fix-again (0774b6a) with typing-inits-cleanup (db83109)}

[beckermr]

closing in favor of #250