DeployCreatePage: private deploys + IP allow-list UI (Pro+)

[mastermanas805]

Summary

Track B for the private-deploy feature (Track A ships the backend in parallel). Adds an opt-in "Private deploy" toggle on /app/deployments and the privacy state + Pro+ inline editor on /app/deployments/:id. Hobby / free / anonymous see a feature-specific UpgradePromptCard for the new private_deploy key.

• New API helpers: createDeploy() and updateDeploymentAccess() lock the wire shape (private: boolean, allowed_ips: string[]) for both the agent prompt and the future PATCH path. DashboardDeployment gains private (defaults false) + allowed_ips (defaults []) so older API responses never silently inherit stale privacy state.
• IpAllowList (new reusable tag input): Enter / comma / space commits, Backspace-on-empty pops the last chip, × on each chip removes, loose IPv4 + IPv6 + CIDR regex gives red-border feedback on bogus entries (server has the real validator), 32-entry cap matches the backend.
• DeploymentsPage: Pro+ tier renders the PrivateDeployConfigurator (toggle + IP allow-list + PromptCard whose body mirrors createDeploy()'s wire shape — keeps the dashboard's read-only / agent-driven pattern). Hobby / free / anonymous render UpgradePromptCard feature="private_deploy".
• DeployDetailPage: header gains a private badge; PrivacyPanel surfaces the public / private state; Pro+ tier gets an inline editor (toggle + IpAllowList + save/cancel). The editor calls updateDeploymentAccess() and on 404 surfaces "edits pending backend" copy (Track A's PATCH is still rolling out) — no fake confirmation when the change didn't land.
• upgradeCopy.ts: new private_deploy key per U2 pattern.

Test plan

• npm test — 329 / 329 pass, 3 pre-existing skips (45 new tests added)
• npm run build clean
• IpAllowList unit tests: add/remove/Backspace/validate/max-32/disabled mode
• DeploymentsPage tier-gate + toggle behaviour tests
• DeployDetailPage privacy panel: public hint, private + allow-list display, edit flow, 404 hint, disabled save when private+empty
• createDeploy + updateDeploymentAccess contract tests (status codes 200/400/402/404, field names, URI encoding)

Backend assumptions (Track A)

• POST /deploy/new accepts { private?: boolean, allowed_ips?: string[] }
• GET /api/v1/deployments/:id returns { private: boolean, allowed_ips: string[] }
• PATCH /api/v1/deployments/:id with same body for updates (this PR returns 404 → friendly hint until shipped)
• 402 on hobby / anonymous / free with agent_action for upgrade
• 400 on invalid IPs / empty allowed_ips when private=true

🤖 Generated with Claude Code