[kvlonge]

Why

Cold compilation repeatedly copies query trees and reconstructs compiler facts. Preserve the implemented improvements with representative, bounded-memory regression gates before further architectural work.

Changes

• Reuse bounded native query facts with conservative fallback, compact analysis results, and reduced validation allocations.
• Batch static interpolation/reference work and overlap independent rule preparation while preserving diagnostics and cache identities.
• Add dense 1k/3k/5k/10k all-rules guards, exact semantic/artifact fingerprints, and zero-cache-hit assertions.
• Enforce 14s/34s/55s/115s regression ceilings and a 4GiB no-swap CI limit; include the matrix in the required Verify gate.
• Keep experimental project-partitioning and prototype shortcuts out of this release.

Verification

• All four dense guards passed before and after tightening budgets.
• Hosted CI measured 11.92s at 1k and 30.18s at 3k; calibrated their ceilings to 14s/34s. Larger dense guards and other required suites passed. Log successful measurements for future calibration.
• uv sync --all-extras and make check-ci passed.
• Focused compiler, native-analysis, cache and real DuckDB integration checks passed at the implementation checkpoints.
• Full cross-platform and integration validation is gated by repository CI.