Redesign setup skill to target complypack.yaml and cache warmup

[jpower432]

Problem / Motivation

The current /comply:mcp-setup skill (skills/mcp-setup/SKILL.md) guides users through configuring .mcp.json for Docker-based MCP server deployment. This is the wrong target for most users — they need a complypack.yaml that configures sources, schemas, and evaluators for both CLI and MCP use.

Issue #80 covers complypack init for YAML generation, but the setup flow is broader: it should also warm the cache (complypack pull) and verify the configuration works before the user starts working.

Proposed Solution

Redesign the setup skill to:

1. Generate complypack.yaml — interactive or flag-driven, listing available platforms from the schema index (this is Add complypack init command to generate complypack.yaml #80)
2. Warm the cache — run complypack pull to fetch OCI artifacts and compile schemas
3. Verify configuration — confirm catalogs loaded, schemas compiled, evaluators available
4. Optionally configure MCP — generate .mcp.json / claude_desktop_config.json pointing at the local binary (not Docker) if the user wants MCP integration

The skill should work for both CLI-only users and MCP users. MCP configuration becomes a final optional step, not the primary goal.

Acceptance Criteria

• Setup skill targets complypack.yaml generation as primary output
• Cache warmup is part of the setup flow
• Setup verifies the configuration works (catalogs load, schemas compile)
• MCP configuration is optional, not required
• Skill works with complypack init and complypack pull commands

Related

• Add complypack init command to generate complypack.yaml #80 — complypack init command (subset of this work)
• Persistent OCI cache with XDG_CACHE_HOME support #88 — Persistent cache with XDG_CACHE_HOME support