BREAKING(http/unstable): split parseProblemDetails, validate status, add statusText option

[tomas-zijdemans]

• Split parseProblemDetails into sync (unknown input) and async parseProblemDetailsResponse.
• Add statusText option to ProblemDetailsResponseOptions, forwarded to Response only when defined.
• Throw RangeError for non-integer status in createProblemDetailsResponse.
• Rewrite ProblemDetailsExtensions JSDoc to honestly describe the intersection-based safety.
• Tighten isProblemDetailsResponse docs; add @throws tags throughout.
• Add runnable Response parse example; replace Record<never, never> defaults with Record<string, never>.
• Backfill tests for status validation, statusText forwarding, and primitive bodies.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.61%. Comparing base (a496da2) to head (3e22841).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #7117   +/-   ##
=======================================
  Coverage   94.61%   94.61%           
=======================================
  Files         634      634           
  Lines       51801    51815   +14     
  Branches     9329     9336    +7     
=======================================
+ Hits        49011    49025   +14     
  Misses       2216     2216           
  Partials      574      574           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[lunadogbot]

Split looks right — keeping parseProblemDetails for plain input and giving the async path its own name parseProblemDetailsResponse removes the overload without forcing sync callers to migrate. Number.isInteger correctly rejects NaN/Infinity/3.14/"500" (the test loop in createProblemDetailsResponse() throws RangeError for non-integer status covers all four). The statusText spread ({ statusText } only when defined) preserves the prior platform default — assertEquals(response.statusText, "") in the unset case confirms.

• nit: @see {@link https://www.rfc-editor.org/rfc/rfc9457.html} was dropped from the module JSDoc. Prose still names RFC 9457 but the clickable link is gone.

[lunadogbot]

@bartlomieju this is ready to merge