Docs: local Sacred Gold install required, no hard-coded game path

README explains --game-dir and the stored GameDir; the VS Code launch
uses the stored path and builds through build.ps1.

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

CLAUDE.md

@@ -14,9 +14,11 @@ the work so far is **mods** — behaviour changes on top of the original
 auto-attack, skill reworks, respec, map fixes, ...). The game stays playable
 at every step; the user plays it to test.
 
-- Target binary: the original `sacred.exe` in `D:\Gaming\Sacred Gold\`
-  (path in `build\x86-debug\sacredK.ini`, `[paths] GameDir`). Ignore the
-  `SacredReborn*` files in that folder.
+- Target binary: the original `sacred.exe` of a local Sacred Gold 2.28
+  installation (see `README.md`, Supported build). The game is not in the
+  repo; its folder is given to the launcher once (`--game-dir`) and kept in
+  `build\<preset>\sacredK.ini`, `[paths] GameDir`. Read it from there; never
+  hard-code a local path in code, docs or configs.
 - Game texts are German (Fertigkeiten, Attribute, Blitzschlag, ...); keep the
   game's names when talking about features.
 - The user's monitor is 3440x1440; the game renders about 1835x768 scaled up.