fix: terse success output for integration/cloud connect

[claude]

Requested by boris · Slack thread

Before

Connecting an integration or cloud account with credentials dumped the entire API response object to the terminal — every field, including token/cipher metadata:

$ polylane integration connect --type axiom --region us-east-1 --api-token xaat-...
id              int_9f2c81a4b7d34e0f8a6c5d2e1b0a9f8e
workspaceId     ws_1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d
name            Axiom
installationId  ...
type            axiom
metadata        {"type":"axiom","region":"us-east-1","apiToken":"xaat-...","notifierId":"..."}
createdBy       usr_...
...20 more lines...

After

$ polylane integration connect --type axiom --region us-east-1 --api-token xaat-...
✓ Axiom connected

Cloud accounts print the same one-liner already used by the browser-wait flows:

$ polylane cloud connect --provider fly --token ...
✓ Connected: my-org (my-org)

--output json (and piped output) still emits the raw response object unchanged.

How

Both integration connect and cloud connect get a small printConnectSuccess helper: JSON mode delegates to formatOutput as before; the human path writes the same ✓ … connected line the existing browser-completion flows already print (stderr, matching in-file convention). Covers every synchronous connect path:

• Integrations: Datadog, Honeycomb, Axiom, Better Stack, Devin, Cursor, Factory, MCP (direct/bearer)
• Cloud accounts: Cloudflare, Fly.io, Render, Modal, Kubernetes, PlanetScale (service token)

Cloud connect failures (partial multi-account connects) are now printed as plain Failed to connect <account>: <message> lines instead of pointing at a "failures" key in the dump. Browser-based flows (GitHub, Slack, Sentry, MCP OAuth, AWS, Vercel, Supabase, PlanetScale OAuth) already printed terse confirmations and are untouched.

Note for reviewers: two parallel PRs touch the same CLI connect flows (back-navigation in prompts, and token-permission guidance before the paste prompt) — expect possible merge conflicts in these files.

🤖 Generated with Claude Code

https://claude.ai/code/session_013Eaq5cSYopxj9cj1mq78vt

---

Generated by Claude Code

[polylane]

Warning

Polylane could not verify the production impact of this pull request.

Checked both changed files — the CLI is an npm package, not a deployed worker, so no production resource runs this code. JSON output is unchanged; only human-readable terminal output moves to terse success lines.

View the full analysis →

Polylane could not find the cloud resources this repository manages, so this review looked at the entire cloud account. Connect this repository to its resources and the next review will focus on exactly what this code deploys to.

_{Polylane analysed 67007f6 for production impact.}