Lattice 0.8.9 - Testability, Diagnostic Clarity, and Release Docs

Added

• PaperDiagnosticContributor snapshot detail keys are now documented in Javadoc: plugin, version, dataFolder, enabled, currentThread. Plugin authors reading the contributor class directly can see the snapshot shape without consulting the source.
• PaperIntegrationBootstrap.failureMessage(Throwable) and failureDetails(Throwable) are now static package-private so the formatting contract can be locked by a unit test without going through the reflective bridges.
• PaperDiagnosticContributor.detailsFor(Path, String, String, boolean) is now a package-private helper, parameter-validated, so the snapshot detail-map shape is unit-testable without instantiating JavaPlugin (whose constructor is unsupported outside the Bukkit loader).
• PaperIntegrationBootstrapFailureLoggingTest locks the failure-logging contract for the 7 reflective integration bootstrap paths.
• PaperDiagnosticContributorTest locks the currentThread snapshot detail so it cannot accidentally drift to a hardcoded value.

Changed

• PaperDiagnosticContributor.detailsFor(...) parameter order is now (Path dataFolder, String pluginName, String pluginVersion, boolean enabled). The Path is first to visually break up two adjacent String parameters of different meaning and remove a call-site transposition footgun. The sole caller (snapshot()) was updated to match. Observable output (the snapshot detail map keys and values) is unchanged.
• docs/api-guide.md#diagnostics now spells out the snapshot detail keys for the paper contributor plus the integration details map shape (reason/message for failures, apiClass/version for an AVAILABLE PacketEvents binding).
• docs/build-and-release.md clarifies that both GitHub Release and Modrinth Release workflows auto-trigger on push events matching v* tag patterns. A normal git push origin v<version> therefore publishes to Maven Central, the GitHub Packages mirror, GitHub Release, and Modrinth in parallel. Manual gh workflow run "Modrinth Release" is reserved for recovery; the workflow already performs its own idempotency check against the Modrinth API before publishing.
• PaperIntegrationBootstrapFailureLoggingTest.failureDetailsMapIsImmutable now uses assertThrows(UnsupportedOperationException.class, ...) to actually verify the Map.of immutability claim (replaced a previous containsKey tautology).

Fixed

• A transposition footgun in PaperDiagnosticContributor.detailsFor(...): the previous (String, String, Path, boolean) parameter list placed two strings of different meaning adjacent to each other. Reorder eliminates this hazard without changing observable behavior.

Compatibility

• No plugin authoring API changes.
• No stable @StableApi types were modified.
• No new transitive dependencies.
• Tests are new additions only; no existing tests were changed or removed.
• failureDetails and failureMessage were previously private static and remain @InternalApi; they are now static package-private to satisfy the same internal-only contract.

Still Experimental (no change in status)

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