pub const PLUGIN_TOOL_MAX_OUTPUT_BYTES: usize = _; // 1_048_576usizeExpand description
Hardening cap (mirrors crate::mcp::MCP_MAX_RESPONSE_BYTES’s rationale,
scaled down: a plugin tool result is model-context-bound, not a raw
resource fetch): the maximum bytes of stdout (and, separately, stderr)
a plugin tool invocation retains — reading never stops at this cap (see
the module doc comment), only retention does, so a flooding child can’t
wedge on a full OS pipe either.