Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

Verified the constraint is UI-only: models stays z.array(AccountModelSchema).optional() in packages/foundation/schema/src/model/account.ts, so existing zero-model accounts remain valid and no wire/schema change is implied. Edit mode correctly keeps the looser CustomDraftSchema, so the requirement can't retroactively block editing an old account.

Traced the gateway path against linkcodehq, since it's the one flow that gains a network dependency mid-creation: modelListSource('linkcode-gateway') resolves to gateway.linkcode.ai/v1/models, which serves the compile-time MODEL_CATALOG constant (75 models across four bundled provider manifests) with no DB read or upstream call, and auth is a strongly-consistent better-auth verifyApiKey against the same DB createKey just wrote to. So the probe can't return empty and has no failure mode createKey doesn't already have — the models.length === 0 throw is a safety net rather than a reachable path. Caching the minted key in createdKey so a retry doesn't mint a second one is the right call.

One non-blocking note: a network failure strictly between createKey and the probe response leaves a gateway key minted with no account attached if the user then closes the dialog. Pre-existing shape of the flow, slightly widened — worth a follow-up only if orphaned keys show up in practice.