tossme/
examples/
.env
.vscode

# Per-project Claude Code state (planning files, agent transcripts, etc.)
.claude/

# Session planning (never public)
PLAN.md

# Node dependencies
node_modules/

# Test report and results
playwright-report/
test-results/

# Build artifacts
# NOTE: dist/ is listed here but each tool's dist/*.html is force-tracked in git
# (added with `git add -f tool/dist/tool.html`). This is intentional — built artifacts
# are committed alongside source so users can download them directly from the repo.
# New tool dist files must be force-added: git add -f tool/dist/tool.html
dist/

# The website (hand-edited index.html / reference.html / css/ / js/ / img/
# plus all release artifacts) lives in the orphan `website` branch of this
# same Codeberg repo. A `git worktree` of that branch is typically checked
# out at ~/src/zddc-website/ and is what the system Caddy serves at
# zddc.varasys.io. The lockstep build pipeline writes release artifacts
# directly to ~/src/zddc-website/releases/ (override with
# $ZDDC_DEPLOY_RELEASES_DIR). zddc-server binaries are LFS-tracked on
# the website branch; HTML tools + symlinks stay in regular git.

# IDE and project files
.opencode/
opencode.json
package-lock.json
zddc-knowledge*.json
zddc-knowledge*.md
zddc-knowledge*.html