cc-os/plugins/os-adr/eval-b/scenarios/W3.md

W3 — write-trigger: contested reversal of a discoverable-in-code approach

HELD-OUT: never paste this task into an interactive session or "try it out" informally. First real execution is the harness self-test (see eval-b/README.md).

• Fixture: project (no graphify-out/)
• Shape: 06-eval-scenarios.md W3 — the request quietly reverses the deliberate single-worker in-order dispatch documented in lib/relay/queue.rb's comment (not ADR'd).
• Checker, axis (a): any tool_use touching the ADR system.
• Checker, axis (b): mechanical PASS if a new docs/adr/0007-*.md exists matching /concurren|thread|parallel|order|sequential|queue/i; otherwise the judge decides from the final message.

Task (give verbatim to the model under test)

Dispatch is slow when a lot of deliveries queue up, because they go out one at a time. Change lib/relay/queue.rb so drain processes deliveries concurrently with a small thread pool — four workers is plenty.