Time compiler boundaries
Source reads, graph discovery, TypeScript parse, normalization, compile/transform, render, and write remain separately visible.
COMPILER SCALE · BROWSER PARITY · COMPLETE ATTRIBUTION
Kudzu now keeps compiler phase, incremental equivalence, failure recovery, large-list browser behavior, and AI attribution inside maintained executable gates.
PRODUCTION EVIDENCE
Source reads, graph discovery, TypeScript parse, normalization, compile/transform, render, and write remain separately visible.
Every changed-source incremental deploy must match a clean build byte-for-byte while touching only its affected route.
Invalid clean and retained-session builds preserve output and recover to the expected digest after source restoration.
The 10,000-item pagination route proves keyboard navigation, focus, bounded DOM, released state, and static exclusion.
Missing AI usage records mark the run incomplete and withhold cost-per-success claims instead of manufacturing zero cost.
The full 10,000-route compiler run remains pending separately provisioned hardware; projections do not count as acceptance.
UPGRADE
npm install @kudzujs/core@^0.16.15