local-dev-setuplisted

# Local dev environment for noisy-coding contributors This skill lives in `.claude/skills/` — project scope, for people hacking on THIS repo. It is deliberately NOT in the plugin's `skills/` directory, so it never ships to end users. The full recipe with rationale is `docs/local-development.md` — read it when anything here surprises you. Quick path: ## 1. Dev daemon (port 7765; production keeps 8765–8767) ```sh scripts/dev_daemon.sh ``` Builds the dashboard if `dashboard/dist` is missing, then starts the listener from this checkout. Verify: `curl -s http://127.0.0.1:7765/status` returns JSON. Dashboard: <http://127.0.0.1:7765> — amber logo + LOCAL DEV badge. Run it in the background (`run_in_background`) and restart it after changing Python code; rebuild (`cd dashboard && npm run build`) after dashboard changes. ## 2. Session wiring — should already be in place - MCP is per contributor machine (LOCAL scope — a committed `.mcp.json` would be auto-loaded by the plugin and leak the dev server to end users): ```sh claude mcp add noisy-coding-dev --scope local \ --env NOISY_CODING_LISTENER_PORT=7765 -- uv run noisy-coding-mcp ``` Tools appear as `mcp__noisy-coding-dev__*` after a restart. - Hooks are committed to this repo, so normally there is nothing to do: `.claude/settings.json` → the five hooks duplicated with local commands (`NOISY_CODING_LISTENER_PORT=7765 python3 hooks/<script>.py`). They run IN ADDITION to the global production hooks — that i