Show sentry init's work before applying changes

[sentry-junior]

sentry init currently compresses meaningful setup work into terse, single-line task output. After feature selection it begins changing the project without first explaining the scope or value of those changes.

UX goal

The flow should make the automation feel legible and valuable, not opaque. Users should understand what Sentry is configuring, why each change matters, and what they will get from it. This is both a trust/UX concern and a product-marketing opportunity: the CLI should visibly demonstrate the work it saves.

Product direction

• Before mutation, preview the meaningful changes and outcomes for the selected features.
• Ask for approval before modifying files or configuration.
• During execution, show enough detail to communicate progress and value rather than reducing each operation to one generic task line.
• Prefer user-relevant outcomes over noisy implementation detail—for example, explain the capability being enabled alongside the project change that enables it.
• Finish with a clear summary of what was configured and any remaining user action.

The intent is not simply more verbose logs. The experience should tell a concise story: what will change, why it is useful, what is happening now, and what value was added.

Requested by David Cramer.

--

View Junior Session [Sentry]