Sync staging after v2.2.1 release

[SpicyMarinara]

Why

Synchronize the release merge back into staging so the long-lived branches share the v2.2.1 release history and the prior main-only README typo fix. This also refreshes the GHCR staging tag from the released tree.

Changes

• merge the v2.2.1 main release commit into staging
• carry the existing README wording correction into active development

Validation

• Confirm main and staging trees match after merge
• Confirm the staging container workflow succeeds

All validation boxes are intentionally left unchecked for human verification.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: a38c8c77-71f4-4c5b-a3d6-e7faa651170b

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch main

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}