Initial spike on the project (via Claude)

Add Webswing spike: MegaMek Swing client rendered in a browser master

Stands up the three pieces needed to judge server-side rendering as an alternative to CheerpJ: HostForHuman - MegaMek Server + Princess bot on :8850, leaving one scenario faction as an unclaimed ghost for a human to log into. Bots are deliberately held in the lounge until that slot stops being a ghost; readying them earlier satisfies checkReady() (which skips ghosts) and starts the game without the human. webswing.config - Webswing Lite 26.4.5 launching the stock MegaMek Swing client via Desktop launcher, mainClass megamek.MegaMek, args "-client -server localhost -port 8850 -player_name TraineeA". start.sh - brings both up. Verified so far: the client args are correct and a native JVM client connects and claims the TraineeA slot (host logs "human connected -> readying bots"). Webswing serves /megamek with HTTP 200. NOT yet verified: that Webswing actually renders the Swing client in a browser - that needs a real browser. Webswing Lite requires Java 21+, which MegaMek also needs, so unlike CheerpJ this path needs no backport and no socket-layer workaround. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>


+201
4 changed files