# Built binaries
/doltsrht
/doltsrht-migrate
/dolt-git-hook

# Built CSS (generated by `make css`)
/static/main.css
/static/main.min.css
/static/main.min.*.css

# The three scratch directories abuild works in. With source="" and
# builddir="$startdir" (see APKBUILD) it has no tarball to unpack elsewhere: it
# unpacks into ./src, stages the package into ./pkg, and defaults tmpdir to
# ./tmp — all three inside the very 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 an untracked directory left beside the build makes
# the packaged binary stamp itself "<sha>-dirty" for the life of the apk. That
# is the same failure the APKBUILD's pkgver comment is about, arriving by the
# other door: there a tracked file was rewritten, here an untracked one appears.
#
# /tmp/ is the one that is easy to miss and the one that bites hardest. abuild
# exports GOTMPDIR to it, so every `go build` puts its work directory inside
# this checkout, and /usr/share/abuild/default.conf exports MAKEFLAGS=-j$(nproc)
# — under which `make all-bin`'s three `go build`s run at the same time. Each
# reads the tree once while loading packages, before it writes anything, so its
# own work directory is still empty and unreported; the other two are not.
/src/
/pkg/
/tmp/

# Git worktrees, kept inside the repo so they never scatter as sibling dirs.
# Both paths, because the two conventions in use across these repos are
# .worktrees/<branch> and the older .claude/worktrees/<branch>.
/.worktrees/
/.claude/worktrees/

# macOS
.DS_Store

# Beads / Dolt files (added by bd init)
.dolt/
*.db
.beads-credential-key
.beads/proxieddb/