D1 database is visible in dashboard and d1 list but Wrangler returns errors 7404 and 10181

### What versions & operating system are you using?

Reported by: Jim Acquaviva

Operating system: Windows 11
Node.js: v24.19.0
npm: 11.17.0
Wrangler tested: 4.121.0 and 4.120.1

The same problem occurs with both Wrangler versions.

### Please provide a link to a minimal reproduction

https://github.com/cloudflare/workers-sdk/issues/10897

### Describe the Bug

I have an existing Cloudflare D1 database named bcb-inventory. It is visible in the Cloudflare dashboard, appears when I run `npx wrangler d1 list`, and works correctly through the D1 dashboard Console.

The database is also successfully bound to my currently active Worker as `DB`, and the live Worker continues to operate.

However, Wrangler cannot access this same database for migrations or validate it during a new deployment.

Running:

`npx wrangler d1 migrations list bcb-inventory --remote`

returns error 7404 stating that the database cannot be found.

Running:

`npm run deploy`

uploads the Worker assets successfully but fails while creating the new Worker version. It returns error 10181 stating that the D1 database UUID could not be found.

I confirmed all of the following:

* Wrangler is logged into the correct Cloudflare account.
* The OAuth login was completely refreshed with `wrangler logout` and `wrangler login`.
* The database UUID in `wrangler.jsonc` matches the UUID returned by `wrangler d1 list`.
* The binding name is `DB`.
* The database has no special jurisdiction; JSON output reports `"jurisdiction": null`.
* The problem occurs with Wrangler 4.121.0 and 4.120.1.
* The database remains accessible through the Cloudflare dashboard Console.
* The existing production Worker already has a functioning `DB → bcb-inventory` binding.
* The failed deployment does not create or activate a new Worker version.

This appears to be an inconsistency between the D1 dashboard/control plane and the API used by Wrangler.

### Please provide any relevant error logs

_No response_

Commencez par la reproduction minimale liée dans l’issue 10897 et examinez les commandes Wrangler `d1 migrations list --remote` et `npm run deploy`. Vérifiez comment l’UUID de la base de données provenant de `wrangler.jsonc` est transmis lors de la recherche des migrations et de la création de la version du Worker. Le travail est terminé lorsque la base de données existante `bcb-inventory` est trouvée de manière cohérente et que le déploiement ne renvoie plus les erreurs 7404 ou 10181.

Rédigé par le modèle d'indexation à partir du texte de l'issue.