v0.115.0

Release-flow fixes (the empty-candidate-window guard now pushes and dispatches run_all itself on stranded resumes; dev-node editable-sibling locks refresh at bump time), the changelog-edit field-wipe fix, and dev install's required --target choice.

Breaking

• Breaking: rlsbl dev install no longer takes --global/--venv. The install mode is now one required choice, --target global or --target venv, with no default -- an invocation that omits it is a parse-time error instead of silently installing globally.

Fixes

• rlsbl changelog edit --no-user-facing no longer erases the entry's stored description and type -- flipping an entry to non-user-facing now only flips the flag, and flipping it back restores the original text.
• Fix. A monorepo release resuming stranded members after a red CI check no longer deadlocks when the fix-forward commit touches none of the members' paths. rlsbl pushes the candidate and dispatches ci-router.yml with run_all=true itself, correlates the dispatched run to the pushed commit, and gates on it. A fresh release whose version-bump commit matches no filter is still refused.
• Fix. A monorepo release now refreshes the uv.lock of every non-releasable workspace project that records a bumped sibling as an editable path source, and commits it with the version bump. Such a project's lock-pin test used to go red at the CI gate on an already-pushed candidate, and the dev-node-only fix-forward that healed it left every releasable's CI job skipped on the resumed candidate.