# Rust
/target/
/src-tauri/target/
**/*.rs.bk

# Node
node_modules/
dist/
dist-ssr/
.vite/
*.tsbuildinfo

# Tauri build output
/src-tauri/gen/

# Environments (test venvs created by the integration suite / spikes)
.venv/
venv/
# Scratch venvs for verifying by hand. Note that the GUI will only ever *see* one named exactly
# `.venv`, `venv`, `env` or `.env` in the working directory — `envs::venv_scan` matches that fixed
# list and `env_add_manual` (Browse…) is still owed — so a suffixed one here is CLI-only.
/.venv-*/
__pycache__/
*.py[cod]
# ci-integration.yml builds these in the workspace. Harmless on an ephemeral runner, but a
# developer running the same steps locally gets an untracked venv that `git add -A` would sweep up.
/.itest/
/.uvtools/
/.itest-appdata/

# Editors / IDEs
# `.claude/` holds git worktrees and a local dev-server launch config — machine state, not source.
.claude/
.idea/
.vs/
.vscode/*
!.vscode/extensions.json
*.swp

# OS
Thumbs.db
Desktop.ini
.DS_Store

# Secrets & local config
.env
.env.*
!.env.example
*.key
tauri-signing-private.key*

# Logs & scratch
*.log
/spikes/out/

# Spike tooling venvs (SP-1 needs several uv versions side by side)
/spikes/.venv*/

# Staged by scripts/bundle-cli.mjs so the installer ships the CLI; rebuilt every bundle.
src-tauri/binaries/
