archivist-performance-auditor

Identify runtime performance bottlenecks by auditing heavy imports, route shims, and root layouts to locate expensive render calculations and unbounded list rendering. The audit provides documented findings with evidence, recording results under docs/code-audits/reports/ without editing code.

A compile-time performance audit inspects unnecessary use client boundaries, lazy-loading boundaries, and local query scaling to find developer build bottlenecks. It reports evidence-based findings on cache behavior and heavy imports without modifying architecture or editing code.

Audit cache behavior and repeated renders without modifying code by generating a report-only analysis of runtime bottlenecks. The process documents findings with evidence under docs/code-audits/reports/, inspecting local query scaling and client boundaries while leaving architecture untouched.

Yes, you can use this performance audit for unbounded list rendering and heavy imports. It specifically targets these runtime and compile-time issues alongside route shims and local query scaling, providing documented evidence of bottlenecks without editing project code or architecture.

The limitation of an evidence-based performance audit that does not edit code is that it only provides documented findings and evidence of runtime bottlenecks. It does not fix heavy imports, client boundaries, or cache behavior, leaving architecture modifications entirely to the developer.

Compile-time bottlenecks occur when starter routes pull too much graph, creating heavy imports and unnecessary use client boundaries. An audit identifies these specific performance issues, documenting the runtime and cache behavior evidence without altering the codebase.