Add runner ci (test)

README.md

@@ -97,6 +97,30 @@ The manifest format is:
 
 `feedUrl` must point to a directory that contains the Electron Builder update descriptors for Windows, macOS, and Linux.
 
+### Automated Gitea release queue
+
+The Gitea workflows in `.gitea/workflows/release-draft.yml` and `.gitea/workflows/publish-draft-release.yml` keep the existing desktop auto-update flow intact.
+
+On every push to `main` or `master`, the release workflow:
+
+1. Computes a semver release version from the current `package.json` major/minor version and the workflow run number.
+2. Builds the Linux and Windows Electron packages.
+3. Builds standalone server executables for Linux and Windows.
+4. Downloads the latest published `release-manifest.json`, merges the new release feed URL, and uploads the updated manifest to the draft release.
+5. Uploads the desktop installers, update descriptors, server executables, and `release-manifest.json` to the matching Gitea release page.
+
+The draft release uses the standard Gitea download path as its `feedUrl`:
+
+	 `https://YOUR_GITEA_HOST/OWNER/REPO/releases/download/vX.Y.Z`
+
+That means the current desktop auto-updater keeps working without any client-side changes once the draft release is approved and published.
+
+To enable the workflow:
+
+- Add a repository secret named `GITEA_RELEASE_TOKEN` with permission to create releases and upload release assets.
+- Make sure your Gitea runner labels match the workflow `runs-on` values (`linux` and `windows`).
+- After the draft release is reviewed, publish it either from the Gitea release page or by running the `Publish Draft Release` workflow with the queued release tag.
+
 ## Main commands
 
 - `npm run dev` starts Angular, the server, and Electron