http.compressionThreshold: docs say default 1200, shipped config sets 0 (compression off by default)

Inizia esaminando le quattro posizioni della documentazione citate e confermando con il responsabile di static/defaultConfig.yaml di Harper se compressionThreshold: 0 è intenzionale. Verifica quindi l’incoerenza corrispondente di Harper e il problema dello stream in #655 prima di aggiornare in modo coerente tutti i valori documentati; il lavoro è completato quando la decisione tra repository è registrata e le quattro pagine corrispondono al comportamento distribuito.

What's wrong

The docs state that http.compressionThreshold defaults to 1200 bytes, so Brotli response compression is on out of the box. Harper's shipped configuration sets it to 0, and the runtime treats 0 as "off" — so on a default install, Brotli response compression never happens.

The root cause is not in this repo. Harper contradicts itself, and our docs faithfully mirror the half of it that isn't what actually ships.

Evidence (harper origin/main)

So the schema documents 1200, the shipped template sets 0, and the runtime honors 0. There is no code-level 1200 default anywhere.

Note this is specifically http.compressionThreshold. The unrelated storage.compressionThreshold (LMDB record compression) does have a real code default — (storage.pageSize || 4096) - 60 at resources/databases.ts:102 — which makes this easy to conflate when grepping.

Affected pages in this repo

• reference/configuration/options.md:37 - "Default: 1200 (bytes)"
• reference/http/configuration.md:111 - the http.compressionThreshold section, plus 1200 in examples at :123 and :318
• reference/http/overview.md:104 - "Compression applies when the response body exceeds the configured compressionThreshold (default 1200 bytes)"
• reference/configuration/operations.md:106 - "compressionThreshold": 1200 in a config response example

The question that has to be answered first

Is compressionThreshold: 0 in the shipped config intentional? The docs fix depends entirely on the answer, and the two outcomes are very different:

• If 0 is a bug in harper - Brotli compression has been silently off for every default install. That is the real finding here, and the fix belongs in static/defaultConfig.yaml. Our docs then need no change beyond possibly noting the versions affected.
• If 0 is intentional - then harper's own schema description and examples are wrong too, and our four locations should say compression is disabled by default and must be explicitly enabled. In that case config-root.schema.json should be corrected alongside.

Either way one of the two harper locations is wrong, so this likely wants a companion harper issue; transferring or cross-linking is fine.

Why it matters beyond a wrong number

Two things downstream depend on this:

1. Anyone following our docs believes responses over 1200 bytes are compressed. If they are not, that is a real and invisible performance difference on a default install.
2. There is a latent crash gated behind this setting. contentTypes.ts:410-425 pipes serializeStream's return value into createBrotliCompress() whenever canCompress is true, but the application/x-msgpack handler returns a Buffer (not a stream) for a plain array. Accept: application/x-msgpack + Accept-Encoding: br + an array body would throw TypeError: stream.pipe is not a function. That is currently unreachable only because compression ships disabled - so if the default is "corrected" to 1200 without fixing the pipe path first, this becomes reachable the same day. Sequencing matters. Surfaced in #655.

Suggested fix

1. Get a ruling from whoever owns static/defaultConfig.yaml on whether 0 is intended.
2. Fix harper's inconsistency (either the shipped default or the schema description + examples).
3. Update the four locations above to match, in one pass so they cannot disagree with each other.
4. Track the .pipe() normalization separately, and land it before any change that turns compression on by default.

_{sent with Claude Opus 5}