A response body that redaction emptied, because a declared secret could
not be cut out, was replayed as an empty reply; it is now treated as not
retained. Bodies that kept redaction markers are counted in a manifest
limitation, since their tools replay the redacted bytes.
The no-body limitation counted transactions no tool can cite and said
their tools replay status and content type, which a failed request does
not have; it now counts records with a usable request line and says
either value may be absent.
The tool contract and capture docs now say a scenario parent relies on
capture-time redaction instead of the sensitive-values refusal, the MCP
contract page lists scenario parents for environment-manifest, and a
scenario parent asked for another view is told the one it supports.
The browser scenario example raised max_network_body_bytes alone, but
the allocation budgets drop a body far below 256 KiB; it now raises
them and says how body and event budgets differ.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
