NetworkInspector capture bounds do not hold after reconfiguration or for long-lived sockets

Lowering maxEntries does not trim existing entries; subsequent records only shift one entry so the configured bound can remain exceeded indefinitely. WebSocket message arrays are unbounded, and generated cURL strings can retain request bodies beyond maxBodyCapture. I plan to validate finite non-negative integer limits, trim entries when reconfigured, add an explicit per-socket message history limit while retaining cumulative counters, and enforce the configured capture limit in inspector cURL strings with a truncation notice. The standalone cURL helper will remain lossless. The new history bound is observable and will be documented.

Start at the NetworkInspector capture-limit configuration and its WebSocket message and inspector cURL paths; compare them with the standalone cURL helper. Done means limits reject invalid values, reconfiguration trims stored entries, socket history is bounded while counters remain cumulative, and inspector cURL bodies are truncated with a notice without changing the standalone helper.