Release ForgeFlow 0.5.2

README.md

@@ -1,5 +1,18 @@
 # ForgeFlow
 
+## Publish this release to the built-in updater repository
+
+Extract the full source ZIP to a folder under Downloads and run:
+
+```powershell
+Set-ExecutionPolicy -Scope Process Bypass
+.\Publish-ForgeFlow-Release.ps1
+```
+
+The script runs the complete quality gate, clones `git@gitea.itworx.tech:Jens/ForgeFlow.git` into a temporary folder, mirrors the verified source without `.git`, `node_modules` or release ZIPs, commits it on `main` and pushes it. A running older ForgeFlow source installation can then update through **Settings → Updates**.
+
+
+
 ForgeFlow is a desktop release cockpit that turns the complete path from a local
 code change to a verified server deployment into one guided flow:
 
@@ -13,9 +26,16 @@ credentials on the user's own computer.
 
 ![ForgeFlow overview](docs/screenshots/overview.png)
 
-## Current status: v0.4.2 integrated desktop test release
+## Current status: v0.5.2 Windows publication reliability release
 
-### v0.4.2 workflow and deployment expansion
+### v0.5.2 publication reliability and v0.5.0 workflow hardening
+
+- viewport-safe deployment and server dialogs with persistent action buttons;
+- NUL-delimited Git pathspec transport for thousands of selected files;
+- per-repository Git mutation queues and explicit stale-lock repair;
+- one-click normalization of legacy Gitea remotes;
+- corrected password capture before the loading overlay re-renders the server form;
+- a verified publishing script for testing the built-in updater.
 
 - large changed-file sets scroll independently;
 - commit actions explain the missing prerequisite and auto-stage selected files;