perf

# perf ## Purpose Performance regression gate. Analyzes code changes for patterns that cause measurable slowdowns — N+1 queries, sync operations in async handlers, unbounded DB queries, missing indexes, memory leaks, and bundle bloat. Not a profiler — a gate. Finds performance bugs with measurable/estimated impact before production, so developers fix them at the cheapest point in the cycle. ## Triggers - `/rune perf` — manual invocation before commit - Called by `cook` (L1): Phase 5 quality gate - Called by `review` (L2): performance patterns detected in diff - Called by `deploy` (L2): pre-deploy regression check - Called by `audit` (L2): performance health dimension ## Calls (outbound) - `scout` (L2): find hotpath files and identify framework in use - `browser-pilot` (L3): run Lighthouse / Core Web Vitals for frontend projects - `verification` (L3): run benchmark scripts if configured (e.g. `npm run bench`) - `design` (L2): when Lighthouse Accessibility BLOCK — design system may lack a11y foundation ## Called By (inbound) - `cook` (L1): Phase 5 quality gate before PR - `audit` (L2): performance dimension delegation - `review` (L2): performance patterns detected in diff - `deploy` (L2): pre-deploy perf regression check - `adversary` (L2): scalability stress test when bottleneck patterns detected in plan ## References - `references/cost-reference.md` — Cost priority hierarchy, quick wins checklist, instance right-sizing, data transfer traps, serverless optimization, ...