# Zig's own build cache. Content-addressed, machine-local, and huge: the
# tracked snapshot had 1,407 files under .zig-cache/h alone, plus object files
# of 14-45 MB that jj refused to snapshot at all.
/.zig-cache/

# `zig build` installs exactly one artefact here (the flashable image, plus the
# ELF under -Delf). Both are derived from tracked sources.
/zig-out/

# Third-party package closure. Nothing here is ours and nothing here belongs in
# this history: one `-Dpardes` build materialised 2.6 GB across 106 packages and
# 42,736 files - SDL, wayland, glslang, mupdf, wasmtime, 25+ tree-sitter
# grammars - and jj tracked every one under 1 MiB while merely warning about the
# rest. Kept as a rule rather than a memory, because a fetch is one command away.
/zig-pkg/

# Scope captures: the .json IS the measurement and stays tracked. The .png is a
# 1.1 MB screenshot of that same JSON and is referenced by nothing.
/captures/*.png

# Vendor and standards-body documents under /cpu-docs/. 121 MB of PDFs that are
# not ours, and by the /zig-pkg/ rule above they do not belong in this history:
# cpu-docs/manifests/ records every source URL with a sha256, byte count and page
# count, so a re-fetch is one command away and a drifted document is detectable.
# The manifests and the index ARE the archive as far as this history is concerned,
# the same way /captures/ tracks the .json measurement and not the .png.
# The small text sources (.rst/.html/.md) stay tracked: those are the documents
# Espressif publishes in no other form, so there is no PDF to re-fetch instead.
/cpu-docs/**/*.pdf
/cpu-docs/**/*.zip

# Generated from experiments/report.typ, which computes its own figures from the CSVs beside it.
# The measurements are the artefact and stay tracked; a rebuilt PDF is not a measurement, and the
# page PNGs are a debugging convenience for checking a figure rendered.
/experiments/report.pdf
/experiments/fig-*.png