Files
benilla-octo/.gitignore
T
SamandClaude Fable 5.1 aff5203393 a fresh clone gets the whole project, and the maintainer's tooling moves out
What a clone lacked: the gates went green with a thousand skipped tests and said nothing, every
login script assumed a worktree-pool slot and its probe account, the client defaulted to the
maintainer's account, a docker path and a home directory were in the code, the temp files broke
on GNU coreutils, and two generators could only run against a sibling repo.

Now the test gates print how many data-gated tests skipped and why; a scripted run logs in as
the account its checkout declares in `.probe-identity` or as the three variables name, never a
default, and the client refuses a scripted login on any other account; the event and message
tables regenerate from vendored inputs, byte for byte; the docs state the real prerequisites.

Out of the tree, into the maintainer's own tooling: the worktree pool, its hooks, the perf leg
runner, the cross-platform compile and the Vulkan container leg — a way of working, and setups
not every machine has. One hook stays: no writes into the install.

Two tests that could never run are gone with their subject: the quest-timer geometry diff
compared a copy of the window that no longer exists (and joined a chain path onto a folder, so
it always skipped), and the FrameXML flag gate now reads the stock files off the player's own
patch chain instead of an extracted folder only one machine had.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-09-23 17:27:14 +07:00

49 lines
1.8 KiB
Plaintext

# Rust build artifacts
/target/
**/*.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 (decision 0954, moved out of the install by 1175) ---
# 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); 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" (decision 0610).
trace-*.json
# OS / editor cruft
.DS_Store
*.swp
/.idea/
# Claude Code: share the project hooks + settings + slash commands + skills, ignore per-machine state.
/.claude/*
!/.claude/settings.json
!/.claude/hooks/
!/.claude/commands/
!/.claude/skills/
/.claude/settings.local.json
# Python bytecode from the `scripts/` tooling.
__pycache__/
# The vanilla addon corpus the UI engine's real-addon tests read (third-party content, decision
# 2329): a symlink beside `WoW`, or `BENILLA_ADDON_CORPUS`.
/wow-addons-vanilla