docs+chore: Cargo.lock, German-only field docs, 0.2.0 changelog (Bundle D)

[Liohtml]

Overview

Bundle D — documentation & repo hygiene. Three small repo-health findings.

#	Fix
#19	Commit Cargo.lock. Removed /Cargo.lock from .gitignore and committed it, so cloners running cargo run --example scrape_one get a reproducible dependency tree and CI audits the exact resolved versions.
#26	German-only field docs. Place::postcode / Place::city now state explicitly they are populated only for German-format addresses (field docs + README struct comment).
#30	Changelog version. Moved the accumulated post-0.1.0 entries from [Unreleased] into a dated [0.2.0] section and bumped Cargo.toml to 0.2.0.

⚠️ Maintainer decisions / merge notes

• [repo-health] Low: CHANGELOG [Unreleased] contains all post-0.1.0 features — published version has empty changelog #30 is a release-versioning call. This declares 0.2.0 in the changelog and Cargo.toml; actually tagging/publishing is your action. Revert the bump if you'd rather keep accumulating under [Unreleased].
• CHANGELOG conflicts expected. Bundles A/B/C (PRs fix: search_many robustness — tab leak, panel-ready wait, dedup fast-path (Bundle A) #33/feat: configurable user-agent + proxy validation (Bundle B) #34/ci: add cargo-audit dependency scan (Bundle C) #35) also add [Unreleased] entries. Whichever order you merge, the CHANGELOG will need a trivial conflict resolution — fold those entries under [0.2.0] (or a fresh [Unreleased]). Merging this bundle last makes that easiest.
• Cargo.lock is now tracked; future dependency bumps will show up in the lockfile diff (intended).

Test plan

• cargo build / cargo test (6 passed)
• cargo fmt --all -- --check
• cargo clippy --all-targets -- -D warnings
• Cargo.lock regenerated at 0.2.0

Closes #19, #26, #30

https://claude.ai/code/session_01TPpTHPokxsZ3dQpRzg4NkD

---

Generated by Claude Code

[coderabbitai]

Warning

Review limit reached

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

More reviews will be available in 30 minutes and 47 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 90607839-15cf-4e8e-881c-17ad2788efee

📥 Commits

Reviewing files that changed from the base of the PR and between 3bdd0a1 and ebd4753.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (5)

• .gitignore
• CHANGELOG.md
• Cargo.toml
• README.md
• src/lib.rs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/bundle-d-docs-hygiene

---

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 and usage tips.}