Network Transaction Recorder
Bridges redacted capture to the bounded transaction store without affecting host behavior. When enabled is false, record returns immediately without building a capture or touching store — the disabled build never redacts, serializes, or stores a payload. Processing (URL parsing, redaction, and store persistence) is offloaded asynchronously from caller threads via a bounded queue (drop-oldest strategy on overflow).
Constructors
Functions
Same as the four-argument record, but stores the transaction under the caller-supplied transactionId instead of a freshly generated one (null keeps the generated id). Recording the same id again replaces the earlier stored transaction -- the NetworkTransactionStore.record contract -- which is how an adapter first records a provisional metadata-only transaction for a still-streaming response and later upgrades it in place with the captured body, without ever showing two entries for one HTTP call.
Installs the capture-exclusion gate; without one every enabled recording is captured.