[billyvg]

When an org runs out of Seer credits, Seer ends the run with failure_reason=out_of_credits (getsentry/seer#9242) or records pr_creation_error_code=out_of_credits on the repo's PR state (getsentry/seer#9268). Until now the UI showed those as generic failures ("This one is on us") next to a retry that fails the same way. This PR reads both fields, says the step stopped for credits, and makes its retry follow the credit check. It builds on #129545 (useSeerCreditCheck), #129551 (out-of-credits CTA), #129563 (agent chat gate), #129565 (autofix entry point gates) and #130463 (chat recheck), all merged.

This PR renders no out-of-credits CTA. The credit gates already show one on each surface: the alert at the top of the Autofix tab and drawer (its autofix-continue copy covers a run that stopped part way), the alert above the chat composer, and the muted alert in the issue sidebar. A stopped step or failed PR only gets a one-line status here.

A step that stopped for credits (root cause, plan, code changes, PR iteration):

• The Seer drawer cards and the chat autofix card keep what the step wrote before it stopped: its reasoning, the root cause's evidence and, for code changes, the partial diff. Seer's own error block is left out. The drawer cards draw that work the way their running state does, like the Seer Agent chat. Below that, one line says which step stopped. It's muted in the drawer and danger in the chat card, which matches each card's existing failure text. Partial code changes can't be copied as Markdown or turned into a PR.
• The issue sidebar previews say the step stopped for credits. A PR-iteration feedback item that stopped is marked failed, with out-of-credits copy.
• In agent chat, the run's last response replaces Seer's plain-text error block with a muted "Seer stopped because your organization is out of credits." Earlier reasoning and tool calls stay in the thinking block. feat(seer): Show the credits notice when a chat runs out mid-conversation #130463 rechecks credits when a run stops for them, so the alert above the composer comes up as well.

A PR create or push that failed for credits:

• The drawer's Pull Requests card keeps "Retry PR" for that repo and adds a line under the PRs saying it failed for credits. The chat PR card says the same instead of "This one is on us".
• The chat failure toast and the PR links bar tooltip use out-of-credits copy instead of the raw backend string.

A step or PR the backend refuses for credits. The gates' credit checks fail open and can be out of date, so the Autofix endpoint has the final say: it answers 402 with code: seer_out_of_credits. startStep and createPR then recheck every Seer credit check, so the gates bring up their CTA and disable their buttons. They toast out-of-credits copy for the step, or for the repo's PR, instead of the backend's detail. A refused kickoff no longer paints a failed run that says "This one is on us", since the start card offers the CTA.

	Before	After
Start Analysis, refused for credits
Yes, draft a PR, refused for credits

These use the real drawer and useExplorerAutofix, with the Autofix endpoint stubbed in the browser: it refuses with a 402 and code: seer_out_of_credits, and the credit check says the organization can pay until that refusal. Before is this branch without the commit that handles the refusal.

Retries follow the credit check. Each retry stays on screen. While the credit check says the org can't afford the operation, the retry is disabled, and its tooltip reads "Your organization does not have enough Seer credits for this." The check refetches on mount and window focus, so the retry turns back on once the org tops up. Until this mount's check answers, the retry stays disabled, even with an earlier answer cached, so it never flashes on. Only retries on screen for a credit failure run the check. Each retry checks its autofix action through #129565's useAutofixCreditCheck, so both gates read one action-to-operation map.

Retry	Where	Operation
Re-run, header Re-run step	Root cause card	autofix_root_cause
Re-run, header Re-run step	Plan card	autofix_solution
Re-run, header Re-run step	Code changes card	autofix_code_changes
Add context & retry, header Re-run step	Code changes card, iteration stopped	autofix_pr_iteration
Retry PR	Pull Requests card, inbox preview	autofix_open_pr
Try again	Chat autofix card	the step that stopped
Draft a pull request	Chat code changes card, after a PR failed for credits	autofix_open_pr

Decisions the spec doesn't cover, for review:

• The spec has no failure copy. The status lines keep the earlier headlines, one sentence each, and the tooltip is new.
• Without seer-credit-checks the hook reports enough credits, so a stopped step shows its retry enabled and the backend decides.
• Only retries of something that stopped for credits are gated here. Retries after other failures, and re-runs of finished steps, don't call the credit check. The chat card's "Draft a pull request" is the exception: feat(seer): Gate autofix entry points on Seer credits #129565 already holds it on autofix_open_pr for every run, so this PR only adds the tooltip when the earlier create failed for credits.
• On a drawer card that stopped for credits, the header Re-run step does what it does on a finished card: it opens the context prompt, or Seer chat where the card offers chat. On cards that failed for other reasons, it still shows nothing.
• A stopped PR iteration is retried through the PR feedback form. Since ref(seer): Stop gating PR iteration UI on its feature flags #129036 dropped the autofix-pr-iteration-manual gate, that retry is always there once the run has a PR. hideErroredPrIteration still hides CI-driven iterations that fail, whether or not they ran out of credits.
• The chat card's "Try again" sends a chat message, so the composer's agent_chat_message gate also applies to it. On a code changes card whose iteration stopped, it still asks Seer to retry the Code Changes step, as it does for other failures, but it waits for the autofix_pr_iteration check.
• The PR links bar has no retry and no status line. Its tooltip is the only status, and the composer's alert carries the CTA.

Location	Screenshot
Seer drawer › Code Changes, stopped for credits
Seer drawer › Code Changes, stopped for credits, after a top-up
Seer drawer › Code Changes, PR iteration stopped for credits
Seer drawer › Pull Requests, failed for credits
Seer Explorer › autofix card › Code Changes, stopped for credits
Seer Explorer › autofix card › Pull Request, failed for credits
Seer Explorer › conversation, run stopped for credits
Seer Explorer › PR links bar, failed for credits

The screenshots come from the stories. Members see "Contact Admin" only when their org can self-serve, so the two captures with a CTA used a self-serve subscription.

Fixes CW-2328

🤖 Generated with Claude Code

[linear-code]

CW-2328

[github-actions]

📊 Type Coverage Diff

Metric	Before	After	Delta
Coverage	96.03%	96.03%	±0%
Typed	142,321	142,430	🟢 +109
Untyped	5,890	5,893	🔴 +3

🔍 3 new type safety issues introduced

Non-null assertions (!) (1 new)

File	Line	Detail
static/app/components/seer/outOfCredits/messages.tsx	88	states[0]!

Type assertions (as) (2 new)

File	Line	Detail
static/app/components/events/autofix/useExplorerAutofix.tsx	343	`as

| null
| undefined` — `e as | {responseJSON?: {code?: unknown}; status?: number} | null | undefined` |

| static/app/components/seer/outOfCredits/__stories__/seerCreditCheckStub.tsx | 27 | as never — queryFn as never |

This is informational only and does not block the PR.

[github-actions]

Story previews

Preview the stories changed in this PR on the Vercel deployment:

• app/components/events/autofix/v3/codeChangesCard.stories.tsx
• app/components/events/autofix/v3/pullRequestsCard.stories.tsx
• app/components/events/autofix/v3/rootCauseCard.stories.tsx
• app/components/events/autofix/v3/solutionCard.stories.tsx
• app/components/seer/markdown/embeds/components/autofix.stories.tsx
• app/components/seer/markdown/seerMarkdown.mdx
• app/views/seerExplorer/components/chat/chatWindow.stories.tsx
• app/views/seerExplorer/components/prLinksBar.stories.tsx

_{Preview deployment: https://sentry-b96dhc9ms.sentry.dev}

[github-actions]

decision-model-linter

voice

static/app/components/events/autofix/v3/rootCauseCard.tsx

• warn miscapitalizesProductName = TRUE (0.64): Use the canonical spelling for this named Sentry product or feature. Leave generic descriptions lowercase and preserve package names and identifiers.

static/app/components/events/autofix/v3/solutionCard.tsx

• warn miscapitalizesProductName = TRUE (0.73): Use the canonical spelling for this named Sentry product or feature. Leave generic descriptions lowercase and preserve package names and identifiers.

_{decision-model-linter: 209 calls on 38 files, 545,564 input tokens, $0.023, model typesafe/jev-1.13-20260917}

[sentry]

Sentry Snapshot Testing

Name	Added	Removed	Changed	Renamed	Unchanged	Skipped	Status
sentry-frontend sentry-frontend	0	0	0	0	934	0	✅ Unchanged

⚙️ sentry-frontend Snapshot Settings

[srest2021]

Can we add out-of-credits error handling to startStep and createPR in useExplorerAutofix.tsx as well (doesn't have to be this PR)? These still show the generic toast.