End of response processing, before the logger is awaited.
Original request value; no defensive copy is made.
Decoded payload or transferred binary stream, absent on processing error.
Route path normalized to one leading slash.
Response arrival, before response body processing; null without a response.
Metadata used to execute the request.
Start of the transport operation, after request preparation.
Received HTTP status, or null when transport produced no response.
Event of one completed fetch, passed to IConnection.logger.
statusandrespond_atarenullwhen no response arrived, andcompleted_atis set after response processing or transport failure. Binary success streams are handed to the caller without reading their bytes, so this timestamp does not measure the duration of their consumption.inputis the value the caller passed andoutputis the response data, the error body for a failed status, orundefinedwhen the request threw. These values retain their original references. Errors before transport, such as encoding or URL construction failures, do not create a logged event.Evidence
contracts/common.md#principled-implementation The event records the route, the request input, the observed status and output, and the three instants of the exchange, which is what a logger or a benchmark needs to compute latency and to group by endpoint.
Evidence
contracts/common.md#clear-and-simple-design A flat record; the two nullable members mark the states with no response.
Evidence
contracts/common.md#prohibited-implementation-shortcuts Every value is measured by the pipeline; none is defaulted to a plausible value.
Evidence
contracts/common.md#meaningful-documentation The comment states the states with no response and what input and output hold.