setuplisted

## Pre-computed context Installed CLI version: !`ctx7 --version 2>/dev/null || echo "not installed"` Latest published CLI version: !`npm view ctx7 version 2>/dev/null || echo "unknown (npm registry unreachable)"` MCP availability: check your own tool list — if `mcp__context7__resolve-library-id` / `mcp__context7__query-docs` are present, the Context7 MCP server is already configured. ## Purpose Bring the local environment to a working state for `/context7:lookup`. Two independent paths, either alone sufficient: the **CLI** (`ctx7` via npm) and the **Context7 MCP server** (configured by the consuming project). An optional `CONTEXT7_API_KEY` raises rate limits for both. Check-centric per the uniform contract: `check` inspects and reports, `apply` resolves what `check` found, and the CLI install is a distinct opt-in subaction. Idempotent and transparent: safe to rerun. Report what is already in place before touching anything, and when both paths are already working, confirm the verified state and make no changes. Action routing: no argument or `check` runs the check; `apply` runs the check first, then the guidance-only remediations (auth, MCP routing); `apply install-cli` additionally authorizes the global `ctx7` install/upgrade below. All actions are non-interactive when the action is given — never prompt. ## `check` (read-only) Work top-down from the pre-computed context and report a PASS/FAIL/INFO table with one remediation line per FAIL. Do not install, edit config,