BEFORE / BASE  MCP SSE timing capture
Commit: 0597532f16d54189c4a696a249cc66c6d44c7ab5

Linux x64; Node v26.13.1; AMD Ryzen 9 9950X; 8 logical CPUs exposed; same VM, sequential fresh processes; synthetic
data only
Five measured runs; same driver; all returned payloads exactly verified.

responsePayloads -> Stream.runCollect (milliseconds)
MiB  Delivery       Median       Minimum       Maximum
---  ------------  -----------  -----------  -----------
  1  one chunk           29.60        21.93        46.85
  1  256 bytes         1728.22      1231.81      2001.87
  2  one chunk            4.54         3.46         5.32
  2  256 bytes         6542.10      4888.82      7892.58
  4  one chunk            7.79         5.57        10.28
  4  256 bytes        27316.75     22016.52     32794.50

4 MiB / 256-byte individual runs (ms):
  32794.50, 23983.23, 27316.75, 28773.17, 22016.52

Real acp-mcp-call CLI, loopback HTTP + controlled 256-byte delivery:
  Median 23591.46 ms; range 21095.70-29420.84 ms
  Runs: 24215.22, 23591.46, 29420.84, 22359.35, 21095.70

Result: exactly 4,194,304 text characters; unchanged tool result.
4 MiB parser budget: 1,500 ms.  EXCEEDED

CLI timing includes process startup, MCP handshake, HTTP, parsing and stdout.
Fetch rechunker buffers HTTP bytes, then yields 256-byte chunks immediately.
This is controlled parser / CLI evidence, not an interactive ACP-provider thread.
