# What this repo publishes is the package, its tests, the worked
# examples/guide the README points to, the issue log, and the dev tooling
# that gates a fix (tools/mutation_check.py). Those last two are tracked
# deliberately: an issue log and a coverage gate that live only on one
# machine cannot be audited, cannot be restored, and cannot run in CI.
# What still stays on this machine: specs, brainstorms, session handoffs,
# and the agent instructions, which are working notes rather than a record
# anyone else needs.
# The front end lives in its own repo, github.com/emmanuelwunjc/synthweave-frontend.
docs/*
!docs/GUIDE.md
!docs/ISSUES.md
demo/
CLAUDE.md

# Python
__pycache__/
*.py[cod]
*.egg-info/
build/
dist/

# Environments
.venv/
venv/

# Secrets. Never committed, read at runtime by src/synthweave/connectors/.
.env
.env.local

# Cached connector responses (e.g. ACS PUMS), regenerable from the API.
.synthweave_cache/

# Tooling caches
.pytest_cache/
.ruff_cache/
.mypy_cache/
.coverage
htmlcov/

# Generated data. Pipelines write here; output is reproducible from a seed,
# so it never belongs in git. Scoped to output directories on purpose: a
# blanket *.csv would silently swallow a future test fixture.
output/
out/

# Claude Code local overrides. CLAUDE.md itself is ignored above, since the
# instructions in it are for this machine rather than for the world.
.claude/settings.local.json
CLAUDE.local.md

# Browser automation scratch output
.playwright-mcp/

# Editors and OS
.DS_Store
.idea/
.vscode/
