fix(telemetry): set sentry.org tag in issue explain and plan commands

The issue explain and issue plan commands never called setOrgProjectContext()
after resolving the org, so SeerError events captured to Sentry were missing
the sentry.org tag. This made it impossible to filter or group Seer paywall
errors by customer org in dashboards.

Add setContext([org], []) right after resolveOrgAndIssueId() returns and
before the Seer API call that may throw, ensuring the tag is set even when
the command fails with a SeerError.

Author: BYK

src/commands/issue/explain.ts

@@ -74,7 +74,7 @@ export const explainCommand = buildCommand({
   },
   async *func(this: SentryContext, flags: ExplainFlags, issueArg: string) {
     applyFreshFlag(flags);
-    const { cwd } = this;
+    const { cwd, setContext } = this;
 
     // Declare org outside try block so it's accessible in catch for error messages
     let resolvedOrg: string | undefined;
@@ -88,6 +88,9 @@ export const explainCommand = buildCommand({
       });
       resolvedOrg = org;
 
+      // Set telemetry context so SeerError events carry the org tag
+      setContext([org], []);
+
       // Ensure root cause analysis exists (triggers if needed)
       const state = await ensureRootCauseAnalysis({
         org,

src/commands/issue/plan.ts

@@ -193,7 +193,7 @@ export const planCommand = buildCommand({
   },
   async *func(this: SentryContext, flags: PlanFlags, issueArg: string) {
     applyFreshFlag(flags);
-    const { cwd } = this;
+    const { cwd, setContext } = this;
 
     // Declare org outside try block so it's accessible in catch for error messages
     let resolvedOrg: string | undefined;
@@ -207,6 +207,9 @@ export const planCommand = buildCommand({
       });
       resolvedOrg = org;
 
+      // Set telemetry context so SeerError events carry the org tag
+      setContext([org], []);
+
       // Ensure root cause analysis exists (runs explain if needed)
       const state = await ensureRootCauseAnalysis({
         org,