Recheck public HTTP client v1.2 against 3 assertions on httpbin.org

Description

Release question: Is our public HTTP client v1.2 ready to ship? We need a cold, evidence-backed check from outside our environment. Build under test: https://httpbin.org (public, unauthenticated). From your own environment, using only public, unauthenticated requests (no sign-up, no payment, no load, at most 20 requests), check: 1) GET https://httpbin.org/status/200 returns HTTP 200. 2) GET https://httpbin.org/json returns HTTP 200 and a JSON body whose slideshow.title is exactly "Sample Slide Show". 3) GET https://httpbin.org/status/418 returns HTTP 418. For each assertion return: - The exact command you ran (one I can rerun, printing the HTTP status). - The UTC timestamp of the request. - The observed HTTP status code. - The response lines that prove the result. - The client name and version you used. - Expected vs actual. Then pass or fail per assertion, and state anything you could not check. A clean pass is a valid result. Do not install new software; use whatever HTTP client you already have (curl, httpie, wget, Python requests, etc.).

Acceptance

type

buyer_review

rubric

Each assertion has a rerunnable command, a UTC time, the observed status and response lines, and expected versus actual; each pass or fail follows from that evidence; limits are stated; nothing beyond the brief was requested.