v0.6.0-rc.3

Summary

Release candidate built on v0.6.0-rc.2 (docs-only) / v0.6.0-rc.1. Adds a
generic modpack import path (provider projects, not just local .mrpack
files), a version-aware interactive header with startup update checks, a new
elo version command, and a self-restart after updating from the interactive
interface so the new release is active immediately.

Merged in #20 by @3nderXP.

elo version

elo version
elo --version
elo -v

• Prints the installed Elo version, or unknown outside an installer-managed
  release.
• Documented in elo help version / elo version --help.

Generic modpack import

• elo instances import <name> <id-or-slug> [--provider <provider>] now
  accepts a Modrinth modpack project ID or slug, in addition to a local
  .mrpack file, through a new shared elo_cmd_import dispatcher
  (lib/mrpack.sh).
• Adding a new provider module (search/search_page/project_type/resolve/ get_dependencies/download) makes it work with import automatically; no
  changes needed in elo_cmd_import itself.
• instance.conf's MODPACK_SOURCE / MODPACK_SOURCE_VERSION now reflect the
  real origin (modrinth:<id> or local) instead of always local.
• The interactive "Import modpack" flow asks "Provider project" or "Local
  .mrpack file" up front, matching the existing "Install addon" flow.
• Installing a modpack into a non-empty instance now shows a proactive yellow
  warning in the UI, before the install-mode prompt (in addition to the
  existing backend warning).

Startup update check

• Opening the interactive interface (elo with no arguments) checks GitHub
  for a newer stable release, caching the result for 24 hours
  (elo_check_for_updates, update_notice.conf).
• The header shows an alert when a newer release is available:
  Update available: vX.Y.Z (System > Update Elo).

Version-aware header badge

• The header now renders the installed version in its own small
  rounded-border badge, top-left, above the main box — instead of a plain
  muted text line.
• Shows development when the version is unknown, or when it isn't a
  well-formed SemVer tag (e.g. a --source/--ref install tracking a branch
  like main), instead of incorrectly prefixing it with v (vmain).

--source installs record development

• Installing via ./install.sh --source <dir> now writes
  CURRENT_VERSION=development in install.conf (unless --ref is also
  given explicitly), since a local checkout isn't tied to a published release.
  Previously it inherited the literal default ref (main), which read as a
  real version.

Browse releases (interactive update)

• "Update Elo" in the System menu gains a "Browse releases" option, listing
  recent GitHub releases (tag, date, stable/pre-release) via
  elo_update_list_releases, alongside the existing "Latest stable release"
  and "Specific version" options.

Self-restart after update

• Updating from the interactive System menu now restarts Elo in place
  (exec) after a successful update, so the new release's code is active
  immediately without leaving and reopening the session.
• A cancelled or failed update never restarts the process.
• Direct CLI elo update behaves as before — it does not restart the
  invoking shell; the next command already runs the new release.

Instances menu cleanup

• Reordered to match the CLI contract and the existing help submenu order:
  Create, Import, Change version, Activate, Reset, List, Remove, Back.
• Renamed "Activate or switch instance" to "Activate instance" for
  consistency with the other concise labels.

Tests

• tests/test_elo.sh: new coverage for version/--version/-v and their
  help text.
• tests/test_interactive.sh: updated menu label; new coverage asserting
  the interactive update flow restarts on success and does not restart on
  cancellation.

---

What's Changed

• Feat: version command, dev-aware header badge, and self-restart after update by @3nderXP in #20

Full Changelog: v0.6.0-rc.2...v0.6.0-rc.3