fix: remaining npm→pnpm gaps + dockerignore for pnpm symlinks

- container/.dockerignore (new): exclude agent-runner/node_modules and
  agent-runner/dist so COPY agent-runner/ ./ doesn't clobber the
  pnpm-installed node_modules with host directories. Under npm's flat
  layout this was forgiving; under pnpm's symlink layout it's a hard
  conflict (overlay2 cannot copy onto a symlink target).
- setup/{groups,service}.ts: execSync('pnpm run build') not npm.
- setup/index.ts: usage string.
- scripts/*.ts: usage comments + seed-discord final log.
- .claude/settings.json: permission allowlist entries.
- .claude/skills/{add-whatsapp-v2,add-dashboard}/SKILL.md: docs.
- container/skills/{frontend-engineer,vercel-cli,self-customize}/SKILL.md:
  agent-facing docs still told the container agent to run npm.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

container/.dockerignore

@@ -0,0 +1,2 @@
+agent-runner/node_modules
+agent-runner/dist

container/skills/frontend-engineer/SKILL.md

@@ -66,7 +66,7 @@ Every frontend task follows this sequence. Do not skip steps.
 Run the build and fix ALL errors:
 
 ```bash
-npm run build 2>&1
+pnpm run build 2>&1
 ```
 
 If it fails, **fix it**. Do not deploy broken builds. Do not disable ESLint rules or TypeScript checks to make it pass.
@@ -76,7 +76,7 @@ If it fails, **fix it**. Do not deploy broken builds. Do not disable ESLint rule
 Start the dev server and test in a real browser:
 
 ```bash
-npm run dev &
+pnpm run dev &
 DEV_PID=$!
 sleep 3
 ```

container/skills/self-customize/SKILL.md

@@ -87,4 +87,4 @@ User: "Can you transcribe audio?"
 
 - **The change is for a one-off task** — just do it in your workspace, don't modify the container
 - **The request is ambiguous** — ask the user what they actually need before spinning up builders or requesting installs
-- **You don't know if it will work** — prototype in your workspace first (`npm install` in `/workspace/agent/`), then promote to container-level install if it proves useful
+- **You don't know if it will work** — prototype in your workspace first (`pnpm install` in `/workspace/agent/`), then promote to container-level install if it proves useful

container/skills/vercel-cli/SKILL.md

@@ -117,7 +117,7 @@ After sending, tell the user you've handed it off and will share the result when
 
 ## Best Practices
 
-- Run `npm run build` locally before deploying to catch build errors early
+- Run `pnpm run build` locally before deploying to catch build errors early
 - Use `--cwd` instead of `cd` to keep your working directory stable
 - For Next.js projects, `vercel deploy` auto-detects the framework — no extra config needed
 - Use `vercel.json` only when you need custom build settings, rewrites, or headers