Velocity support. The same jar now also runs as a Velocity plugin - the update half, exactly like BungeeCord and Waterfall: /pm update check, install, list and reload-config, plus /pm search and /pm download. Plugin control (enable, disable, load, unload, reload) stays Bukkit-only; Velocity wires its plugins up once at startup through Guice and offers no runtime unload at all.

• New descriptor: the jar carries a velocity-plugin.json alongside plugin.yml and bungee.yml
• Velocity plugins are recognised by their velocity-plugin.json, on every platform - a proxy full of Velocity plugins is now scanned properly instead of coming back empty
• Modrinth is queried with the velocity loader, Hangar with the VELOCITY platform
• Parked updates are applied on proxy shutdown, the same way BungeeCord does it
• Compiled against Velocity API 3.1.1 and only long-stable API, so one jar still covers every platform

Driven through a live Velocity 3.5.0 proxy: a real plugin recognised by its velocity-plugin.json, matched on Modrinth, the update downloaded, parked and swapped in as the proxy shut down, plus a search and a download of a plugin that was not installed.

Fixed

• /pm update ... did nothing on a proxy. On BungeeCord and Waterfall - and in 1.1.0 on Velocity - the leading "update" was passed on instead of cut off, so exactly the command the help prints fell through to that same help. Both spellings work now, /pm check and /pm update check, and "update" is offered in tab completion.
• /pm load showed nothing to pick from: tab completion offered no file names, and the command without an argument only printed its usage. It now completes the jars in the plugins folder that are not loaded yet, and lists them when called without an argument.
• 1.1.0 threw on Velocity while starting up ("The plugin main instance is automatically registered") - Velocity registers the main class as a listener itself.

BungeeCord and Waterfall still have not been through a live proxy.