Add Reporting and Network Error Observability Hooks

Proposal

Introduce a lightweight reporting surface for collecting browser-like diagnostics in automation contexts.

Scope:

• Add API hooks for reporting events and network error signals.
• Allow configurable sinks for captured reports.
• Provide filtering by type and endpoint.
  Technical Notes:
• Reporting backend should be injected for storage/forwarding.
• Keep event model minimal and deterministic.
  Acceptance Criteria:
• Reports can be emitted, enumerated, and flushed.
• Network error events can be captured from requester pipeline.
• Tests validate schema shape and filtering behavior.
  Out of Scope:
• Full browser reporting policy implementation.
• Full CSP/NEL parity on first release.

Description

Add reporting/observability hooks for browser-like diagnostics, including structured report emission and network-error-related capture points.

Background

Automation and headless deployments benefit from centralized diagnostics. A lightweight reporting layer improves debuggability without requiring full browser reporting-policy parity.

Specification

• Reporting API: https://w3c.github.io/reporting/
• NEL (background reference for network error reporting concepts): https://www.w3.org/TR/network-error-logging/

Start by locating the existing requester pipeline and API abstractions used for injected backends. Define the minimal report and network-error surfaces around those entry points, then add tests for schema shape, emission, enumeration, flushing, and filtering. Done means reports can use configurable sinks and network errors are captured without implementing full browser policy parity.