ultrareview fails with "firestore: not found" on every attempt after credit top-up

Summary

/ultrareview consistently fails to start with a Firestore not-found error after a credit top-up that was made specifically to enable the feature. Three consecutive attempts all returned the same error within seconds of invocation.

Error message (verbatim, identical across all three attempts)

Ultrareview could not start the remote session: seed bundle: seed bundle import: failed to import files: error executing request: file not found: {"code":"not_found","message":"file to import not found: error retrieving file to import: firestore: not found"}

Steps to reproduce

1. Subscribe to Claude Code + top up extra usage credit specifically to use /ultrareview.
2. Inside a Claude Code session, type /ultrareview at the chat input.
3. Result: command flashes purple (registered), then local-command-stdout returns the above error within a couple of seconds.

Branch is committed and pushed to https://github.com/atreiou/globalsocials-club (main, HEAD af8f404). The branch is reachable via standard git operations from the same machine. No LFS objects, no submodules.

Repro frequency

3/3 attempts in a 10-minute window. Not transient.

Environment

• Claude Code 2.1.141
• Windows 10 Home 10.0.19045
• PowerShell shell, Git Bash via WSL-like bash for harness tool calls
• Repo size ~70MB working tree, ~75K LOC of in-scope code

Context that may matter

• The very first /ultrareview attempt earlier today failed silently (purple, no output) because the account was out of extra-usage credit at the time. Credit was then topped up, after which the command produces the Firestore error above instead of silently failing. It's possible the account state cached from the pre-top-up failure is what's now causing the Firestore lookup to miss.
• The repo has a docs/REVIEW_BRIEF.md that the cloud agent would read once the session starts — but the failure is at seed-bundle import, before any review-agent stage runs.

Impact

The user paid for extra-usage credit specifically to use this feature for a pre-launch code review (launch in ~one week). The feature is currently unusable.

Asks

1. Confirm whether this is a known issue / outage.
2. If account-state related, suggest a clear-and-retry path.
3. If a fix lands, confirm whether the consumed credit during the failed attempts is refunded.

🤖 Bug report drafted with Claude Code on the user's behalf.