.gitignore

# Ignore Repo to Prompt
repo-to-prompt.codemod.js

# MCP config (names deployment-specific server URLs and token env vars).
# `.codex/config.toml` is the same file for a different harness and mirrors
# `.mcp.json` server for server, so the two must be ignored together.
.mcp.json
.codex/

# Node / JavaScript
node_modules/
*.tsbuildinfo

# macOS resource forks / metadata
._*
.DS_Store

# Byte-compiled / optimized / DLL files
__pycache__/
*.py[cod]
*$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

# 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

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

# Celery stuff
celerybeat-schedule
celerybeat.pid

# SageMath parsed files
*.sage.py

# Environments
.env
.env.*
*.env
!.env.example
!docker.example.env
.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

# Local runtime sessions
apps/mewbo_cli/data/

# Local config files (MCP/tool manifests, secrets)
**/app.json
**/*config.json
!apps/mewbo_console/tsconfig.json
!apps/mewbo_console/tsconfig.node.json
# A TypeScript base config is source, not local configuration — the pattern
# above catches it by accident. Missing it is invisible on a developer machine,
# where the untracked file is present, and fails only in a clean checkout: the
# build config extends a base that is not there, TypeScript falls back to its
# defaults, and the compile dies of a dozen unrelated-looking option errors
# rather than of the one missing file.
!apps/mewbo_ide/tsconfig.json
configs/*.toml
configs/*.yaml
configs/*.yml
configs/mcp.json
!configs/*.example.json

# Pyre type checker
.pyre/

# pytype static type analyzer
.pytype/

# Cython debug symbols
cython_debug/

# PyCharm
#  JetBrains specific template is maintainted 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/
docker.env
docker-compose.override.yml
docker/init.d/*
!docker/init.d/00-toolbox.sh
!docker/init.d/10-git-setup.sh
!docker/init.d/12-agent-clis.sh
!docker/init.d/13-models-cli.sh
!docker/init.d/15-tea-setup.sh
# Secrets-manager directory binding — names the deployment's project and
# configuration, which are deployment identifiers and never belong in the tree.
.ssm/

/.claude/settings.json
/.playwright-mcp

# mewbo_console build cache + runtime session state
apps/mewbo_console/.vite/
apps/mewbo_console/data/
.claude/settings.local.json
# Local agent instruction layer — holds internal hosts, tracker IDs and ops
# touchpoints that must never reach the public GitHub mirror. Ignored at any
# depth, plus the .claude/ variant discover_all_instructions() also loads.
CLAUDE.local.md
**/CLAUDE.local.md
.claude/CLAUDE.local.md
# Skills that document internal-only process rather than the product. A board
# ritual reads machine-local scripts and a private tracker's conventions, so it
# belongs beside the local instruction layer above, not in a mirrored tree.
.claude/skills/board-standup/
# Live git worktrees rooted under the project — checked out files belong to
# their own branch and must not be tracked by the parent repo.
.claude/worktrees/
.mewbo/worktrees/
.worktrees/
# Grove roots its workspace worktrees here, so ignore the directory CONTENTS —
# but track the committed team baseline: `config.json` and the `init.sh` it
# invokes (together they seed CLAUDE.local.md into each new workspace).
# Per-machine overrides live in the ignored `config.local.json`. Uses `.grove/*`
# rather than `.grove/`: git cannot re-include a path whose parent DIRECTORY is
# excluded. `init.sh` must stay tracked — Grove RAISES if `init_script.path`
# is missing, unlike an inline script which can just no-op.
.grove/*
!.grove/config.json
!.grove/init.sh

# Generated docs artifacts — the canonical schema is tracked at
# configs/app.schema.json; docs/ copies are regenerated by the MkDocs build.
docs/app.schema.json
docs/build-info.json

# Stray root npm lockfile — the real one lives in apps/mewbo_console/; a root
# package-lock.json (no root package.json) is an errant `npm install` artifact.
/package-lock.json

# Wrangler local dev state (KV/D1/R2 emulation, build tmp) — regenerated
# on every `wrangler dev` / `wrangler deploy`; may contain dev tokens.
.wrangler/

# Demo-as-code: the demo stack is deterministic BY DESIGN — its env
# and api config carry no secrets (replay mode, fixed demo token) and MUST be
# versioned or `make demo-up` cannot reproduce the artifact pipeline.
!demo/demo.env
!demo/configs/app.json

# Local presentation scratch — working material, never project documentation.
# Deliberately kept OUT of docs/: mkdocs builds every markdown file in docs_dir
# whether or not it appears in `nav:`, and that site is published, so anything
# dropped there ships publicly by default.
/docs-interview/

# Written by `devcontainer build` beside the config it was handed. Generated,
# host-specific, and never ours to ship — the launcher resolves Features
# through the devcontainer CLI and never reads a lockfile back, so committing
# one would only churn.
/.devcontainer/devcontainer-lock.json