[nightly-telemetry] Drop native image paths from Sentry crashes

[r3dbars]

Summary

• Drop native Sentry debugImage.codeFile values before crash events leave the app.
• Drop native Sentry frame.package values instead of trying to sanitize them as text.
• Add a repo contract test so path-shaped native crash metadata stays out of future payloads.

Nightly evidence

Top candidate: current-release Sentry crash metadata privacy/debugging blind spot, score 92/100.

Evidence used:

• Sentry production issue APPLE-MACOS-1X appeared on transcripted@1.1.48 with 2 fatal events in the last 24h.
• The event looked like local build/smoke noise rather than a clean public-user crash, but native crash metadata still carried path-shaped frame/debug image fields.
• PostHog for 1.1.48 had launch/update/dictation coverage, but no matching workflow context that made this crash actionable.

Why this won:

• User pain/workflow distortion: 24/30
• Debugging/confusion severity: 25/25
• Current-release relevance: 15/15
• Small-patch safety: 14/15
• Privacy/payload confidence: 14/15

Why the next candidates lost:

• Home delete confirmation UX: real user-facing issue, but Fix dead Home "Delete meeting" confirmation #1126 is already open with the targeted fix and tests.
• Update install proof gap: useful telemetry gap, but weaker direct evidence than the current-release Sentry payload issue and a less obvious tiny patch.

Verification

• bash build-deps.sh --force
• bash build.sh --no-open
• bash run-tests.sh (5353 passed)
• bash scripts/dev/agent-preflight.sh Sources/Observability/CrashReporter.swift Tests/RepoCommandContractTests.swift
• codex-review --mode local (Swift changes built/tested; only noted unrelated untracked local Wrangler cache, not staged)

Privacy

No new telemetry. This removes path-shaped native crash fields from off-device Sentry payloads.