# 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

# 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/

# Ruff stuff:
.ruff_cache/

# PyPI configuration file
.pypirc

# Cursor
#  Cursor is an AI-powered code editor. `.cursorignore` specifies files/directories to
#  exclude from AI features like autocomplete and code analysis. Recommended for sensitive data
#  refer to https://docs.cursor.com/context/ignore-files
.cursorignore
.cursorindexingignore

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


# Pakunoda stuff (we have a lot of notes which shouldn't be tracked)
env/
*.md
.md 
*.qcow2
*.elf
.elf
.img
*.img
*.elf.meta.json
.elf.meta.json
experiments/dumps/acquired/
*.lime
*.tex
.tex

# Editor/pipeline backup copies. `*.tex` above does not match a file whose
# name *ends* in .bak (e.g. `cv.tex.pre-a2.bak`), so without these a backup
# stays re-addable after it is untracked. Note gitignore never untracks an
# already-tracked file -- these only take effect once `git rm --cached` has
# removed it from the index.
*.bak
*.bak.json

.lime
experiments/dumps/*
!experiments/dumps/acquire_dump.sh
!experiments/dumps/download_images.sh
!experiments/dumps/run_stream_c.sh
# Tracked as of 2026-08-07: this wrapper carried a comment claiming the script
# detected the guest's running kernel, which it never did. That false claim is
# how two corpus rows ended up labelled with a kernel they were not running,
# and it survived because the file was never under review.
!experiments/dumps/run_stream_c2.sh
!experiments/dumps/update_manifest.py
!experiments/dumps/manifest.json
tests/fixtures/dumps/

# misc
tools/
.*/
# Exceptions: GitHub Actions and key project docs
!.github/
!.github/workflows/
!.github/workflows/*.yml
!README.md
# User-facing docs README.md links to. These MUST stay re-included: `*.md`
# above swallows everything else, which is how README.md ended up linking to a
# README_ARTIFACT.md that is invisible in a fresh clone. Add a `!` line here for
# any new doc the README points at, and verify with `git check-ignore -v <path>`.
!docs/GROUND_TRUTH_HARNESS.md
!docs/PROFILE_CACHE.md
.xz
*.xz
.pkl
*.pkl
*.lock
.lock
paper/
*.dwarf
!README_ARTIFACT.md

.DS_Store


# Ad-hoc post-paper audit scripts and their outputs
/an*.py
/mkfig.py
/agree_table.json
/audit_isf_metrics.csv
/fig_metric_audit.png
/handoff_metric.json
/timing_table*.json
/vol3_resolved_*.json

# Superseded plugin-coverage runs; keep only what the paper and
# run_gt_ablation.py depend on
!experiments/tier1_results/pub/timing.json
experiments/plugin_coverage_results/*/
!experiments/plugin_coverage_results/gt_v2/
!experiments/plugin_coverage_results/pakunoda_final10/
!experiments/plugin_coverage_results/pakunoda_final11/
!experiments/plugin_coverage_results/gt_ablation/
# The stream-gate evidence: both arms' coverage JSON, the ablation
# JSON/TeX and the stderr sidecars behind pak_only_fail on
# debian-12-arm64. 32 KB, and it is the only reproducible basis for a
# number the paper's correctness claim rests on -- a disputed 148/160
# was already lost once to /tmp.
!experiments/plugin_coverage_results/gate_a5b_2026-08-03/

# Revised paper workspace (v1). Untracked on purpose: it holds the
# post-audit rewrite plus its regenerated results, and `paper/` stays the
# frozen v0 reference so every change is diffable against it.
/paper_v1/


# pakunoda artifacts
vol3-sweep-*
recovered_fs.tar.gz
experiments/ground_truth/isf_cache.snapshot*
tests/unit/test_consolidate_dumps.py
# The corpus consolidator lives at the repo root because every path it derives
# hangs off its own location, but it names private absolute paths (ownCloud
# case studies, ~/Downloads), so it stays out of the repo like its test.
/consolidate_dumps.py
