cooldowns survive a relog, the MOTD prints, and lost channels come back

- a cooldown still running when you log out and back in keeps sweeping instead of vanishing, and another character no longer inherits the previous session's cooldowns (2116)
- the server's Welcome and Patch 1.12 lines print at login in system yellow, and a character whose General, Trade and LocalDefense had gone silent for good gets them back at the next login (2119, 2120)
- the stock Interface Options window loads hidden beside ours, so pfUI's options skin finds the real thing; the Auto-join Guild Recruitment Channel row has a real store, and a /reload no longer trips on its camera dropdowns (2115)
- the combat log words a power gain on the display scale, so MikScrollingBattleText shows +1 Rage where it showed +10; a 1.12 predicate answers 1 or nil rather than a Lua boolean, the test ColorPickerPlus makes (2117, 2118)
- a Lua error quotes a program element with a backquote the way 5.0 does, so AceLibrary's argument checks report their caller instead of raising inside the error path (2122)

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

third_party/lua-src/BENILLA.md

@@ -41,17 +41,18 @@ downgrade, and it is the entire reason this is a one-hunk fork rather than a ven
 
 ## The delta, and the command that proves it
 
-**Current state: seven hunks, in three files.** `src/lib.rs` additionally differs by having Lua
+**Current state: eight hunks, in three files.** `src/lib.rs` additionally differs by having Lua
 5.2/5.3/5.4/5.5 stripped from the `Version` enum (with their source trees deleted) — benilla builds
 5.1 and only 5.1, and a fork that still *offered* the other four would answer a request for one with
 a missing directory at build time instead of a compile error.
 
-**Four hunks restore what 5.1 changed or removed:**
+**Five hunks restore what 5.1 changed or removed:**
 
 | file | hunk | why | record |
 |---|---|---|---|
 | `lvm.c` | 5.0's `OP_TFORPREP` table→`next` substitution, folded into the top of `OP_TFORLOOP` | `for k, v in someTable do` raised "attempt to call a table value"; it was the first session-start error for **60** corpus addons | 1215 |
 | `luaconf.h` | `LUA_COMPAT_LSTR` `1` → `2` | 5.1 kept 5.0's nesting machinery and put an advisory error in front of it; two corpus addons died on "nesting of `[[...]]` is deprecated" | — |
+| `luaconf.h` | `LUA_QL(x)` back to 5.0's `` `x' `` from 5.1's `'x'` | every Lua error message quotes a program element, and `WoW.exe`'s own `.rdata` carries all five formats in the 5.0 spelling (`` bad argument #%d to `%s' (%s) ``, `` attempt to %s %s `%s' (a %s value) ``, `` %s:%d: %s near `%s' `` at the client's `0x87217c`, …). ~80 corpus addons ship AceLibrary, whose `argCheck` parses its own caller back out of `debugstack()` with a pattern that requires the backquote | 2122 |
 | `lparser.c` | 5.0's compat-semicolon skip restored at the top of `constructor()`'s field loop — 5.0's own line, verbatim, comment included | one extra `;` after a field separator inside a table constructor (`Back_Title = AL["Factions"];;`, ×20 in AtlasLoot's `ButtonRegistry.lua`) parses on the client and died here with "unexpected symbol near `;`"; statement-level `;;` stays rejected by both dialects | 1315 |
 | `lparser.c` | `recfield`'s `cc->nh++` moved back INSIDE its `TK_NAME` arm — 5.0's own placement | a `[expr] = value` constructor field must credit **neither** `OP_NEWTABLE` size hint, so the table is born on the dummy node, the first store rehashes, and the dense integer keys land in an ARRAY part that `next` walks ascending. 5.1 pre-sizes a node vector instead and leaves them in the hash, where `next` is slot order — so every list in every saved-variables file came back scrambled (Bagnon's keyring drew first) | 2111 |
 
@@ -85,7 +86,7 @@ diff -r third_party/lua-src/lua-5.1.5 \
   ~/.cargo/registry/src/*/lua-src-550.0.0/lua-5.1.5
 ```
 
-That must print **exactly** the seven hunks in the tables above and nothing else. If it ever prints
+That must print **exactly** the eight hunks in the tables above and nothing else. If it ever prints
 more, something crept in.
 
 ## Status of the payload

third_party/lua-src/lua-5.1.5/luaconf.h

@@ -200,7 +200,24 @@
 @@ LUA_QL describes how error messages quote program elements.
 ** CHANGE it if you want a different appearance.
 */
-#define LUA_QL(x)	"'" x "'"
+/*
+** BENILLA (decision 2122): 1.12's Lua is 5.0, which quotes every program element in an error
+** message with a BACKQUOTE and an apostrophe. 5.1 introduced this macro and made it two
+** apostrophes. Read out of WoW.exe's own .rdata, which carries all five of the formats this macro
+** feeds, in the 5.0 spelling:
+**
+**   bad argument #%d to `%s' (%s)          lauxlib.c luaL_argerror
+**   calling `%s' on bad self (%s)          lauxlib.c luaL_argerror's method arm
+**   attempt to %s %s `%s' (a %s value)     ldebug.c  luaG_typeerror
+**   %s:%d: %s near `%s'                    llex.c    luaX_lexerror (the client's own 0x87217c)
+**    in function `%s'                      ldblib.c  the traceback line debugstack renders
+**
+** The last one is not cosmetic: 80+ corpus addons ship AceLibrary, whose argCheck reads its own
+** caller back out of `debugstack()` with the pattern "`argCheck'.-([`<].-['>])", a pattern
+** cannot match 5.1's quoting, so the nil it gets is then passed to a %s and raises inside the
+** error path.
+*/
+#define LUA_QL(x)	"`" x "'"
 #define LUA_QS		LUA_QL("%s")