One HTTP request to a (private) container port

Make ONE HTTP request to a port inside a RUNNING node and get the response back structured, with timing - THE way to test a server you just started (a vLLM /v1/chat/completions, a health check) without shell-quoting a curl payload through run_command: the JSON body rides the body parameter verbatim, and the request goes over the platform's own pipe to the port (no expose_port needed; the port stays private). Returns {status, headers, body, body_bytes, truncated, timing_ms: {dial, ttfb, total}}: dial is connection establishment to the port, ttfb is request-sent to response-status, total includes reading the whole body. The body is read to the end (SSE streams included) and capped at 64 KiB (truncated: true past the cap); a non-UTF-8 body arrives base64 as body_base64. Budgeted by timeout (default 60s, ceiling 300 - a long generation wants more). This tool never wakes a stopped node. A run_command wakes it, and the wake bills. This tests the PORT, not a public URL - it bypasses the ingress edge (no capability check, no bearer), so a 200 here does not prove an exposed endpoint's URL works; curl the minted URL for that. Bulk traffic and load tests belong on an expose_port URL.