__pycache__/
*.py[cod]
*.egg-info/
dist/
build/
*.egg
.pytest_cache/
.eggs/
.coverage

# Sphinx build output
docs/_build/

# Project-specific config (generated per-project, not part of the package)
vaibify.yml

# Build context files generated by 'vaibify build'
docker/binaries.env
docker/container.conf
docker/director.py
docker/latexConnector.py
docker/overleafSync.py
docker/pip-flags.txt
docker/zenodoClient.py
docker/requirements.txt
docker/system-packages.txt
docker/workflows/
# Build contexts are staged under ~/.vaibify/build/ since 2026-07-27,
# so nothing generated should land in the packaged context any more.
# Kept as a backstop: these names were untracked-and-unignored for
# months and rode a `git mv` straight into a wheel, where a stale
# requirements.txt would have silently changed the image.
vaibify/containerImage/docs-staged/
vaibify/containerImage/director.py
vaibify/containerImage/overleafSync.py
vaibify/containerImage/latexConnector.py
vaibify/containerImage/zenodoClient.py
vaibify/containerImage/container.conf
vaibify/containerImage/requirements.txt
vaibify/containerImage/system-packages.txt
vaibify/containerImage/pip-flags.txt
vaibify/containerImage/binaries.env

# Runtime state written by vaibify itself when run from this checkout
/.vaibify/

# Generated by setuptools_scm at build/install time (see pyproject.toml
# write_to); regenerated on every build, so never tracked.
vaibify/_version.py

# Browser-lane failure artifacts (trace, video, screenshot)
test-results/

# Browser-lane scratch homes: the picker's registry-isolation makes a
# throwaway project tree beneath the checkout (the path guard requires
# it be under the user's home). A killed run leaves one behind; keeping
# them here means a stray tree can never be git-added (a bare repo-root
# temp dir once shipped into history as tmpu2uv9b_9/).
/.browserLaneTmp/
