# Rust build artifacts
/target/
/dist/
/.env
/.env.*
# Locally supplied patch source content.
/src/Data/
**/*.rs.bk
# Cargo.lock IS committed (this workspace produces binaries).

# --- Blizzard-owned content: NEVER commit ---
# The user's legally-installed 1.12.1 client. Read at runtime; not redistributed.
/WoW
# Cached / extracted assets derived from the user's install.
/extracted/
/out/
# Real client files used as test fixtures (document expected paths, do not commit).
**/tests/fixtures/

# --- benilla's own local state ---
# The one folder benilla persists into: config.toml, macros/, bindings/, saved-variables.lua,
# camera/. A dev build resolves it to the main checkout (so linked worktrees share one, bar a
# worktree with a .probe-identity, which keeps its own); a release build puts it beside the
# binary — which is why it is not called `benilla/`: that name collides with the binary of the
# same name. Machine-local by definition — `crate::local_state`
# is the only thing in the tree that may write it.
/benilla-config

# The account a scripted run from this checkout logs in as (scripts/probe-identity.sh and the
# client's account guard read it): WOW_USER=, WOW_PASS=, WOW_CHAR=, one per line. A credential.
/.probe-identity

# Profiling output: `--features bevy/trace_chrome` drops a multi-GB flame chart in the cwd, which
# otherwise leaves the checkout "dirty".
trace-*.json

# OS / editor cruft
.DS_Store
*.swp
/.idea/
# Claude Code: settings and skills under .claude/ are each person's own.
/.claude/

# Python bytecode from the `scripts/` tooling.
__pycache__/

# The vanilla addon corpus the UI engine's real-addon tests read (third-party content): a symlink
# beside `WoW`, or `BENILLA_ADDON_CORPUS`.
/wow-addons-vanilla
.vscode

# graphify: commit the graph and report only. Its caches, scratch files and the interpreter
# path it saved are machine-local; the AST cache lands under the scan root (crates/).
/graphify-out/cache/
/graphify-out/.graphify_*
/graphify-out/cost.json
/crates/graphify-out/
