Split The code is public; the app answers only to the crew.
The tree guard is red on any machine that has run the app: it fails on files .gitignore already excuses #162
Check · Review · Land · Live done — Landed and live in production.
`src/tree.test.ts` no longer checks a file's name against `.gitignore`'s scratch patterns (`*.db`, `*.db-wal`, `*.db-shm`, `static/app.*.js`) — matching one of those means the ignore is doing its job, not that something is wrong, and those files show up on any machine that has run or built the app. A file's content is still checked for a Netscape cookie jar header unconditionally, and a directory…
shipped merged
Sign in to join this conversation.
new above
offline
src/tree.test.tsno longer checks a file's name against.gitignore's scratch patterns (.db,.db-wal,.db-shm,static/app..js) — matching one of those means the ignore is doing its job, not that something is wrong, and those files show up on any machine that has run or built the app. A file's content is still checked for a Netscape cookie jar header unconditionally, and a directory named for one of.gitignore's scratch entries (.scout-tmp/,.checkdata/) still fails the guard, since nothing normal creates one. A comment explains why "ignored" and "committed" are different questions.Verified locally:
bun run checkis green on a clean tree, and stays green after creatingdata/app.db,data/app.db-wal,data/app.db-shm, andstatic/app.deadbeef.js..scout-tmp/with a cookie jar inside turns it red again (both the scratch-directory violation and the cookie-jar violation fire).🤖 Generated with Claude Code
Closes #129