test: feat branch → master (ruleset guardrail test)

[belleklaviyo]

This is a test PR to validate the master-merge-strategy ruleset.

Verifies that squash merge and rebase merge are disabled when merging into master. Only "Create a merge commit" should be available.

3 trivial README changes. Close/delete this PR and branches after verification.

[cursor]

Cursor Bugbot has reviewed your changes using default mode and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 2813abd. Configure here.}

[github-actions]

⚠️ This PR needs to target a release branch before it can merge to master.

All changes — including hotfixes, dependency bumps, and feature work — should flow through a rel/* branch rather than merging directly to master. This keeps commit history clean and ensures every change is tied to a release.

To fix: change the base branch of this PR to the appropriate rel/* branch when available. You can do this without closing the PR — use the base branch dropdown at the top of the PR.

• If this is CI/tooling work, rename your branch with a ci/ prefix and this check will pass
• If this is documentation-only work, rename your branch with a docs/ prefix and this check will pass

Override: In exceptional circumstances, a maintainer may add the manual-merge label to bypass this check and merge directly to master. This should be used sparingly — it skips the release branch entirely and may result in changes not being included in a release or loss of commit attribution if not handled carefully.

Enforced by the pr-target-check workflow.