Distillation

Date: Sep 9, 2026

• 🔴 [requested-review] (09:30) User requested read-only analysis in /home/byk/.local/share/opencode/worktree/0e8c2f3bbe145a3280d6fb6ed900a5121f382cf0/toolkit-bridge-upgrade; explicitly instructed not to edit files or run broad tests.
• 🟡 (09:30) User asked to analyze packages/cli/src/lib/upgrade.ts, src/commands/cli/upgrade.ts, src/lib/version-check.ts, src/lib/release-notes.ts, and relevant tests, then return concise file/symbol recommendations.
• 🔴 (09:30) Required upgrade-source contract: resolve and retain an UpgradeSource for stable latest, explicit stable versions, rolling nightly, and pinned nightly.
• 🔴 (09:30) Required source order: getsentry/toolkit with cli@-prefixed tags first, then getsentry/cli with unprefixed tags.
• 🔴 (09:30) Required fallback behavior: fall back only on HTTP 404; non-404 HTTP errors and transport or malformed-response failures must stop resolution.
• 🔴 (09:30) Required short-circuit behavior: once a source succeeds, legacy must never be contacted.
• 🔴 (09:30) Package-manager stable upgrades must remain npm-based and require no GitHub source.
• 🔴 (09:30) Direct helpers may default to the primary source, while production standalone paths must explicitly pass the resolved source.
• 🟡 (09:30) User asked for the smallest type/signature changes needed and for exact regressions and compatibility concerns to be flagged.