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>

third_party/lua-src/Cargo.toml

@@ -7,11 +7,8 @@
 # error for 60 of 218 addons at session start, three quarters of everything that breaks in a running
 # session. It is not reachable from inside Lua: not a library function, not a global, an OPCODE.
 #
-# WHAT IS AND IS NOT CHANGED. **Right now: nothing.** The `lua-5.1.5/` tree here is byte-identical
-# to upstream's, and this fork was landed inert on purpose — the pipeline is proven transparent
-# BEFORE any behavioural payload goes into it, so that when the suite moves, the patch is the only
-# thing that could have moved it. `BENILLA.md` carries the current state and the one command that
-# verifies the sources against upstream.
+# WHAT IS AND IS NOT CHANGED: `BENILLA.md` lists every hunk against upstream's `lua-5.1.5/` tree
+# (eight, in three files) and the one command that verifies the sources against the registry copy.
 #
 # When the payload does land we are still NOT adopting Lua 5.0: we stay on 5.1.5 and restore the
 # behaviour of one opcode Lua itself shipped and labelled "for compatibility only", so every other