Lattice

Added

• Added direct standalone host contract coverage for managed plugin registration, duplicate registration protection, handle detach, host diagnostics, reverse-order shutdown, and shared storage cleanup.
• Added an experimental UpdateService for GitHub release checks, typed update results, release assets, and explicit jar install requests.
• Added PaperUpdateInstaller so Paper plugins can implement confirmed update commands that back up the old jar into Lattice/Old, replace the plugin jar, and prompt for a server restart.

Changed

• Standalone host shutdown now disables all managed plugin runtimes in reverse registration order even when one dependent plugin fails during disable.
• Standalone host close now continues through managed plugin disable, shared storage pool close, and handle cleanup before rethrowing a collected shutdown failure.
• The standalone Lattice plugin shutdown path now continues through managed plugin disable, host runtime disable, Bukkit service unregister, and host close before rethrowing a collected shutdown failure.
• LatticeRuntime#disable() now closes registered services and cancels tasks even when called before the runtime has loaded.
• The standalone Lattice plugin now performs a best-effort startup check for newer Lattice GitHub releases and stays silent when it is already current.
• Public docs now describe the shared runtime host lifecycle, dependent plugin detach behavior, and the disable() before load() cleanup guarantee.
• Public docs now include update-check and confirmed-install examples for plugin-owned admin commands.

Fixed

• A failed dependent plugin disable no longer prevents later managed plugins from being disabled during standalone host shutdown.
• Shared JDBC pools are now closed during standalone host close even if a managed plugin fails while disabling.
• Hosted plugin handles are now detached when a newly created runtime is disabled before it has loaded.
• The runtime lifecycle docs no longer duplicate the enable() lifecycle step.

Compatibility

• Existing LatticeHost, LatticePluginHandle, and LatticeRuntime method signatures are unchanged.
• Dependent plugins using LatticePaperPlugin or LatticePaper.bootstrap(...) do not need code changes.
• Shutdown failures are still surfaced to the caller, but cleanup now continues before the failure is rethrown.
• Update installs are opt-in and must be triggered by plugin code; no dependent plugin jar is replaced automatically.