fix(init): require explicit zero workflow exit

[betegon]

Summary

Make sentry init accept a terminal workflow result as successful only when it explicitly reports status: "success" and result.exitCode: 0.

Previously, a successful response with no result or no exitCode passed the truthiness check and could print the success handoff with process exit 0. The CLI now treats that as malformed, surfaces a specific WizardError, and exits nonzero. Existing nonzero workflow-to-CLI exit mappings are unchanged.

This makes the process exit status a reliable black-box signal for the init smoke harness.

Compatibility

This intentionally stops accepting terminal success payloads that omit exitCode. The current wizard success output already returns exitCode: 0.

The draft #1406 also touches handleFinalResult; merge order will require rebasing whichever PR lands second.

Test plan

• focused wizard runner tests: 74 passed
• CLI typecheck
• Biome on the three changed files
• git diff --check
• native darwin-arm64 binary build
• real Express init against the local candidate API: exit 0
• invalid OpenRouter credential: CLI exit 61 and smoke harness exit 1

Rollout

The paired API-owned smoke is getsentry/cli-init-api#249. Once this lands, bump its pinned CLI SHA so malformed successful workflow responses cannot produce a false-green smoke result.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
cli	Ready	Preview	Aug 21, 2026 12:30pm