fix(setup): agent-first `next:` — open a coding-agent session and keep building

Merged
TO
3mo ago
+20-4

Tony's ask: after setup, the next step shown should be "open a coding-agent session and keep on building" — the agents now know InstaCloud (skill + MCP) and drive insta themselves (project create/link, deploys, login via device flow), so pointing the human at raw CLI commands undersells what setup just did.

  • logged-in: next: open a coding-agent session in your app directory and keep building — your agents know InstaCloud now
  • logged-out: same + (they will walk you through \insta login` when it is needed)`

Output-pinning test updated. No command/flag surface change. Gate: typecheck clean, 478/478 tests.

🤖 Generated with Claude Code

Summary by cubic

Makes setup’s “next” guidance agent-first: instead of CLI commands, we tell users to open a coding-agent session. Previously: logged-in saw “run insta project create…”, logged-out saw “insta login then create…”. Now: both see “open a coding-agent session…”, and logged-out users are told agents will guide device-flow login.

  • Updated src/commands/setup.ts to emit agent-first messages; logged-out includes a device-flow login note, logged-in omits any login clause.
  • Updated test/setup-agent.test.ts to pin both logged-out and logged-in messages; removed old expectations.
  • No command or flag changes; behavior change is console output only.