resolve-pluginslisted

# Resolve Plugins — Curate & Pin Curate Claude Code skill / MCP / hook picks against live upstream sources and write them to `.claude/settings.json`. Designed for two callers: standalone refresh (`/super-bootstrap:resolve-plugins`) and gated tier-2 curation (run by `/super-bootstrap` once seed docs are substantive). ## When to Use Caller: standalone refresh (`/super-bootstrap:resolve-plugins`) or gated tier-2 curation (run by `/super-bootstrap` once seed docs are substantive). Same execution path. --- ## Phase 1: Read inputs (or fail loud) Read inputs from files: `docs/techstack.md`, `docs/overview.md`, `.claude/settings.json` — caller passes no state. ### Required input `docs/techstack.md` — drives stack-matched picks. Read § Runtime, § Framework, § Key Dependencies. If missing → fail loud: > No `docs/techstack.md` found. `/super-bootstrap:resolve-plugins` reads stack signal from harness-seeded docs. Run `/super-bootstrap:harness-bootstrap` first to seed the harness, then re-run `/super-bootstrap:resolve-plugins` if you want a standalone refresh. Don't silently scan manifests — manifest detection is harness's job. Doing it here would duplicate logic. ### Workflow-tools signal (priority order) 1. **Existing `.claude/settings.json` pinned MCPs** — Notion MCP pinned → docs-heavy workflow. Linear MCP pinned → ticket-driven. Slack MCP pinned → team comm. Etc. Strong signal — user already explicitly enabled the tool. 2. **`<!-- harness-meta -->` block in `docs/overvie