Release automation won't kick off if a release PR is mistitled

It is common for developers to create a release PR but then fail to name the PR "Release X.Y.Z". Unfortunately they don't know that this won't work until it's too late.

We should document the expectations for release PR titles. We should also possibly figure out a way to detect when the root package has been bumped and advise the developer accordingly, perhaps by automatically posting a comment on the PR.

Start by reviewing the release automation and release PR workflow to confirm where the title requirement is enforced. Document the expected “Release X.Y.Z” title and explain when it matters; treat automatic detection and comments as a separate scope unless an existing project hook is identified. Done means developers can find and follow the release PR naming guidance.

Written by the indexing model from the issue text.