.gitignore

# Python
__pycache__/
*.py[cod]
*.egg-info/
.pytest_cache/
.ruff_cache/

# Node
node_modules/
**/node_modules/
# ...and again WITHOUT the trailing slash: the patterns above only match
# DIRECTORIES, so a node_modules *symlink* (e.g. one created to share deps
# with a git worktree) is a file and slips straight past them — it then gets
# committed, and checking that commit out elsewhere replaces the real
# node_modules with a symlink pointing at itself.
node_modules
**/node_modules
jarvis/public/node_modules/
jarvis/public/node_modules
# Root yarn.lock has no production role here (the frontend has its own
# frontend/package-lock.json); a stray `yarn`/`npx` in the repo root would
# otherwise pull gemini-cli + keytar onto contributor machines.
yarn.lock

# graphify (knowledge-graph index; local-only)
graphify-out/

# Frappe build artefacts
jarvis/public/dist/

# Vite SPA build output (regenerated by `cd frontend && npm run build`)
jarvis/public/frontend/
jarvis/www/jarvis.html
frontend/auto-imports.d.ts
frontend/components.d.ts

# Mobile PWA build output (regenerated by `cd pwa && npm run build`). The .py
# controller next to it IS tracked; only the generated shell + bundle are not.
jarvis/public/pwa/
jarvis/www/jarvis_mobile.html
pwa/auto-imports.d.ts
pwa/components.d.ts

# OS
.DS_Store

# Brainstorm mockups + design specs (local working docs — never commit).
# This app ships publicly; internal design/plan/decision docs live in the admin
# repo, never here. Patterns catch them at the repo root AND nested (jarvis/docs).
.superpowers/
docs/superpowers/
**/docs/superpowers/
jarvis/docs/
*.plan.md

# Local virtualenvs + logs
.venv/
logs/
*.log

# Claude Code config, tooling, and workflow artifacts (kept local, not tracked)
.claude/