3.0: retain released HTTP adapters with report-once middleware #95

Status and delivery

Report-once HTTP adaptation belongs to PR 3; the owner has now also approved the request/representation scope in 8. The expanded implementation is under local integration. Earlier exact-head checks at c178301 below do not validate these additional changes or establish current merge readiness.

JSON/Whoops renderers and the reporting decorator were delivered in 2.5.0 through 92/96. This major preserves the useful concrete adapters while deliberately migrating their contract and provider wiring.

Approved migration boundary

• Require one scoped lifecycle/reporter and one original diagnostic delivery before a pure response renderer.
• Require ServerRequestInterface as the second argument to every createResponseFromThrowable implementation and direct call. Middleware forwards the current object unchanged.
• Replace separate JSON/Whoops provider profiles with one ErrorHandlerServiceProvider. Normal application-first bootstrap supplies overrides; the library provider defines only its own services.
• The default response is request-aware negotiation: generic safe fallback, Symfony HTML for public/debug pages, and Serializer Problem Details for accepted JSON media types. Trusted debug controls details without forcing the representation.
• Retain concrete JSON/HTML/Whoops renderers and explicit public-template capture. Whoops is optional and explicit; its installation never switches the HTML default. Preserve lazy page customization and honest sequential/concurrent limits.
• JSON's required SerializerInterface is third and debug fourth. Update the prior error/envelope payload to Problem Details and migrate direct JSON content type to application/problem+json; negotiation also supports application/json.
• Keep reporter/renderer failure identity, inert construction, cached process services and fresh middleware scopes. Add no HTTP emission or competing native registration.
• Keep the reporting decorator an explicit utility for pipelines that have not already reported; do not wrap this middleware's renderer and report twice.

Whoops ^2.18.7 retains the separately delivered upstream native-source correction. That maintenance adoption does not make Whoops mandatory or solve request negotiation. Detailed Accept/media/debug/fallback/cache/Vary policy and the separately reviewable CLI opt-in are recorded in 8; coherent-major validation is owned by 26.

Completion criteria

• Validate original-once/report-before-render behavior and unchanged collaborator failures under the new required-request and single-provider contracts.
• Verify cached services/fresh scopes, application overrides, lazy unused renderers, optional Whoops absence/configured sequential pages, and explicit capture boundaries.
• Align PHPDoc, source-accurate runnable recipes, API/HTTP/provider/migration guides, site, consumer skill and the major note with the completed implementation.
• Record full local validation and fresh exact-head native checks without suppression or waived coverage/security rules.
• Obtain the owner's code review and merge decision.