base exe patch moves the per-chapter coin and flag arrays into free .data space (128 entries), so every testlevel chapter is safe (revision 2, caches rebuilt once); new projects start on a free chapter from 32, manual shows number ranges, texture swatch caches follow texture edits, stray levelbau.md.orig removed

notes/llamamod-app.md

@@ -121,7 +121,8 @@ Each contains `68 90 E0 56 00` (push offset subkey string, VA 0x56E090) followed
 byte `02` of each `push 80000002h` becomes `01` (HKEY_CURRENT_USER), so no admin rights are needed
 on Windows. German CD (`groove.exe` MD5 697d67a31c20079838c662d8187dbd86, 1,642,496 bytes),
 file offsets of the changed bytes: **0x579B, 0x57D0, 0x5810, 0x5859, 0x5880** (original 02,
-new 01; patched MD5 6199a42eb7582b2a70b1ac6e29f00f43). The patcher searches the pattern
+new 01; MD5 with only this part 6199a42eb7582b2a70b1ac6e29f00f43; the base patch also relocates the
+world-9 level records, see "groove.exe patches" below). The patcher searches the pattern
 (push of the subkey string VA + push HKLM) instead of fixed offsets, so other language builds work
 if their code is the same.
 
@@ -222,8 +223,10 @@ reads a CD folder, collects writes in `ctx.written`, resolves options (defaults
 
 `game/groove.exe` is rebuilt on every apply: `original/hd/groove.exe` → HKCU base patch
 (`platform/ExePatcher`, owner "base", always first) → exe changes of the enabled mods in apply
-order. Without exe mods the result is byte-identical to the old ExePatcher output; "Restore
-original" goes back to it. A mod gets the shared image with `ctx.exe()`; all changes are
+order. Without exe mods the result is byte-identical to `ExePatcher.patch` (installer output);
+"Restore original" goes back to it. The base patch (REVISION 2) = HKCU + `relocateLevelRecords`
+(world-9 coin/flag arrays moved into .data's page slack, 4-byte address operands only, see
+testlevel-chapters.md); `ExePatcher.changes` lists both as byte runs. A mod gets the shared image with `ctx.exe()`; all changes are
 attributed to the mod id, journaled into the mod's cache manifest (`"exe": [...]`) and replayed
 (with full verification) on a cache hit. Every patch/allocation is logged in apply.log
 (`exe <mod>: patch 0x… n bytes – label`).