Synchronize packaging docs for v1.4.0-beta.1

Author: masarray

docs/RELEASE_PACKAGING.md

@@ -39,16 +39,18 @@ git add -f docs/QUICK_START.pdf docs/USER_MANUAL.pdf
 ## Local packaging
 
 ```powershell
-.\scripts\repository-health.ps1 -ExpectedVersion "1.3.0-beta.2"
-.\scripts\publish-windows-portable.ps1 -Version "1.3.0-beta.2"
-.\scripts\verify-release-package.ps1 -PackageZip ".\artifacts\release\ProcessBusInsight-v1.3.0-beta.2-win-x64-portable.zip"
+.\scripts\repository-health.ps1 -ExpectedVersion "1.4.0-beta.1"
+.\scripts\publish-windows-portable.ps1 -Version "1.4.0-beta.1"
+.\scripts\verify-release-package.ps1 -PackageZip ".\artifacts\release\ProcessBusInsight-v1.4.0-beta.1-win-x64-portable.zip"
 ```
 
-## GitHub workflow
+## GitHub workflows
+
+The candidate workflow runs for `stabilization/*` and `architecture/*` pull requests. It restores, builds, tests, packages, verifies the ZIP, creates a candidate manifest, and uploads the candidate without publishing a public release.
 
 The release workflow runs manually or for tags matching `v*`. It restores, builds, tests, packages, verifies the ZIP, produces a checksum and release manifest, uploads workflow evidence, and optionally creates or updates a GitHub Release.
 
-Manual inputs:
+Manual release inputs:
 
 - `version` — semantic version label
 - `publish_release` — create/update the GitHub Release
@@ -58,4 +60,4 @@ Manual inputs:
 
 ## Packaging design notes
 
-The publish script performs a runtime-specific restore and then publishes with `--no-restore`. It splits prerelease versions into numeric assembly/file version and informational/package version so a label such as `1.3.0-beta.2` remains valid while Windows assembly versions stay numeric.
+The publish script performs a runtime-specific restore and then publishes with `--no-restore`. It splits prerelease versions into numeric assembly/file version and informational/package version so a label such as `1.4.0-beta.1` remains valid while Windows assembly versions stay numeric.