init feature selection: pre-select features based on actual project usage

[sentry-junior]

Summary

The sentry init feature selection step pre-selects all features (Crons, AI Monitoring, Profiling, etc.) regardless of whether the project actually uses them. The wizard should analyze the project first and only pre-select features that are relevant to the detected stack.

Current behavior

All features are toggled on by default in the multi-select prompt, including Crons and AI Monitoring, even when the project has no scheduled jobs or AI model calls.

Gap

Pre-selecting irrelevant features adds noise to the generated config (unnecessary sample rates, DSN registrations) and gives the wrong impression that these features apply to every project. Users who don't notice the defaults end up with config for features they don't use.

Options

• Static heuristics: during the platform/framework detection step, check for signals like cron libraries (node-cron, APScheduler, Celery beat), AI SDKs (openai, anthropic, langchain), and only pre-select matching features
• AI analysis: since the wizard already uses AI to analyze the project, extend that pass to emit a features manifest that drives pre-selection
• Default none: ship with all features off by default and let users opt in

Recommendation

Use the existing AI analysis pass (or static heuristics as fallback) to drive pre-selection. Default to off for anything with no detected signal.

Action taken on behalf of Sergiy Dybskiy.