AtomChat

Fixed image codes with a different spelling (lower-case tag, reordered parameters) being dumped into chat as raw protocol text with a clickable tail that threw when clicked; one tolerant grammar now covers every spelling, and a code we cannot read shows a placeholder instead of the protocol. Fixed the image picker crashing with ClassNotFoundException when another mod bundles FlatLaf under the same public package name; our copy is now packed under a private package and can no longer be shadowed. Fixed incremental builds silently losing the Mixin refmap, which produced jars that died at startup with "No refMap loaded"; a build gate now fails the build instead. Fixed a failed panel blur retrying and logging on every frame, burying its own cause; the first failure now disables it for the session and the panel keeps its solid background. Added a one-line build identity at startup (version, loader, the jar actually loaded, its SHA-256 and the commit it came from), so a single log line pins down which build produced it. Added a full environment summary under the debug switch: which jar the FlatLaf in use came from, whether the Skija native library loaded and how long it took, the GPU and driver, and the switches. It is emitted as one log record, so copying it cannot be cut apart by other mods' lines. Added input logging under the debug switch (key, character, click point and the panel coordinates it maps to). The UI is drawn by Skia, so none of the usual widget debugging applies, and this is the only reliable way to chase a button that does nothing. Changed the render-state save/restore to cover what Skia moves (blend equation, blend colour, front face and the stencil family); a leak there raises no error at all and shows up as another mod's geometry missing pixels or facing backwards. Docs: both troubleshooting pages now explain how to turn debug on and which lines to send. Fixed the Skija row of the environment summary contradicting itself on NeoForge: one half said "no native bundled" while the other said "natives loaded in 181 ms". The native was always fine; the diagnostic was wrong, because the version lookup asks the loader to list a resource inside a nested jar, which Forge does, NeoForge does not, and Fabric flattens into place. The load result is now read first, only a real load failure may claim the native is missing, and otherwise the version is read straight out of our own artifact. This is a same-version re-upload; tell the two 0.2.11 builds apart by the sha256 in their log.