feat(mcp): expose plan / verify on wizard-mcp-server

[kelsonpw]

Summary

Resurrects #258 onto current main. Exposes two new tools on the external wizard-mcp-server (the stdio MCP server invoked via amplitude-wizard mcp serve):

• plan_setup — wraps runPlan from agent-ops.ts. Detects framework, builds a structured WizardPlan (framework, sdk, intended file changes), persists it to disk under a fresh planId. Read-only; no files touched. The returned planId can be passed to apply (CLI: amplitude-wizard apply --plan-id <id> --yes) within 24h.
• verify_setup — wraps runVerify. Cheap, no-network check that the project has the SDK installed, an API key configured, and a detectable framework. Returns { outcome: "pass" | "fail", failures: [...] }.

Both wrap pure functions already on main (landed via #269, which includes the path.resolve fix).

What changed vs. #258

#258 also shipped list_projects, but that tool depended on runProjectsList / ProjectsListResult from #257 — which was closed, not merged. Rather than block on resurrecting #257, this PR drops list_projects from scope. It can be re-added once #257 is resurrected (path A).

plan_setup and verify_setup are otherwise unchanged from the original commit (8e31b67f on kelsonpw/wizard-mcp-plan-verify-list).

Test plan

• pnpm vitest run src/lib/__tests__/wizard-mcp-server.test.ts — 15 tests pass (5 new for plan_setup + verify_setup, no regressions on the 4 pre-existing tools)
• pnpm tsc --noEmit clean
• pnpm lint clean (only the pre-existing agent-interface.ts warning, unrelated)
• CI green
• Manual smoke: amplitude-wizard mcp serve lists plan_setup + verify_setup over stdio

Closes #258.

---

Note

Medium Risk
Adds new externally callable MCP tools that can create persisted setup plans and report verification failures; while intended to be read-only, it expands the agent-facing surface area and could impact how automation drives project setup flows.

Overview
Exposes two new MCP tools on wizard-mcp-server: plan_setup (wraps runPlan) and verify_setup (wraps runVerify), both accepting optional installDir (defaulting to process.cwd()) and returning JSON-wrapped results.

Updates unit tests to expect six registered tools and adds coverage that the new tool handlers forward arguments correctly, default installDir as expected, and that plan_setup’s description explicitly signals read-only / no file writes.

^{Reviewed by Cursor Bugbot for commit 6fc3d68. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

🧙 Wizard CI

Run the Wizard CI and test your changes against wizard-workbench example apps by replying with a GitHub comment using one of the following commands:

Test all apps:

• /wizard-ci all

Test all apps in a directory:

• /wizard-ci django
• /wizard-ci fastapi
• /wizard-ci flask
• /wizard-ci javascript-node
• /wizard-ci javascript-web
• /wizard-ci next-js
• /wizard-ci python
• /wizard-ci react-router
• /wizard-ci vue

Test an individual app:

• /wizard-ci django/django3-saas
• /wizard-ci fastapi/fastapi3-ai-saas
• /wizard-ci flask/flask3-social-media

Show more apps

• /wizard-ci javascript-node/express-todo
• /wizard-ci javascript-node/fastify-blog
• /wizard-ci javascript-node/hono-links
• /wizard-ci javascript-node/koa-notes
• /wizard-ci javascript-node/native-http-contacts
• /wizard-ci javascript-web/saas-dashboard
• /wizard-ci next-js/15-app-router-saas
• /wizard-ci next-js/15-app-router-todo
• /wizard-ci next-js/15-pages-router-saas
• /wizard-ci next-js/15-pages-router-todo
• /wizard-ci python/meeting-summarizer
• /wizard-ci react-router/react-router-v7-project
• /wizard-ci react-router/rrv7-starter
• /wizard-ci react-router/saas-template
• /wizard-ci react-router/shopper
• /wizard-ci vue/movies

Results will be posted here when complete.