v0.8.3 — Plugin engine compat fix (Docker image was reporting wrong version)

Patch — fixes plugin engine compat in the Docker image

This release fixes a release-process bug that has been silently breaking plugin installs on every Docker deployment since 0.8.0.

The bundled Docker image swaps packages/backend/package.json for a static runtime manifest (package.prod.json) at build time — and that manifest still carried "version": "0.7.2" from three releases ago. getOscarrVersion() (used by plugin compat checks) read from that file, so every plugin requiring Oscarr >=0.8.x was silently refused at install time on Docker — including Quotas which requires >=0.8.2. The in-app version banner correctly showed 0.8.2 because it reads from a different file, masking the bug.

Fixes

• Compat reads the root package.json (the only file shipped fresh on every release, already used by other version readers). The version field is dropped from package.prod.json — no more double-bump to forget.
• Discover catalog surfaces engine compatibility — GET /plugins/registry now returns compat per entry, the Install button on incompatible plugins is disabled and the label switches to Requires Oscarr <range>. No more downloads triggered for plugins that can't load.
• Reload button force-refreshes the Discover catalog — previously only the update-check cache was bypassed. A newly-registered plugin (e.g. Quotas which just landed in the registry) wouldn't surface until the 30 min cache expired. GET /plugins/registry now accepts ?force=true and the Reload button uses it.

🐳 Image: ghcr.io/arediss/oscarr:0.8.3