docs: align README release rules with title-only bump

The Release Process section claimed a "BREAKING CHANGE" mention in the PR
body/title forces a major bump. The workflow now derives the bump from the
title's `!` marker only and ignores the body. Update the rules accordingly.

Author: mogita

README.md

@@ -352,16 +352,16 @@ Bug reports and pull requests are welcome on GitHub at https://github.com/getstr
 
 Releases use two paths, both handled by `.github/workflows/release.yml`:
 
-- **Default**: automatic release when a PR is merged to `main`/`master`. The PR title (and body) drives the semver bump.
+- **Default**: automatic release when a PR is merged to `main`/`master`. The PR title drives the semver bump.
 - **Fallback**: manual release via the `Release` workflow's `workflow_dispatch` (admin use). Select a `version_bump` (`patch`/`minor`/`major`). `use_current_version=true` skips the bump and publishes whatever is already in `lib/getstream_ruby/version.rb`.
 
 Automatic semver bump rules:
 
 - `feat:` -> minor
 - `fix:` (or `bug:`) -> patch
-- `feat!:`, `<type>(scope)!:`, or `BREAKING CHANGE` in the PR body/title -> major
+- `feat!:` or `<type>(scope)!:` (the `!` marker) -> major
 
-PRs with any other prefix do not trigger a release.
+PRs with any other prefix do not trigger a release. The bump is derived from the PR title only; the body is not scanned, so mentioning "BREAKING CHANGE" in prose does not force a major bump. Use the `!` marker to signal a breaking change.
 
 The release pipeline runs lint (`make format-check && make lint && make security`), the unit suite (`make test`), and all three integration suites (chat, feed, video) on the merged commit before publishing to RubyGems. Each step is idempotent; a failed run can be re-dispatched from the Actions UI.