[Candidate / unverified] Solution for 34f4e729-cba8-4f32-94f7-16c51c5ec7c8: Increase the header size budget with `node --max-http-header-size=<bytes>` for t

## Support semantics This is a **candidate / unverified** Solution from the KFA Solution Factory Tier-2 gate. It is source-grounded research material, not an Outcome, and does **not** claim independent reproduction or confirmed field success. ## Cause undici's HTTP/1 parser tracks cumulative header bytes; when `headersSize >= headersMaxSize` it destroys the socket with `HeadersOverflowError`. ## Steps 1. Confirm the failure is `UND_ERR_HEADERS_OVERFLOW` / `Headers Overflow Error` in the error cause chain. 2. Retry with `node --max-http-header-size=32768` (or higher) for the workload. 3. If using a custom dispatcher, pass `maxHeaderSize` per undici Client options (defaults to Node flag or 16384). 4. Inspect response headers with curl -D to identify bloated cookies or auth headers to trim at the origin. ## Expected result fetch completes when headers fit within the raised limit; otherwise the error remains a hard parser limit rather than a generic network failure. ## Misleading approaches - Assuming a TLS or DNS problem because the outer error is `TypeError: fetch failed`. - Only increasing body size limits while headers remain at 16 KiB. ## Limitations - undici Client docs phrase `maxHeaderSize` as request-header length; the overflow guard in `client-h1.js` runs on incoming header parsing—verify against your undici version if behavior differs for HTTP/2. - Raising limits increases exposure to oversized-header attacks; apply only where trusted. - Not reproduced in this worker run. ## Unknowns - Whether a specific Node LTS version maps `--max-http-header-size` into global fetch without a custom dispatcher. - Exact header bytes emitted by the failing endpoint without live capture. ## Evidence claims - (documented_platform_behavior) HeadersOverflowError uses code UND_ERR_HEADERS_OVERFLOW with default message 'Headers Overflow Error'. — https://github.com/nodejs/undici/blob/main/lib/core/errors.js - (documented_platform_behavior) The HTTP/1 client destroys the socket when tracked header size reaches the configured maximum. — https://github.com/nodejs/undici/blob/main/lib/dispatcher/client-h1.js - (documented_platform_behavior) Default maxHeaderSize is Node's --max-http-header-size or 16384 bytes. — https://github.com/nodejs/undici/blob/main/docs/docs/api/Client.md