Add useful repo status badges to the README

[dbachko]

Context

The README header did not surface core repo signals, so visitors had to scan deeper to find CI, version, license, and docs entry points.

TL;DR

Add four high-signal badges under the README logo for CI, license, latest tag, and docs.

Summary

• Add a CI badge linked to the existing make-all workflow
• Add license and latest tag badges linked to GitHub metadata pages
• Add a docs badge linked to the workflow reference entry point

Alternatives

• Considered stars, forks, contributor, and activity badges, but skipped them as low-signal vanity metrics for the current repo size.

Test Plan

• cargo fmt --check
• cargo test
• cargo clippy --all-targets --all-features -- -D warnings
• git diff --check -- README.md
• Inspect the README badge row and badge targets in the staged diff

Summary by CodeRabbit

• Documentation
  • Added status and metadata badges to the README, providing quick links to CI workflows, license information, release history, and documentation resources.

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 671fccdb-08a1-4e7c-a4a9-84a6fa3103f9

📥 Commits

Reviewing files that changed from the base of the PR and between 8e86e8f and 619a60c.

📒 Files selected for processing (1)

• README.md

---

📝 Walkthrough

Walkthrough

Four status badges have been added to the top of README.md, providing visual links to the CI workflow, license, release tags, and documentation. These badges serve as quick reference points for project status and resources without modifying any existing README content or functionality.

Changes

Cohort / File(s)	Summary
Documentation Badges README.md	Added four metadata badges (CI, License, Release, Docs) linking to workflow, license file, GitHub tags, and documentation reference.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 Hoppity-hop, badges so bright,
CI, License, Release in sight!
Docs gleaming with helpful cheer,
The README shines crystal clear! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: adding status badges to the README, which matches the changeset perfectly.
Description check	✅ Passed	The description follows the template structure with all required sections (Context, TL;DR, Summary, Alternatives, Test Plan) completed with relevant details.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/readme-badges

---

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