chore(release): v0.3.0 — changelog, version bump, README updates

[Liohtml]

Release preparation for v0.3.0:

• CHANGELOG.md – Unreleased folded into a new 0.3.0 section (dated 2026-07-02) covering everything since v0.2.1: the four security/maintenance batches (fix: high-priority security issues from repo-health audit (#112, #95, #117, #62, #98) #122, fix: harden web API and DICOM parsing (#120, #100, #110, #63, #111) #123, chore: supply-chain & deployment hygiene (#113, #91, #67, #65, #60, #72, #90) #124, test: add e2e pipeline integration tests; raise coverage floor to 80% (#93, #35, #97, #66) #125), the earlier hardening PRs (fix: harden serve/web/CLI/i18n from repo-health findings (#105, #96, #102, #99, #106) #108, fix: prevent PHI leakage via .gitignore and add HTTP security headers (#114, #109) #116, fix: resource-exhaustion & concurrency guards (#115, #94, #74) #121) and the five Dependabot GitHub-Actions bumps (build(deps): Bump docker/build-push-action from 6 to 7 #79–build(deps): Bump actions/upload-artifact from 4 to 7 #83).
• Version bump – 0.2.1 → 0.3.0 in pyproject.toml, src/medcheck/__init__.py and uv.lock.
• README.md – documents the new --deidentify flag, MEDCHECK_RATE_LIMIT, the PHI-in-reports note and the no-silent-fallback LLM routing guarantee.

After merge, tagging v0.3.0 triggers the release workflow (PyPI via Trusted Publishing + GHCR lite/full images).

🤖 Generated with Claude Code

https://claude.ai/code/session_014ywk8AWq5mgbeERmvuhcJy

---

Generated by Claude Code

[coderabbitai]

Warning

Review limit reached

@Liohtml, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 44 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 5cb6312d-2616-4a3e-a2a0-2345250673cc

📥 Commits

Reviewing files that changed from the base of the PR and between d7f9fe0 and 2b40f94.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (4)

• CHANGELOG.md
• README.md
• pyproject.toml
• src/medcheck/__init__.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/dependabot-maintenance-u1mdmh

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!