mcp: create_deploy gains private + allowed_ips for Pro-tier private deploys (v0.10.0)

[mastermanas805]

Summary

Track C of the private-deploys feature (pairs with Track A's backend on
api/internal/handlers/deploy.go). Extends the MCP create_deploy tool
with two optional fields so AI coding agents can spin up private apps
without touching the dashboard.

• private: boolean — restrict the deploy to IPs in allowed_ips
• allowed_ips: string[] — IP / CIDR allowlist (["1.2.3.4", "10.0.0.0/8"])
• Forwarded to POST /deploy/new as multipart form fields
• get_deployment + list_deployments surface private + allowed_ips
  back to the agent
• Tier-gate copy in the tool description: Pro+ required; hobby returns 402
  with agent_action

Bumps version to 0.10.0 (additive feature, no breaking changes).

Test plan

• npm test — all 10 tests pass (7 pre-existing + 3 new):
  • tools/list advertises private (boolean) + allowed_ips (array)
  • create_deploy description includes the Pro-tier gate note
  • create_deploy accepts { private: true, allowed_ips: [...] } and forwards through (no Zod rejection)
• npm run build — clean TypeScript compile
• Wire-level smoke test against Track A's /deploy/new once that PR lands

Coordination with Track A

Track A is shipping the backend in parallel. The shared contract is:

POST /deploy/new
  private?: boolean
  allowed_ips?: string[]
  → 402 on hobby with agent_action
  → 400 on validation failures

If Track A renames allowed_ips → allowed_cidrs, reconcile post-merge
with a one-line schema rename in src/index.ts and the
form.append("allowed_ips", …) line in src/client.ts. The MCP tool
description references "IPs" not "CIDRs"; minor copy fix accompanies that
rename. This assumption is documented in the inline JSDoc on both
CreateDeployParams and Deployment.

Out of scope (flagged for the operator)

• npm publish skipped. NPM_TOKEN is still pending operator rotation
  (task v0.9.0 — add create_deploy + 4 deploy management tools #4). When the operator rotates it, run the existing
  prepublishOnly → npm publish flow. The version is already bumped to
  0.10.0.

Lockfile note

package-lock.json also refreshed — it was stale (carried the old
@instant/mcp name from before the instanode-mcp rename landed). The
diff is a metadata correction, not a dep change.

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