@CryogenicPlanetchecks…cryo/scope-referenceid-heal-to-consumer-path → main3 files · +48 −10review: @shamsharoonupdated 1w agoFollow-up #2 to the incident hotfix #728 ("Re-introduce legacy-key self-heal scoped to the consumer-api-key path only").
Re-introduce the legacy-key self-heal that #728 deliberately dropped — but scoped to the dashboard consumer path only, never the OAuth /mcp path.
#728 reverted #721's unconditional referenceId: { not: null } from findExistingConsumerApiKey (it ran on the per-request OAuth bearer path and mass-deleted keys → reconnect outage). That left a // do NOT add referenceId here … self-heal must be scoped to the consumer-api-key path only (see follow-up) note. This PR is that follow-up.
findExistingConsumerApiKey takes a requireReferenceId flag; the filter is gated behind it (default false):
...(requireReferenceId ? { referenceId: { not: null } } : {})
consumerMiddleware (src/server/api/trpc.ts) → true: a legacy NULL-referenceId key is treated as "no key" → re-provisions → self-heals on dashboard access, where the user actually sees the new ck_*.resolve-bearer (OAuth /mcp) → false: never re-provisions on the per-request path — keeps #728's incident fix intact.Threaded through the React.cache memo as a distinct positional arg so true/false don't collide.
The OAuth /mcp path still passes false, so it behaves exactly as it does on main today — no re-provision, no churn. Only the dashboard middleware opts into the heal, and only there does the user receive the regenerated key. Paired with platform#10482 (follow-up #1: scopes the backend's createProjectApiKey soft-delete to its own kind), even the dashboard heal's re-provision never touches the OAuth INTERNAL_CONSUMER_MCP key.
main shows 0 new type errors from the 3 changed files.ensureConsumerProject callers confirmed correct; findExistingConsumerApiKey queries consumerApiKey (ck_), never the OAuth ak_.🤖 Generated with Claude Code
The latest updates on your projects. Learn more about Vercel for GitHub.
| Project | Deployment | Actions | Updated (UTC) |
|---|---|---|---|
| dashboard |  Ready | Preview, Comment | Jun 4, 2026 2:35am |