addlightness-benchlisted

# /addlightness-bench -- before/after performance benchmark Time two runnable commands head-to-head and report whether the difference is **real** -- not just noise. This is the **measurement** half of addlightness; it does not trim code (`/addlightness`) and does not measure static weight (`/addlightness-review`). ## Scope - Benchmark ONLY. No edits, no weight metrics, no refactoring. - Input is two commands you can actually run; output is a timing comparison with a significance verdict. - If the user has not trimmed anything yet, point them at `/addlightness`. If they want code-weight numbers (LOC/complexity), point them at `/addlightness-review`. ## Inputs The user supplies **two runnable commands**: a *before* command and an *after* command. Read trailing args / the request as exactly that pair. - If they hand you two snapshot files instead of commands, ask for (or infer) the command that runs each -- e.g. `node old.js` vs `node new.js`, `python3 before.py` vs `python3 after.py`. - Both commands must do the **same work** on the **same input** -- otherwise the comparison is meaningless. State the assumption if you have to guess. - Quote each command so the harness receives it as one argument. ## How to run Call the benchmark harness once: ```bash "${CLAUDE_PLUGIN_ROOT}/scripts/benchmark.sh" \ --runs 10 --warmup 3 \ --before '<before-command>' \ --after '<after-command>' ``` It uses `hyperfine` when present and falls back to a `date`+`awk` timing