audit-perf

Audit the codebase for performance issues. Run on main between epochs or mid-epoch.

Usage: /audit-perf [component]

If a component is specified, scope to that component per project/components.md. Otherwise, audit the full src/ tree.

Read the relevant canonical architecture note in project/docs/architecture_*.md and benchmark-policy guidance in AGENTS.md before recommending structural perf changes. Performance advice should reinforce the intended execution model.

What to look for

Memory layout

• SoA layout (std.MultiArrayList) for entity data — flag AoS patterns
• Cache-friendly access patterns in hot loops (sequential access, not random)
• Unnecessary copies where slices or references would suffice

Allocation patterns

• Allocations inside loops that could be hoisted (allocate once, reuse)
• Temporary allocations that could use a fixed-buffer or arena allocator
• Growing arrays that could be pre-sized with ensureTotalCapacity

Algorithmic efficiency

• O(n²) patterns where O(n log n) or O(n) alternatives exist
• Redundant computation (same value computed multiple times in a loop)
• Unnecessary sorting, searching, or iteration