fix(scripts): stop the large-file guard firing on text

[miguel-heygen]

What

The pre-commit large-file guard no longer fires on text files. The binary rule, the registry/ exemption, the LFS check and the 500 KB threshold are unchanged.

Also adds the first test for scripts/check-large-files.sh, wired into test:scripts.

Why

docs/changelog.mdx reached 512 KB, so chore: release v0.8.14 could only be committed by passing HF_MAX_NONLFS_KB. Every release from here would need the same override, and the file grows a few KB each time.

The check is for binaries. Its own error message says "large binaries are being committed to git instead of LFS", and its header explains the cost it exists to prevent: a 31 MB ONNX model, HDR-regression MP4s, demo clips, each living in history forever and paid for by every clone.

That cost is specific to binaries. Git delta-compresses text, so release notes growing a few KB per commit add a few KB to the pack. A binary of the same size re-enters the pack whole on every edit, which is how the history got its hundreds of megabytes in the first place.

How

One grep -qI skip: a file containing NUL bytes is binary, the same heuristic git uses to decide "Binary files differ". Everything else in the script is untouched.

The alternative was an allowlist entry for docs/changelog.mdx. That leaves the next legitimately growing text file to hit the same wall and collect its own one-off exemption, and it does not address why a binary check was rejecting text.

Worth flagging for the reviewer, since it is a real narrowing of the guard: a large generated text blob (a vendored bundle, a giant JSON fixture) now passes where it previously failed. I judged that acceptable because such a file is caught in review by being visible in the diff, whereas a binary is not, and because a text blob's pack cost is a fraction of a binary's. Say so if you would rather have a higher text threshold than a full exemption.

Test plan

• Unit tests added/updated
• Manual testing performed
• Documentation updated (if applicable)

scripts/check-large-files.sh had no test. It has four now, added to the test:scripts list so they actually run rather than sitting unreferenced:

• an over-limit binary fails, and is named in the error
• an over-limit text file passes
• an under-limit binary passes
• multiple offenders are all reported, not just the first

Verified the test bites: with the exemption line removed, "accepts a text file over the limit" fails and the other three still pass.

--- with the exemption removed ---
    not ok 2 - accepts a text file over the limit
# pass 3
# fail 1
--- restored ---
# pass 4
# fail 0

Also exercised through the real staged-set path the hook uses, rather than only the explicit-argument path the tests use:

--- staged: one large binary + one large text file ---
ERROR: large binaries are being committed to git instead of LFS.
  • big-probe.bin (2048 KB)

Full bun run test:scripts: 188 passed, 0 failed, plus the 42 vitest catalog tests it chains.