Release ForgeFlow 0.5.2

docs/RELEASE_NOTES_0.5.0.md

@@ -0,0 +1,14 @@
+# ForgeFlow 0.5.0
+
+## Reliability and viewport release
+
+- All dialogs are constrained to the visible desktop viewport. Long deployment configuration and preflight content scrolls independently while the action footer remains available.
+- Large partial selections use Git's NUL-delimited `--pathspec-from-file` interface instead of thousands of command-line arguments. This removes Windows `ENAMETOOLONG` failures.
+- Mutating Git operations are serialized per repository, preventing ForgeFlow background actions from competing for `.git/index.lock`.
+- Added explicit stale index-lock inspection and repair APIs.
+- Added one-click normalization of every linked repository origin to the current Gitea SSH URL, replacing legacy aliases and renamed owners without changing files or commits.
+- Source updater remains exact-commit pinned and runs the full quality gate before restart.
+
+## Upgrade test
+
+Push the extracted source to `Jens/ForgeFlow` with package version `0.5.0`. A running 0.4.5 source installation can then use Settings → Updates → Check now → Download update → Apply & restart.

docs/RELEASE_NOTES_0.5.1.md

@@ -0,0 +1,16 @@
+# ForgeFlow 0.5.1
+
+## Windows publication reliability
+
+- Validates the server deployment shell script through Bash standard input instead of passing a Windows working directory to Bash.
+- Removes the Git Bash versus WSL path ambiguity that caused a blank-error quality-gate failure from Downloads.
+- Adds regression coverage proving shell validation no longer depends on a Windows path or a path containing spaces.
+- Retains all v0.5.0 viewport, Git batching, remote normalization, repository serialization and password-form fixes.
+
+Publish the extracted source to `Jens/ForgeFlow` with package version `0.5.1`. A running older source installation can then discover and apply it through the built-in updater.
+
+## Carried forward from 0.5.0
+
+- Responsive viewport handling keeps long modals and their actions reachable.
+- Large Git selections continue to use `--pathspec-from-file` with NUL separation.
+- Mutating Git work remains serialized per repository.

docs/RELEASE_NOTES_0.5.2.md

@@ -0,0 +1,11 @@
+# ForgeFlow 0.5.2
+
+## Windows publication and update reliability
+
+- Removes the external Bash executable as a Windows publication/update prerequisite.
+- Always performs deterministic structural validation of the Linux/Unraid deployment script.
+- Runs GNU Bash `-n` syntax validation on non-Windows hosts and Linux CI.
+- Prevents Git Bash, WSL launcher, or another `bash.exe` shim from blocking a valid Windows release.
+- Keeps all ForgeFlow 0.5.0 and 0.5.1 viewport, Git batching, remote normalization, serialized per repository, lock handling, SSH form, and updater improvements.
+
+The release retains the viewport fixes, Git `--pathspec-from-file` batching, and Git mutations serialized per repository from 0.5.0/0.5.1.

docs/UPDATING.md

@@ -53,3 +53,8 @@ The updater deliberately checks the semantic version stored in the remote
 `package.json`. Merely pushing a new commit without increasing that version does
 not present an update. Publish the complete validated ForgeFlow source to the
 configured repository and bump the version for every release.
+
+
+## Publishing v0.5.1 from a Downloads folder
+
+Extract the complete release and run `Publish-ForgeFlow-Release.ps1`. The script validates the source, clones `Jens/ForgeFlow` into a temporary directory, mirrors the verified source, commits it and pushes `main`. Keep the currently running older ForgeFlow source folder untouched; use its **Settings → Updates** screen to test the exact-commit download, validation, rollback and restart path.