fix(init): force exit on failure paths so stdin closes cleanly

[betegon]

Summary

• sentry init calls process.exit after success to release Bun's fetch keep-alive sockets and the forwarded /dev/tty stream. Error paths skipped that call, so a failing init (e.g. Forbidden during project analysis) left the terminal hung.
• Wraps the command body in try/catch/finally so process.exit fires on every path — success, WizardError, or errors from arg parsing / findProjectsBySlug.

Context

Closes #798. The existing success-path process.exit(process.exitCode ?? 0) was added in #782 with the rationale that the libuv loop stays alive otherwise (Bun's global fetch dispatcher + the fresh /dev/tty forwarded by forwardFreshTtyToStdin). That rationale applies equally to error paths — runWizard throws WizardError from preflight, connection, and step-loop failures, and none of those hit the exit call.

Notes on the approach:

• The catch calls reportCliError directly. Normally Stricli's exceptionWhileRunningCommand handler (src/app.ts:327) reports to Sentry, but since we process.exit in finally the error never propagates to it — so we own reporting here.
• WizardError.rendered=true means clack already displayed the message; skipping the stderr write avoids double-printing. Other errors get an Error: … line matching src/app.ts:335.
• Tradeoff: autoAuthMiddleware no longer retries on AuthError thrown from init's pre-wizard steps. In practice the wizard owns its own auth via preflight; the only reachable path was findProjectsBySlug for the init <bare-slug> shape. Users hit with an auth error there will see a rendered message and can sentry login + retry.

Test plan

• bun test test/commands/init.test.ts — 42/42 pass (added 6 new error-path regressions; updated 4 pre-existing "throws" tests to the new "force-exits" behavior).
• bun test test/commands test/lib — 5453/5453 pass.
• bunx tsc --noEmit — no new errors (only pre-existing unrelated picomatch types issue).
• bunx ultracite check src/commands/init.ts test/commands/init.test.ts — clean.
• Manual repro: run sentry init in a project that triggers a preflight or workflow failure (e.g. revoked token → 403 on project analysis). Before: shell hangs after "Setup failed". After: shell returns to prompt with non-zero exit code.

[github-actions]

PR Preview Action v1.8.1
🚀 View preview at https://cli.sentry.dev/_preview/pr-802/
Built to branch gh-pages at 2026-04-21 16:17 UTC. Preview will be ready when the GitHub Pages deployment is complete.

[github-actions]

Codecov Results 📊

✅ 138 passed | Total: 138 | Pass Rate: 100% | Execution Time: 0ms

📊 Comparison with Base Branch

Metric	Change
Total Tests	—
Passed Tests	—
Failed Tests	—
Skipped Tests	—

✨ No test changes detected

All tests are passing successfully.

✅ Patch coverage is 100.00%. Project has 1754 uncovered lines.
✅ Project coverage is 95.65%. Comparing base (base) to head (head).

Coverage diff

@@            Coverage Diff             @@
##          main       #PR       +/-##
==========================================
+ Coverage    95.65%    95.65%        —%
==========================================
  Files          280       280         —
  Lines        40273     40284       +11
  Branches         0         0         —
==========================================
+ Hits         38518     38530       +12
- Misses        1755      1754        -1
- Partials         0         0         —

---

Generated by Codecov Action

[BYK]

Don't think this is the right approach. We should identify the dangling refs. Closing stdin should be the first step.