[billyvg]

Why?

The Seer auto-load modal didn't enforce the agreed limits: a minimum amount of $15, no $0 daily limit, and an unset daily limit meaning no cap. It let any amount above $0 through. Clearing the daily limit sent $0, which blocks all Seer usage, and there was no way to leave the limit unset.

The "Due now" preview also disagreed with the backend at exactly the threshold. The modal showed no charge, but the backend bills a load at or below the threshold. A new wallet starts at exactly the threshold, so turning auto-load on billed without showing "Due now".

How?

The modal reads the minimum amount and daily limit from the auto-load API instead of hardcoding them. It disables saving below either minimum and shows an inline message. An empty daily limit is saved as null, meaning no limit. The "Due now" preview now uses at-or-below the threshold, which matches when the backend bills the first load. The modal and wallet card now say auto-load triggers "at or below" the threshold rather than "below".

This depends on getsentry/getsentry#23167, which returns minTopUpCredits, minDailySpendCapCents and a nullable dailySpendCapCents. That change must deploy first.

Fixes REVENG-751

_{Generated with Claude Code}

[linear-code]

REVENG-733

REVENG-751

[github-actions]

Story previews

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

• gsApp/views/subscriptionPage/seerWallet/autoTopUpModal.stories.tsx

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

[billyvg]

QA

I tested this on a box devserver, running this branch's frontend with getsentry/getsentry#23167's backend. The org is a local mock org on a token-billed (am3_business_seer_credits) contract, with 500 of 500 included credits. That is exactly the 500-credit threshold, the state from REVENG-751. The "before" frames come from master (b1ed56cb6fe) on the same backend and data.

	Before	After
Turning on at the threshold
$14 amount, $0 daily limit
Wallet card, auto-load on

• Turning on at the threshold: Before, the modal said "drop below $5" and showed a plain "Turn on", but the backend bills $15 as soon as auto-load is on at this balance. It now says "at or below $5", shows "Due now $15.00", and the button reads "Turn on and pay $15.00 + tax". An unset daily limit shows "No limit" instead of $0.
• Minimums: A $14 amount and a $0 daily limit used to be accepted. They now show inline errors and disable the button. Clearing the daily limit removes its error and re-enables the button; I checked that in the DOM.
• Not covered: clicking "Turn on and pay" (off-cycle invoices are off locally, so the charge can't go through), dark theme, and narrow viewports. The "auto-load on" config was written straight through SeerWalletConfigService, because turning it on through the API would bill.

_{Generated with Claude Code}