Coverage was 79.51% of statements. Add tests for the paths that had none:

- `httpClient.create()` and the proxied `stop` signal. The existing
  "can use create()" test never called `create()`.
- A direct call with a method that is not proxied, which goes straight to
  `ky` and so skips the response and error handling.
- `convertAgent` declining to override a custom `fetch` from another lib.
- The `fetch` override used when the installed undici cannot drive the
  platform `fetch`. No supported node takes that path with `undici@7`, so
  the test forces it by reporting an incompatible platform undici major.
- Importing when the version read fails, which must not throw at module
  load.

Now at 100% of statements, lines, and functions, and 98.27% of branches.
The one uncovered branch is the fallback for an installed undici major that
is not in the compatibility table.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

The `Possible CORS error` message was produced by matching the literal
string `Failed to fetch`, which is Chromium's wording for a failed or
blocked `fetch`. Firefox reports `NetworkError when attempting to fetch
resource.` and WebKit reports `Load failed`, so neither matched and both
fell through to `ky`'s generic network error.

Match against a set of the three engines' messages instead. Node.js
`fetch failed` is deliberately excluded: there is no CORS in Node.js, so
the hint would be misleading there.

All three strings were measured, not assumed, and each is exercised by the
browser test matrix.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

This is what keeps the per-engine CORS messages honest, and running the
shared suite in each engine surfaces any other behavior difference.

Three changes were needed to make the other engines work:

- Advertise the test servers as `127.0.0.1` rather than the `0.0.0.0` that
  `address()` reports. Only Chromium treats `0.0.0.0` as loopback when used
  as a request host; Firefox and WebKit refuse to connect, which failed
  every test that used a local server.
- Replace the raw `--no-sandbox` launch args with `chromiumSandbox: false`.
  WebKit rejects unknown options and fails to launch; the `playwright`
  option is applied to Chromium only.
- Use the `istanbul` coverage provider rather than `v8`. v8 coverage is
  gathered over CDP, which only Chromium supports, so `coverage` refused to
  start once the other engines were added.

`istanbul` counts default parameters and some conditionals that `v8` did
not, which surfaced an untested documented option, so also test
`parseBody: false` and `create()`/`extend()` with no overrides.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>