ForgeFlow 0.10.16

Signed releases from the public source repository

Packaged updates follow the exact published release commit, so later documentation or source-only changes do not invalidate the signed executable.
New installations check Jens/ForgeFlow-Public for Windows updates.
Existing installations that still use the legacy Jens/ForgeFlow endpoint move to ForgeFlow-Public after installing this bridge release. An intentionally configured alternative update repository is preserved.
A version change in the curated public source now starts the Windows quality, build, signing and release workflow. Source-only updates do not create another binary release.
The publisher refuses to replace an already published version or attach assets built from a different commit. Release manifests continue to bind the executable checksums to the exact public source commit and the existing Ed25519 publisher key.

The legacy repository remains available for older installations until the bridge update has been verified in the field.