Lattice 0.8.8 - Integration Failure Surfacing And Diagnostics Cleanup

Added

• PaperDiagnosticContributor.snapshot() now includes the current JVM thread name as a currentThread diagnostic detail. This makes it easier to verify Folia scheduler context when inspecting a runtime snapshot through diagnostics.
• Reflective integration bootstrap failures now consistently surface the offending exception class and message through SimpleIntegration.failed(...) details. Diagnostics commands can read the same reason and message keys for every optional integration (previously only PacketEvents exposed them).

Changed

• PaperIntegrationBootstrap failure logging is now a concise single-line warning per integration instead of a full reflective stack trace. The exception class and message are still preserved in the details map on the returned SimpleIntegration so diagnostics remain rich.
• PaperDiagnosticContributor.snapshot() entries are still keyed by their original ordering; currentThread is appended after enabled.

Fixed

• Inconsistent diagnostic detail population for failed reflective integrations: Junction, PlaceholderAPI, Nexo, Oraxen, ItemsAdder, and CraftEngine bootstrap failures now report reason and message consistently with PacketEvents.

Compatibility

• No plugin authoring API changes.
• No stable @StableApi types were modified.
• No new transitive dependencies.
• Server owners who relied on full reflective stack traces in plugin logs see a single-line summary instead; the underlying exception class and message are still available through the diagnostic snapshot for any Integration with FAILED status.

Still Experimental (no change in status)

• dev.beryl.lattice.update
• dev.beryl.lattice.hook
• dev.beryl.lattice.template and annotation processors