the repo carries no Claude Code settings (#23)

A committed .claude/settings.json bound everyone who opens the repo in Claude Code: it switched
their auto memory off, and its one hook guarded the install against Claude's Edit and Write
tools only, never a write through the shell or by another agent. The rule it backed is enforced
for every tool by the code and by scripts/smoke.sh's install watch, which METHOD now cites. jq is
no longer a prerequisite, and .gitignore shares only the skills under .claude/.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

docs/CONTRIBUTING.md

@@ -39,7 +39,7 @@ fork, and forks are welcome.
 - **The toolchain.** Stable Rust (`rust-toolchain.toml` adds clippy and rustfmt) and a C
   compiler, because the client's Lua is vendored and built from source. On macOS the Xcode
   command line tools, which also supply libclang for the audio bindings; on Linux the ALSA and
-  udev development packages and pkg-config. `python3` runs two of the gates, and `jq` the hooks.
+  udev development packages and pkg-config. `python3` runs two of the gates.
 - **A 1.12.1 install of your own.** `WOW_DATA=<its Data folder>`, or a `WoW` link at the repo
   root, which only a dev build sees: the player build looks for `Data/` or `WoW/Data/` beside
   the binary. benilla reads the install and never writes into it. `WOW_DATA=` (set, empty)

docs/METHOD.md

@@ -40,8 +40,7 @@ comment naming the reference fact and why we differ. Anything else is a fork.
   interface code: FrameXML and GlueXML run off the player's own patch chain, and our own
   counterparts under `assets/ui` stay until they retire.
 - **The install is read-only.** benilla never writes into the WoW folder: no screenshot, log,
-  cache or scratch file. A hook blocks such a write at the tool call, and `scripts/smoke.sh`
-  fails a run that leaves the install changed.
+  cache or scratch file. `scripts/smoke.sh` fails a run that leaves the install changed.
 - **Local state lives in one folder**, `benilla-config/` beside the binary, and every path to
   it resolves through `crate::local_state`. Player settings are CVars persisted as a diff in
   `benilla-config/config.toml`.
@@ -85,7 +84,6 @@ comment naming the reference fact and why we differ. Anything else is a fork.
 - **Platform seams**: a `cfg(target_os)`, a `[target.'cfg(…)']` dependency, a `#[link]` or an
   `extern "system"` is invisible to the gates of the platform you are on. Say in the commit
   which platforms you built.
-- One hook: no writes into the install. Everything else is a gate or discipline.
 
 ## The local server