Two changes, both prompted by review. Patches are now unified diffs in patches/patchset/ rather than copied source files. A copied file silently discards upstream changes to that file when rebasing onto a new MegaMek release; a diff either applies or fails loudly. build-patched-jar.sh copies only the touched files into a scratch dir, applies the patchset with -p1 there, compiles just those, and injects the classes into a copy of the release jar. The MegaMek source and release trees are never mutated, so the same patches apply to a fresh checkout. The multi-tenancy patch is no longer built. It is archived as a diff under patches/archive/multitenancy/ with a note on why: the architecture settled on one game per container, so the Server.getServerInstance() static never bites, and the patch was insufficient anyway. Verified the built jar now differs from stock MegaMek.jar in exactly one entry: entries: stock=4458 patched=4458 differing: megamek/client/ui/clientGUI/audio/Sound.class Server.class and AbstractGameManager.class are byte-identical to stock. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>