Scale Canary (Performance & Resource Allocation Audit)

Audit code for scalability issues, performance bottlenecks, and resource leaks.

Auditing Categories

1. O(N^2) Complexity — nested loops over growable collections without indexing or caching (crashes at scale).
2. N+1 Database Queries — querying records in a loop instead of a batch JOIN or bulk prefetch.
3. Memory Bloat / Leaks — appending to global arrays/maps without clearing them → unbounded growth.
4. Blocking Main Loop — synchronous FS ops or CPU-heavy work on the main event thread (lag/hangs).
5. Resource Leakage — streams, connections, or handles left open without a finally close.

Per-ORM N+1 shapes, per-stack blocking patterns, and what NOT to flag: read references/checks.md before scanning.

Fix mode (choice-gated)

In Agent Context, after the report, present via ask_question:

• Apply safe optimizations: async-ify synchronous file ops; insert finally blocks for stream closing. Each fix: checkpoint (copy the touched file(s) aside, or use an isolated worktree — never git stash/git commit, which can hide or include unrelated staged/unstaged user work) → record a build+test BASELINE → apply → build + tests → auto-revert only if a NEW failure appeared versus the baseline.
• Let me pick: user selects specific optimizations.
• Report only: exit unchanged.

Grants & denials (CLASSIFY-BLOCK)

Output

| file:line | bottleneck | severity | finding | optimization plan |

Severity: CRITICAL (O(N^2) on user-facing API / unclosed file handles) · HIGH (N+1 query pattern / blocking main loop) · MEDIUM (unbounded cache growth) · LOW (minor efficiency suggestions)