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

@@ -1363,7 +1363,14 @@ async function provisionResources<B extends Bindings>(
       input.eventSources
         ? Promise.all(
             input.eventSources.map(async (eventSource) => {
-              return await QueueConsumer(`${eventSource.queue.id}-consumer`, {
+              // Use dev.id (resource ID, e.g. "email-queue") in local dev mode
+              // instead of queue.id (Cloudflare API ID, empty "" in dev mode).
+              // Without this, all consumers collide on the same resource ID "-consumer",
+              // causing concurrent writes to the same state file.
+              const queueId = options.local
+                ? (eventSource.queue.dev?.id || eventSource.queue.id)
+                : eventSource.queue.id;
+              return await QueueConsumer(`${queueId}-consumer`, {
                 queue: eventSource.queue,
                 scriptName: options.name,
                 settings: eventSource.settings,