Three services, one message bus

The game server isn't one process pretending to be modular — it's a real multi-module build: bus, common, login, channel, and supervisor, each with its own job. Login and channel are the two services a client actually talks to; the supervisor watches over both.

The bus is what actually ties them together — a real message bus for service-to-service coordination, not a shared database table doing double duty as a mailbox. It's also what the live status page listens in on to know who's actually up, instead of a separate system someone has to remember to keep in sync.

It runs as a Gradle multi-module reactor now too, migrated off an older Maven setup — one real build, five real modules.