Describe the situation. Verify the outcome.

Behavioral checks cross several queue operations to prove realistic user journeys: serialized ownership, dependency gates, atomic producer rejection, stale-reference-safe clearing, auto-run recovery, explicit hand-offs, independent queues, reprioritization, and the native no-bundler package entry.

Exact inventory

All 9 Behavioral checks.

Functional checks own focused feature transitions. These scenarios begin with a consumer situation and finish only after the complete externally observable outcome is verified.

serial jobs do not overlap before each owner releases the queue
reopening a dependency lets the next producer start buffered work in arrival order
a rejected producer batch leaves existing backlog runnable
clearing backlog detaches stale contents references
a default auto-run failure leaves later work recoverable
returned values and fulfilled promises wait for explicit hand-off
an occupied queue does not block work on another queue
pending work can be reprioritized before dispatch
given the native no-bundler entry when declared work runs then observable orders complete

Run this layer

Behavioral only, or the complete suite.

npm run test:behavioral
npm test