# Byte-compiled / optimized / DLL files
__pycache__/
*.py[codz]
*$py.class

# C extensions
*.so

# Distribution / packaging
.Python
build/
develop-eggs/
dist/
downloads/
eggs/
.eggs/
lib/
lib64/
parts/
sdist/
var/
wheels/
share/python-wheels/
*.egg-info/
.installed.cfg
*.egg
MANIFEST

# PyInstaller
#   Usually these files are written by a python script from a template
#   before PyInstaller builds the exe, so as to inject date/other infos into it.
*.manifest
*.spec

# Installer logs
pip-log.txt
pip-delete-this-directory.txt

# Unit test / coverage reports
htmlcov/
.tox/
.nox/
.coverage
.coverage.*
.cache
nosetests.xml
coverage.xml
*.cover
*.py.cover
.hypothesis/
.pytest_cache/
cover/

# Translations
*.mo
*.pot

# Django stuff:
*.log
local_settings.py
db.sqlite3
db.sqlite3-journal

# Flask stuff:
instance/
.webassets-cache

# Scrapy stuff:
.scrapy

# Sphinx documentation
docs/_build/

# PyBuilder
.pybuilder/
target/

# Jupyter Notebook
.ipynb_checkpoints

# IPython
profile_default/
ipython_config.py

# pyenv
#   For a library or package, you might want to ignore these files since the code is
#   intended to run in multiple environments; otherwise, check them in:
# .python-version

# pipenv
#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
#   However, in case of collaboration, if having platform-specific dependencies or dependencies
#   having no cross-platform support, pipenv may install dependencies that don't work, or not
#   install all needed dependencies.
# Pipfile.lock

# UV
#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
#   This is especially recommended for binary packages to ensure reproducibility, and is more
#   commonly ignored for libraries.
# uv.lock

# poetry
#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
#   This is especially recommended for binary packages to ensure reproducibility, and is more
#   commonly ignored for libraries.
#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
# poetry.lock
# poetry.toml

# pdm
#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
# pdm.lock
# pdm.toml
.pdm-python
.pdm-build/

# pixi
#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
# pixi.lock
#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
#   in the .venv directory. It is recommended not to include this directory in version control.
.pixi

# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
__pypackages__/

# Celery stuff
celerybeat-schedule
celerybeat.pid

# Redis
*.rdb
*.aof
*.pid

# RabbitMQ
mnesia/
rabbitmq/
rabbitmq-data/

# ActiveMQ
activemq-data/

# SageMath parsed files
*.sage.py

# Environments
.env
.envrc
.venv
env/
venv/
ENV/
env.bak/
venv.bak/

# Spyder project settings
.spyderproject
.spyproject

# Rope project settings
.ropeproject

# mkdocs documentation
/site

# mypy
.mypy_cache/
.dmypy.json
dmypy.json

# Pyre type checker
.pyre/

# pytype static type analyzer
.pytype/

# Cython debug symbols
cython_debug/

# PyCharm
#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
#   and can be added to the global gitignore or merged into this file.  For a more nuclear
#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
# .idea/

# Abstra
#   Abstra is an AI-powered process automation framework.
#   Ignore directories containing user credentials, local state, and settings.
#   Learn more at https://abstra.io/docs
.abstra/

# Visual Studio Code
#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
#   that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
#   and can be added to the global gitignore or merged into this file. However, if you prefer, 
#   you could uncomment the following to ignore the entire vscode folder
# .vscode/
# Temporary file for partial code execution
tempCodeRunnerFile.py

# Ruff stuff:
.ruff_cache/

# PyPI configuration file
.pypirc

# Marimo
marimo/_static/
marimo/_lsp/
__marimo__/

# Streamlit
.streamlit/secrets.toml

# Grove — project-local config layer (machine-specific overrides)
.grove/config.local.json

# Grove — lock sidecars left beside a project config layer. `paths.exclusive_lock`
# never unlinks its sidecar (unlinking would reintroduce the rename race it
# exists to close), so writing project-scope create defaults leaves one behind.
# It holds no data; ignoring it keeps `git status` clean in every repo Grove
# writes a project config into.
.grove/*.lock

# Grove — worktrees created under worktree.root_template (${repo}/.worktrees).
# Each is a linked git worktree (git tracks them via .git/worktrees/); ignore the
# checkout dir itself so the main repo's `git status` stays clean.
/.worktrees/

# Session-local working memory used by brainstorming → writing-plans →
# execution skills.  Never committed.
/docs/superpowers/specs
/docs/superpowers/plans

# Auto-generated by `make docs-schema`; source of truth is the Pydantic
# model in src/grove/core/config.py.
/docs/grove.schema.json

# Auto-generated by docs/hooks/schema_to_md.py at mkdocs build time.
/docs/configure-reference.md

# Claude Code state is local to each checkout and stays ignored, with a small
# allowlist of committed, publicly-served skills. The `!` lines only let git
# descend into `.claude/skills/`; `/.claude/skills/*` re-ignores every OTHER
# skill, so nothing else under .claude is committed. Add one `!` line per skill
# you want tracked.
/.claude/*
!/.claude/skills/
/.claude/skills/*
!/.claude/skills/configuring-grove/
!/.claude/skills/reinstalling-grove/

# Webapp build + test artifacts
/webapp/node_modules
/webapp/.next
/webapp/coverage
/webapp/playwright-report
/webapp/test-results
/webapp/tests/e2e/.auth
/webapp/.env.local
# The Python `lib/` rule above (distutils build) sweeps up the webapps'
# source `lib/` directories. Negate them explicitly so source TS files are
# tracked. The Python build artifacts that the original rule targets
# never live under a webapp anyway.
#
# This one bites silently: `git add webapp/lib/...` refuses, and a bare
# `git add webapp` simply skips the tree, so a whole data layer can look
# committed and not be. Any new front-end app needs its own negation here.
!/webapp/lib
!/webapp/lib/**

# macOS filesystem cruft (Finder metadata + AppleDouble resource forks)
.DS_Store
._*

# Written by `devcontainer build` beside whichever config it was handed.
# Generated, host-specific, and never ours to ship. Grove resolves Features
# through the devcontainer CLI and never passes --experimental-lockfile, so
# nothing reads these back — committing one would only churn.
src/grove/core/data/devcontainer-lock.json
/.devcontainer/devcontainer-lock.json

# Playwright MCP scratch (browser console/page dumps from agent sessions)
/.playwright-mcp/

# Codex's per-repo config. It names the MCP gateway hosts and bearer-token
# variables of whoever set it up, which is host-private and has no business in
# a tree that mirrors to a public remote. Keep your own at `.codex/` locally.
# Note the trade-off: a Grove workspace is a git worktree and sees only
# committed files, so an ignored config does NOT propagate into worktrees.
/.codex/

# The prebuilt dashboard `make webapp-bundle` stages for the wheel.
/src/grove/_webapp/
/src/grove/_webapp.old/
