# Node build-time deps (frontend/ bundle is built and vendored, not committed deps)
node_modules/

# Compiled service binary
/comparesrht

# The three scratch directories abuild works in: with `source=""` and
# `builddir="$startdir"` (see APKBUILD) it unpacks into ./src, stages the
# package into ./pkg and keeps ./tmp for the toolchain caches it redirects —
# i.e. all three are inside the checkout it is packaging.
#
# Listing them is not tidiness. Go records vcs.modified in every binary built
# inside a repository and reads that flag from `git status --porcelain`, which
# counts UNTRACKED files — so one untracked directory left beside the build is
# what makes a released binary stamp itself "+dirty". /tmp/ is the one that is
# easy to miss: abuild defaults `tmpdir` to "$startdir/tmp" and exports GOTMPDIR
# to it, so every `go build` puts its work directory INSIDE this checkout.
/src/
/pkg/
/tmp/

# `make css` output: the intermediate and the hashed result. It is derived from
# scss/main.scss and a `base` partial that belongs to the deployment's core.sr.ht
# version, so it is build output — the `scss` task of .build.yml materializes the
# partial and the APKBUILD runs `make css` before the compile.
#
# NOTE: web/static/main.min.79713f25.css is still TRACKED in this revision, and a
# tracked file is unaffected by these patterns. Dropping it from the index is the
# second half of this change, and waits on the first CI run confirming that
# `make css` reproduces it — see docs/ci.md#css.
/web/static/main.css
/web/static/main.min.*.css

# Transient build artifacts
*.tmp

# What `make cover` and `make bench` write when they are run with the defaults,
# i.e. from a laptop. CI puts both in $HOME instead, outside the checkout — for
# the reason the paths above are listed: an untracked file here is what makes
# the next `go build` stamp its binary "+dirty".
/cover.out
/bench.txt

# Local instance config
/config.ini

# Git worktrees checked out inside the repo (both conventions seen here)
.worktrees/
.claude/worktrees/