feat(next): accept Promise<Queue[]> for queues

[omarzeineddine-ai]

Problem

Closes #46

The Next.js adapter only accepted queues: Queue[]. Apps that collect their queues asynchronously (the issue author has 40+ queues behind an async helper) had no way to pass them without blocking module evaluation.

Solution

queues now also accepts Promise<Queue[]>:

export const { GET, POST, PUT, PATCH, DELETE } = workbench({
  queues: loadQueues(), // Promise<Queue[]>
  basePath: "/admin/jobs",
});

• Sync usage is unchanged — the handler is still built eagerly, exactly as before.
• With a promise, the fetch handler is built once the promise resolves; requests arriving earlier await it.
• A rejected queues promise surfaces on each request (Next renders a 500) instead of becoming an unhandled rejection that can take the server down before any request lands.

Tests

Added packages/next/src/index.test.ts covering sync queues, promised queues, single resolution across handlers/requests, and rejection behavior. Verified with bun test, tsc --noEmit, tsup build, and biome lint in packages/next.

[vercel]

@omarzeineddine-ai is attempting to deploy a commit to the Pontus Abrahamsson's projects Team on Vercel.

A member of the Team first needs to authorize it.