TickScope 1.2.0

Wider version support

One jar now covers Paper 1.18.2 through 26.2. Nothing in the exporter needed a modern API — the
only blocker was a single call in the status command. The build targets Java 17, which is Minecraft
1.18's own runtime requirement, so there is no version-specific code, no multi-module build, and no
meaningful change in size.

Verified against real 1.18.2, 1.19.4, 1.20.6, 1.21.4 and 26.2 servers: identical metric families,
identical label values, no startup warnings.

Optional bearer auth on the endpoint

The metrics endpoint has always been open, on the assumption it sits on loopback or behind a
firewall. That is not available to everyone, so auth-token in config.yml now requires
Authorization: Bearer <token> on every scrape.

It is empty by default, so nothing changes for an existing install. The comparison is
constant-time, and a refused scrape gets an empty body rather than anything describing the server.

This is not confidentiality — the endpoint is plain HTTP and the token crosses the wire in the clear.
Put a TLS-terminating reverse proxy in front if the scrape path leaves a network you control.

Fixed

Entity type labels are now the Minecraft registry name rather than the Bukkit enum name. Bukkit
realigned the enum with the registry in 1.20.5, so on older servers 18 of 114 entity types were
labelled differently — including dropped_item, which is item everywhere now. No effect on
26.2, where the two already agree, so existing dashboards and history are untouched.

Upgrading

Drop the new jar in and restart. No configuration changes required.