# N5-L2 — negative: test/verify existing behavior (webhook failure handling)

> 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:** Moderate vocabulary (webhook, fails, logs, notification) but task is test/verify, not design
- **Correct non-trigger:** No new decision being made; testing existing notification failure handling within established 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)

Write tests verifying that when a webhook notification fails to deliver, the system logs it properly and doesn't silently drop the notification. Check the current failure handling in taskq/notifications.py.