scale-canary

Scale Canary (Performance & Resource Allocation Audit)

Language: Generate EVERYTHING at runtime in the user's language — questions, answer options, menu labels, recommendations, report narrative. Detect from their messages; never default to English just because this file is English. English is allowed only for technical terms: commands, paths, code identifiers, severity labels (CRITICAL/HIGH/MEDIUM/LOW), and tier names (Light/Standard/Heavy).

Config reads — every config key, always the CASCADE, never the bare project file: ~/.claude/.coalmine.json first, then the project config (own agent dir → other known agent dirs → legacy <gitroot>/.coalmine.json), project wins per key. A bare project read is ABSENT on a machine configured only globally, so it silently yields defaults.

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 (git stash/commit in a git repo; else copy the file aside — never assume git) → apply → build + tests → auto-revert if newly red.
• Let me pick: user selects specific optimizations.
• Report only: exit unchanged.

Grants & denials (CLASSIFY-BLOCK)

class	step it powers	grant	on denial
read	scan loops/queries/caches for the categories above	Read·Grep·Glob	refuse that file, name it — never a clean bill
write	Fix mode's safe-optimization apply, incl. checkpoint → build+tests → auto-revert if newly red	Edit·Bash (checkpoint/build/revert need exec)	report the fix as NOT applied AND the checkpoint/revert as NOT available, never claim done