fix(cloudflare): use queue dev.id for consumer resource ID in local dev mode

In local dev mode, Queue resources return an empty string for `id`
(Cloudflare API ID) since no remote API call is made. When a Worker
has multiple eventSources, all QueueConsumers were derived as
`${queue.id}-consumer` which all resolved to "-consumer",
causing concurrent Promise.all writes to the same state file.

This led to corrupted JSON state files and silently broken queue
consumers — the Worker HTTP endpoint would respond normally but
queue messages were never consumed.

Fix: use `queue.dev.id` (the resource ID, e.g. "email-queue") in
local dev mode, which is always unique per queue.

Fixes #1363

Author: xiaoyu2er

alchemy/src/cloudflare/worker.ts

@@ -1563,7 +1563,14 @@ async function provisionResources<B extends Bindings>(
     input.eventSources
       ? Promise.all(
           input.eventSources.map(async (eventSource) => {
-            return await QueueConsumer(`${eventSource.queue.id}-consumer`, {
+            // In local dev mode, queue.id is "" (no Cloudflare API call).
+            // Use queue.dev.id (resource ID, e.g. "email-queue") to avoid
+            // all consumers colliding on the same "-consumer" resource ID.
+            // See: https://github.com/alchemy-run/alchemy/issues/1363
+            const queueConsumerId = options.local
+              ? eventSource.queue.dev?.id || eventSource.queue.id
+              : eventSource.queue.id;
+            return await QueueConsumer(`${queueConsumerId}-consumer`, {
               queue: eventSource.queue,
               scriptName: options.name,
               settings: eventSource.settings,