AtomChat

Fixed issue #19, where a dedicated server could be forced onto the AWT toolkit by a client-side head start: the shared mixin plugin called AwtDisplay.claim() unconditionally, so a headless server with a stale DISPLAY variable tried to bring up X11, permanently poisoned GraphicsEnvironment$LocalGE, and made every later server-side image operation (WorldComment in the report) fail with NoClassDefFoundError. The claim now stays in the mixin-plugin phase - it has to run before Minecraft's Main caches the headless answer - but each target ships its own client-only plugin: NeoForge and Forge gate on FMLEnvironment.dist.isClient() and Fabric relies on the config's "environment": "client", so a dedicated server never loads AWT. The client startup log now prints the AWT outcome for field diagnosis.