frontend/dist
node_modules
build/bin/
test_data
test.db

# ── Agent development harness (plan 005) ──
# playwright-cli scratch output (snapshots, console logs, screenshots)
.playwright-cli/
# headless app process state: pid file + captured stdout
.dev/
# Playwright spec output: traces, screenshots and videos of failures
e2e/test-results/
e2e/playwright-report/

# Vitest browser-mode scratch (screenshot diffs, failure captures).
# The committed baselines under frontend/test/**/__screenshots__ stay.
frontend/.vitest-attachments/

.aider*
lefthook-local.yml

# Profiling artifacts
trace-*.out
*.pprof

# ── Legacy GSD planning snapshot (replaced by .planning/) ──
# Kept on disk for reference only; safe to delete once nothing relies on it.
.gsd
gsd-session-*.html
.DS_Store
Thumbs.db
*.swp
*.swo
*~
.idea/
.vscode/
*.code-workspace
.env
.env.*
!.env.example
node_modules/
.next/
dist/
# build/ holds v3 build assets and is tracked; only its output is not.
__pycache__/
*.pyc
.venv/
venv/
target/
vendor/
*.log
coverage/
.cache/
tmp/
bin/

# Task's checksum cache, written by every `wails3 task` run.
.task/

# Generated by build/linux/Taskfile.yml's generate:dotdesktop from
# build/config.yml on every build, and consumed by the deb/rpm/AppImage
# packaging tasks that depend on it. A derived file with one source.
build/linux/yellowjacket.desktop

# `wails3 task common:update:build-assets` regenerates the mobile trees
# whether or not anything asks for them. This is a desktop player and
# cannot target iOS/Android, so their includes: entries are dropped from
# Taskfile.yml and the trees themselves are not carried — ignored rather
# than deleted-and-rediscovered on every asset refresh.
build/ios/
build/android/