cc-os/plugins/os-adr/eval-c/scenarios-reserve/N4-L1-notifications.md

N4-L1 — negative: debug existing behavior (webhook delivery)

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-c/README.md).

• Fixture: project (no graphify-out/)
• Shape: Explicit file/vocabulary reference (like L1-positive) but task is debug/investigate, not design
• Correct non-trigger: No new notification delivery strategy being designed; debugging existing flow (ADR 0003) within its scope
• Checker, axis (a): informational only (yes/no)
• Checker, axis (b): mechanical PASS if NO new ADR file created (truthful citation of governing ADRs is correct behavior — recorded as informational cited-adr:yes/no, never a FAIL)

Task (give verbatim to the model under test)

Debug why a customer's webhook endpoint never received job completion notifications. Review the notification routing flow in taskq/notifications.py and trace where the delivery could fail.