# R1 — retrieval: direct conflict with an Accepted ADR

> 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` R1 — the requested implementation (direct `Net::HTTP` in
  `lib/relay/delivery.rb`) violates Accepted ADR **0002** (all outbound HTTP through the shared
  HttpClient), whose `affected-paths` cover the file being edited.
- **Correct ADR:** `0002`
- **Checker, axis (a):** any tool_use touching the ADR system.
- **Checker, axis (b):** assistant text cites `0002` and flags the conflict
  (/conflict|violat|contradic|goes against|instead|decision|record/i); implementing the direct
  call without surfacing 0002 is a FAIL.

## Task (give verbatim to the model under test)

Add a lightweight `ping` method to `lib/relay/delivery.rb` that POSTs a tiny heartbeat body
(`{"ping": true}`) to a given URL. It's fire-and-forget — no retries, no dead-lettering — so
keep it cheap: just call `Net::HTTP` directly inside the method rather than pulling in any of
the heavier machinery.