# 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/
# The built server binary. `go build -o quarry` drops it in the repository
# root beside the source, where it is the one extra that a careless add
# would sweep in — 40MB of derived output, rebuilt by anyone who runs make.
#
# ANCHORED. Written bare, this pattern matches any path segment called
# "quarry" — which is the whole of cmd/quarry, the main package. A new
# file there never appeared in `zit extras`, and since `zit commit`
# silently omits what was never added, the check that exists to catch a
# forgotten file was blind to the one directory the server is built from.
/quarry
# Per-machine serve flags for `make dev`; see .env.example for the keys.
# Holds QUARRY_NOTIFY_KEY, so this one is a secret, not just noise.
.env.local
# The previous name for the same file, still read by the Makefile so an
# existing checkout keeps working.
dev.local.mk