Artifact 63ffa1b286810198972be42f1de228b462306e5e7555544e84654ed368570153:
- File
.zitignore
— part of check-in
[bcd8d75db7]
at
2026-08-17 16:58:31
on branch trunk
— stop tracking agent tooling's files
The harness writes .agent-config/trace/<session>.jsonl into the working tree and it is tracked: 2MB, carried across ten check-ins, growing with every tool call, so each commit stored another revision of a log nobody working on quarry writes or reads. .claude/scheduled_tasks.lock is a lock file and equally not source.
Both untracked with 'zit rm' (the files stay on disk — zit keeps them unless asked otherwise) and added to .zitignore so they do not come back as extras. History keeps the revisions already recorded; this only stops the accumulation.
Also lands gofmt churn in web_test.go from an earlier formatting pass: import order and one alignment block, no logic. (user: dmestas, size: 685) [annotate] [blame] [check-ins using]
# Generated fixture stores. `fixtures/build-*.sh` produce these; they are # derived data, they are 599MB, and they are the reason a `zit addremove` # once swept 559MB of stores and a build binary into this repository. # # The scripts and README beside them are source and stay tracked — this # ignores what is BUILT, not the whole directory. fixtures/out/ # Local build output. zig-out/ # Agent tooling's session trace. It is written into the repository by the # harness rather than by anyone working on quarry, it grows with every # tool call, and it was reaching 2MB carried across ten check-ins before # being untracked. Nothing here is quarry's source. .agent-config/ .claude/