only-cli 886ce58e27 fix: judge an unreadable page by evidence, not by length alone ...

contentFailure called every render under 25 tokens a failure, which
made exit 2 claim a terse page was JavaScript-only, gated, or
challenged when it had simply arrived terse. The verdict now needs
evidence: nothing extracted is empty whatever the page weighed, and a
short render is only a failure when the markup behind it was far too
big to have carried only that. A status endpoint or a one-line answer
now exits 0, script-only shells and consent walls still exit 2, and
raw applies the same rule before refusing. The --json empty field
follows the same policy, so callers keep a machine-stable distinction
between empty and merely short.

Fixes #29

2026-08-24 13:59:27 -04:00

..

pages

fix: hand over code an agent can actually run

2026-08-23 09:12:25 -04:00

act.test.js

fix: hand over code an agent can actually run

2026-08-23 09:12:25 -04:00

distill.test.js

fix: judge an unreadable page by evidence, not by length alone

2026-08-24 13:59:27 -04:00

fetch.test.js

fix: bound response bodies before buffering them

2026-08-24 13:59:11 -04:00

sites.test.js

feat: dispatch the site shortcuts the README already documented

2026-08-23 20:54:55 -04:00