vercel-plugin-evallisted

# Plugin Eval Launch real Claude Code sessions with the plugin installed, monitor debug logs in real-time, and verify every hook fires correctly with proper dedup. ## DO NOT (Hard Rules) - **DO NOT** use `claude --print` or `-p` — hooks don't fire, no files created - **DO NOT** use `--dangerously-skip-permissions` - **DO NOT** create projects in `/tmp/` — always use `~/dev/vercel-plugin-testing/` - **DO NOT** manually wire hooks or create `settings.local.json` — use `npx add-plugin` - **DO NOT** set `CLAUDE_PLUGIN_ROOT` manually - **DO NOT** use `bash -c` in WezTerm — use `/bin/zsh -ic` - **DO NOT** use full path to claude — use the `x` alias - **DO NOT** write eval scripts — do everything as Bash tool calls in the conversation **Copy the exact commands below. Do not improvise.** ## Quick Start **Always append a timestamp** to directory names so reruns don't overwrite old projects: ```bash # 1. Create test dir & install plugin (with timestamp) TS=$(date +%Y%m%d-%H%M) SLUG="my-eval-$TS" mkdir -p ~/dev/vercel-plugin-testing/$SLUG cd ~/dev/vercel-plugin-testing/$SLUG npx add-plugin https://github.com/vercel/vercel-plugin -s project -y # 2. Launch session via WezTerm wezterm cli spawn --cwd /Users/johnlindquist/dev/vercel-plugin-testing/$SLUG -- /bin/zsh -ic \ "unset CLAUDECODE; VERCEL_PLUGIN_LOG_LEVEL=debug x '<PROMPT>' --settings .claude/settings.json; exec zsh" # 3. Find debug log (wait ~25s for session start) find ~/.claude/debug -name "*.txt" -mmin -2 -exec grep -