Skip fully cutoff-excluded resolver candidates

[charliermarsh]

Summary

Warm locking with exclude-newer can encounter tens of thousands of registry versions whose files are all beyond the cutoff. Resolution intentionally treats those versions as nonexistent, but candidate selection previously materialized each lazy PrioritizedDist first, deserializing files and performing compatibility work only to discard the candidate.

This PR adds a cutoff-aware candidate iterator that checks archived upload times before materialization.

Performance

Workload	Wall time	Wall change (95% CI)	CPU time	CPU change (95% CI)
Transformers	343.0 → 315.1 ms	−8.1% [−9.2, −5.7]	378.8 → 352.8 ms	−6.9% [−7.4, −6.0]
Home Assistant	132.1 → 119.9 ms	−9.2% [−10.3, −6.8]	95.2 → 81.9 ms	−13.9% [−15.2, −12.4]
Warehouse	187.4 → 170.1 ms	−9.2% [−11.6, −7.1]	197.9 → 178.2 ms	−10.0% [−11.6, −9.0]
JupyterLab	117.4 → 110.4 ms	−6.0% [−8.1, −3.7]	62.9 → 57.4 ms	−8.7% [−9.6, −7.8]
Semantic Kernel	132.7 → 119.9 ms	−9.7% [−12.2, −6.8]	86.0 → 69.4 ms	−19.2% [−20.2, −18.7]
Geometric mean		−8.5% [−9.3, −7.4]		−11.9% [−12.4, −11.4]

[zanieb]

How does this interact with our error messages about excluded versions?

[codspeed-hq]

Merging this PR will improve performance by 26.48%

⚡ 6 improved benchmarks
✅ 15 untouched benchmarks
⏩ 6 skipped benchmarks¹

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
⚡	WallTime	resolve_warm_jupyter	38 ms	26.8 ms	+41.77%
⚡	WallTime	resolve_warm_airflow	382.9 ms	280.6 ms	+36.46%
⚡	Simulation	resolve_warm_airflow	501.3 ms	369.6 ms	+35.64%
⚡	Simulation	resolve_warm_jupyter	49.4 ms	37.6 ms	+31.29%
⚡	WallTime	resolve_warm_jupyter_universal	113.3 ms	103.2 ms	+9.77%
⚡	Simulation	resolve_warm_jupyter_universal	138.3 ms	127.7 ms	+8.23%

Tip

Curious why this is faster? Use the CodSpeed MCP and ask your agent.

---

_{Comparing charlie/codex-skip-cutoff-candidates (4f7ef45) with main (27ac822)}

Footnotes

1. 6 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[charliermarsh]

It shouldn't affect them. I believe we independently walk the unfiltered map to determine the available_versions and included_versions.