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/

# Release artifacts under website/releases/ ARE committed — including
# zddc-server binaries. Per-version HTML tool files (<tool>_v<X.Y.Z>.html)
# and per-version zddc-server binaries (zddc-server_v<X.Y.Z>_<platform>)
# are immutable real files; partial-version pins (<tool>_v<X.Y>.html,
# <tool>_v<X>.html, zddc-server_v<X.Y>_<platform>, zddc-server_v<X>_<platform>)
# and channel mirrors (<tool>_<channel>.html, zddc-server_<channel>_<platform>)
# are checked-in symlinks. The lockstep build (shared/build-lib.sh
# promote_release + promote_zddc_server) maintains both chains. Everything
# serves from zddc.varasys.io/releases/; no Codeberg release-asset
# publication anymore.

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