.gitignore

# compiled load-test binaries (rebuilt by the runners)
memory/mock
memory/ugen
perf/mock
perf/ugen
# per-run generated configs + gateway build/venv artifacts.
#
# NOT `gateways/*/*.gen.*`. That glob ends in `.*`, so it matched the rendered `config.gen.yaml` AND
# the `config.gen.yaml.tmpl` it is rendered FROM - and the template is source. It kept the config
# templates of 12 of the 13 gateways out of the repository, which nobody noticed while the box was
# rsynced a working tree that had them on disk. The moment boxes started cloning a pinned commit,
# every one of those gateways failed validation on the box with "definition.json declares config
# template X, but X does not exist" - the same shape of defect as the unanchored `bin/` below, and
# found the same way, by a box getting only what git actually tracks.
#
# The rules below name the RENDERED suffix exactly, so a `.tmpl` can never be swept up again.
gateways/*/*.gen.yaml
gateways/*/*.gen.yml
gateways/*/venv/
# transient EC2 driver logs (the results JSON + charts are the durable evidence)
results/*.log
# per-run gateway launch log (each docker manifest writes gateways/<gw>/launch.log at gw_launch)
gateways/*/launch.log
# rust mock build artifacts
mock/target/
mock/target-linux/
mock/target-x86/
# python bytecode cache
__pycache__/
*.pyc
# prebuilt bench rig binaries live in the `rig` GitHub release, not git.
# ANCHORED to the repo root on purpose: unanchored, `bin/` also matches engine/src/bin/, which is
# where the otb entry point lives, and it silently kept the engine's whole CLI out of the repository.
/bin/
# box-qualification scratch: the per-box stage1/stage2 probe output and the assembled verdict the
# orchestrator ships back onto the box. The DURABLE record is rig.box_qualify inside each snapshot
# (results/snapshots/), which is committed — these are the working files that produced it.
results/box-qualify/
target/

# Rendered gateway config. The TEMPLATE (*.tmpl) is the source and is tracked; what the harness
# renders from it at launch is output, and a stale rendered file in the tree is a config someone
# could read as authoritative when the template beside it says something else.
gateways/*/*.gen.yaml
gateways/*/*.gen.yml
# Ignore the CONTENTS of the runtime data dir, not the dir itself: a template that lives inside it is
# still source. Excluding the directory outright would make the negation below unreachable, because
# git never descends into an excluded directory to reconsider a file in it.
gateways/*/bfdata/*
!gateways/*/bfdata/*.tmpl
gateways/*/config/*.toml
gateways/*/launch.log

# Layout-review screenshots from site/screenshot-matrix.mjs: ~138 full-page PNGs of every page x
# every control combination x three widths. Regenerable from the working tree in one command, and a
# committed set would be a stale picture of a CSS file that moved - the CSS is the durable artifact.
results/screenshots/

# Internal working notes - never published to the public board repo.
KICKOFF.md