fix: use .versions | keys | last for deterministic latest MC version

[TimInTech]

The Fill v3 API returns .versions as an object (keys = MC version strings), not an array. Using keys | last yields the lexicographically highest (= newest) version reliably. Fixes broken .versions | last (was null on object input) and the non-deterministic keys_unsorted[0] variant.

Pull Request – Simulation Only

Summary

Describe what this PR changes (scripts, docs). No commands are executed in this workspace.

Checklist

• No commands executed locally; all steps are simulated/explained only.
• Changes are limited to scripts and/or documentation.
• SIMULATION.md updated to reflect behavior and risks.
• If adding a new script or option, included example usage commands (chmod +x; ./script; screen -r ...).
• Security considerations addressed (least-privilege user, ports, backups).

Testing (Simulation)

Explain expected side effects if run on a proper host (files created, services started, ports opened). Include rollback/cleanup notes.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 417bcdac6c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Use semantic version ordering for latest lookup

jq '.versions | keys | last' chooses the lexicographically largest key, not the newest Minecraft version; with version strings this can select older releases (for example 1.9.x compares greater than 1.21.x as plain text). In environments where Paper exposes multiple historical versions, this will download and run an outdated server instead of the latest stable release, so the version selection needs semantic ordering (or API-provided ordering) rather than string-key ordering.

Useful? React with 👍 / 👎.

[TimInTech]

Fixed directly on main in f8cca25. Thanks for the contribution!

Note: The Codex bot raised a valid concern about keys | last using lexicographic instead of semantic version ordering (e.g. 1.9.x > 1.21.x as strings). This has been addressed in a follow-up commit using proper semantic version sorting via jq.