feat: implement Gitea update checks and installer management

README.md

@@ -39,6 +39,21 @@ On first launch, Scoreko copies the packaged NodeCG runtime to the user's app da
 - `npm run dist:win`: create the Windows installer.
 - `npm run doctor`: check the prepared runtime and the configured port.
 
+## Updates from Gitea
+
+Scoreko can check a Gitea release feed without forcing the user to update. Edit `static/updates.json` before building:
+
+```json
+{
+  "enabled": true,
+  "apiUrl": "http://gitea.local/api/v1/repos/OWNER/REPO/releases/latest",
+  "releasePageUrl": "http://gitea.local/OWNER/REPO/releases",
+  "assetPattern": "Scoreko-setup-.*\\.exe$"
+}
+```
+
+For each release, bump `package.json` version, build with `npm run dist:win`, create a Gitea release tagged like `v0.2.0`, and attach `release/Scoreko-setup-0.2.0.exe`. When Scoreko sees a newer tag, it asks whether to download and install it.
+
 ## Configuration
 
 The defaults match the parent bundle:
@@ -47,5 +62,7 @@ The defaults match the parent bundle:
 - `NODECG_PORT=9090`
 - `SCOREKO_DASHBOARD_ROUTE=dashboard/scoreko-dev/main.html?standalone=true`
 - `SCOREKO_LOADING_ROUTE=dashboard/loading/main.html?standalone=true`
+- `SCOREKO_UPDATES_ENABLED=true`
+- `SCOREKO_UPDATE_ASSET_PATTERN=Scoreko-setup-.*\.exe$`
 
 Copy `.env.example` only if you need local overrides while developing.