Problem

Pushing large generated data files (e.g. prospecting/exports/**/*.csv, 4–8 MB each) is blocked by the pre-push credential guard with a HIGH engine.input_too_large finding — a false positive that has nothing to do with credentials. The scan engine fail-closes on input over the 1 MiB cap, and the hook concatenates all added-line text before scanning, so one large generated file oversizes the whole push. The only escape is GSTACK_REDACT_PREPUSH=skip on every such push, which defeats the guard entirely (it also skips real code in the same push).

Change

Add an opt-in, auditable path-ignore to bin/gstack-redact-prepush. Generated data files can be exempted from the pre-push scan without weakening credential scanning on code.

Ignore globs merge two sources:

• .gstack/redact-prepush-ignore committed at the repo root (one glob per line, # comments, blank lines skipped) — the recommended mechanism: versioned, reviewable in git history, shared across contributors.
• redact_prepush_ignore_globs config key (gstack-config, comma-separated) — a machine-local supplement in ~/.gstack (never committed).

Globs match repo-root-relative paths via Bun.Glob (so ** spans directories, e.g. prospecting/exports/**/*.csv). Matched paths are dropped from the scanned diff via a git :(exclude) pathspec, so excluded content never reaches scan(). Every exemption prints a one-line stderr notice reporting how many paths / bytes were skipped and appends an audit record to prepush-skip.jsonl — an ignore is never silent.

Fail-closed invariant preserved (#1946)

An ignore glob is an explicit, auditable opt-in. Anything not matched by an ignore glob still goes through scan(), so:

• a bare oversize non-ignored file still fail-closed-blocks (unchanged);
• a real secret in a non-ignored file still blocks, even when ignore rules are present;
• with no ignore rules configured, behavior is byte-for-byte unchanged.

The accepted tradeoff: a secret inside an explicitly ignored path is exempted — but that path is a versioned opt-in and the skip is always reported.

Tests

Six new cases in test/redact-prepush-hook.test.ts (all green, plus the existing 15):

• (a) ignored large file passes, skip reported on stderr
• (b) non-ignored large file still blocks fail-closed
• (c) real secret in a non-ignored file still blocks with ignore rules present
• (d) explicit ignore glob exempts its file (auditable opt-in)
• (e) machine-local config key is an additional ignore source
• (f) no ignore rules → default behavior unchanged

Docs

• bin/gstack-config: new redact_prepush_ignore_globs default + annotated header entry.
• CLAUDE.md: redaction-guard section documents the config key and the committed-file mechanism.

Config bump / CHANGELOG

None here — VERSION and CHANGELOG are branch-scoped and land at /ship time per repo convention, not during development.

CI note

This PR comes from a personal fork by a non-collaborator, so the eval/E2E jobs won't receive base-repo secrets and will fail with empty-env auth. Per CONTRIBUTING / CLAUDE.md, a maintainer can move the branch to a base-repo branch to run those jobs. Free tests (bun test) pass; the two unrelated failures observed locally (sidepanel-terminal.js forceRestart, parent-process watchdog) reproduce on a clean tree with these changes stashed, so they are pre-existing and unrelated.

Context: hit while shipping noygear/medical-mockup PR #282, which commits prospecting/exports/<version>/<STATE>/suspects-*.csv (4–8 MB each). That repo will set redact_prepush_ignore_globs = prospecting/exports/**/*.csv (or the committed file) once this lands.

🤖 Generated with Claude Code