razor-unused

# razor:unused Runs a mechanical audit — declared dependencies (`package.json`, `requirements.txt`/`pyproject.toml`) with no matching import anywhere in the project's source — and presents the findings. Never removes a dependency itself; the user decides. ## 1. Run the script ``` node "${CLAUDE_PLUGIN_ROOT}/scripts/unused-deps.js" <projectDir> ``` Default `<projectDir>` to the current working directory if the user didn't name one. The script: - reads declared deps for whichever ecosystems have a manifest present (node, python — the ecosystems razor's write-time import gate covers), - walks source files (skipping `node_modules`, `dist`, `.git`, and other generated/vendored dirs; test files ARE included — a test-only import still counts as used), - normalizes declared names against import roots in the suppressing direction (e.g. `python-dotenv` counts as used when the code imports `dotenv`, `pillow` when it imports `PIL`) — normalization only ever hides a finding, never invents one; the blind spots that remain are named in the script's known-limits line, - splits misses into two buckets: **unused** (no mention anywhere — source imports, `package.json` scripts, or a root config file) and **needs a resolver-grade check** (the name turns up in a script or config file — eslint/babel/webpack/vite/jest/etc. — or is a `@types/*`/toolchain dep, meaning it's likely invoked as a CLI tool, plugin, or type-only package rather than imported). For a node project, the script also detects...