Tip builds are published without the Sentry SDK linked

[baron]

Impact

Official Tip builds cannot send crash, app-hang, or performance telemetry because the Sentry SDK is not linked.

Reproduction

1. Install the latest Tip build.
2. Open Settings → General → Telemetry.
3. Observe: “Telemetry is inactive in this build because the Sentry SDK is not linked.”

Reproduced with RepoPrompt CE 1.0.28 (29.8.98).

Expected behavior

Official Tip builds should include the same privacy-gated Sentry support as stable releases.

Confirmed evidence

The public artifact manifest for build 29.8.98 records:

bundle.telemetry_enabled: false

Package.swift links Sentry only when REPOPROMPT_ENABLE_SENTRY=1. The stable release pipeline enables this during staging, injects the protected DSN during signing, and uploads dSYMs. The Tip workflow currently omits those steps, and its environment has no Sentry configuration.

This has been present since the Tip workflow was introduced rather than being a recent SDK regression.

Acceptance criteria

• Official Tip artifacts link the Sentry SDK.
• The DSN is injected only during the protected signing stage.
• Tip dSYMs are preserved and uploaded for symbolication.
• Artifact manifests report telemetry as enabled without exposing configuration values.
• Release-tooling coverage prevents Tip and stable telemetry configuration from drifting.
• Existing user opt-out and process kill-switch behavior remains unchanged.