docs: refresh release, roadmap, and contributor references for v0.4.1Docs/issue 38

[ananya-sajan07]

Closes #38

Changes made:

• README.md: Update Status from v0.4.0 to v0.4.1
• README.md: Make release examples version-neutral (v0.1.0 → vMAJOR.MINOR.PATCH)
• README.md: Remove completed 0.3.0 roadmap from contributing section
• README.md: Update contributing focus to August 2026 Community Dev Sprint (Pythonlings Community Dev Sprint — August 2026 tracker #52)
• docs-site/roadmap.md: Update version from v0.4.0 to v0.4.1

No changes needed for docs-site/contributing.md - it's already current.

Summary by CodeRabbit

• Documentation
  • Updated the README to reflect version 0.4.1.
  • Highlighted the August 2026 Community Dev Sprint.
  • Generalized the release-tag format example.
  • Updated the roadmap to reference version 0.4.1.

[coderabbitai]

📝 Walkthrough

Walkthrough

Public documentation now identifies version v0.4.1, points contributors to the August 2026 Community Dev Sprint, and uses a version-neutral release-tag example.

Changes

Documentation refresh

Layer / File(s)	Summary
Update release and contribution references Readme.md, docs-site/roadmap.md	The README and roadmap now reference v0.4.1. The README points contributors to the August 2026 Community Dev Sprint and uses vMAJOR.MINOR.PATCH for release tags.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Suggested reviewers: abhiksark

Poem

I’m a rabbit with a tidy pen,
Updating tags from now to then.
The roadmap shines, the sprint is bright,
Version four-one reads just right.
Hop, hop—docs are clear in sight!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description summarizes the changes but omits the required Tests, Screenshots, and Checklist sections.	Add the required sections and document test results, screenshot applicability, and checklist status.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the documentation refresh for release v0.4.1 and contributor references, despite minor spacing noise before "Docs/issue 38".
Linked Issues check	✅ Passed	The changes address the v0.4.1, version-neutral release, completed-roadmap, and current-sprint objectives in [#38].
Out of Scope Changes check	✅ Passed	The changes are limited to public README and roadmap updates and do not modify package metadata or historical release documentation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@Readme.md`:
- Around line 192-193: Align the contributor guidance referenced by the README’s
“August 2026 Community Dev Sprint” link with the current focus: update the root
CONTRIBUTING.md to reference that sprint or the active backlog instead of the
completed 0.3.0 roadmap, while preserving the existing contributor flow.

🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 69e82d71-ead4-454c-a34b-7353e292c844

📥 Commits

Reviewing files that changed from the base of the PR and between e3bdcc9 and 6d564c1.

📒 Files selected for processing (2)

• Readme.md
• docs-site/roadmap.md

📜 Review details

🔇 Additional comments (2)

Readme.md (1)

29-29: LGTM!

Also applies to: 212-212

docs-site/roadmap.md (1)

3-3: LGTM!

[coderabbitai]

📐 Maintainability & Code Quality | 🟠 Major | ⚡ Quick win

Update the linked contributor guide before merge.

The README now directs contributors to the August 2026 Community Dev Sprint, but the supplied CONTRIBUTING.md content still identifies the completed 0.3.0 roadmap as the current focus. This creates conflicting contributor instructions. Update the root CONTRIBUTING.md to reference the sprint or backlog, or change this README flow so it does not send contributors to stale guidance.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@Readme.md` around lines 192 - 193, Align the contributor guidance referenced
by the README’s “August 2026 Community Dev Sprint” link with the current focus:
update the root CONTRIBUTING.md to reference that sprint or the active backlog
instead of the completed 0.3.0 roadmap, while preserving the existing
contributor flow.