Always cut a new release immediately after merging a fix or upgrade PR

After merging a PR into master (whether a bug fix or dependency upgrade), the user consistently decides to cut a new release right away. This applies to both hotfix scenarios (e.g., Node version pin to fix a regression) and feature/upgrade scenarios (e.g., Node 24 upgrade). The user does not wait for additional changes to batch into a release — each significant merge is followed immediately by a release cut. When assisting, proactively prepare for or suggest the release step as the natural next action after a successful merge. This was confirmed after merging PR #843.