chore(main): release 0.6.0

[github-actions]

🤖 I have created a release beep boop

0.6.0 (2026-07-10)

Features

• icaptcha-client: solve the iCaptcha proof-of-work on answer (#181) (c98b503)

---

This PR was generated with Release Please. See documentation.

[beardthelion]

Approving as code owner. Clean release-please output: routine 0.5.1 to 0.6.0 bump across the workspace plus the changelog entry.

What I checked: all five crate versions, the manifest, and the changelog move together to 0.6.0; the changelog is complete (the only release-worthy commit since v0.5.1 is the icaptcha proof-of-work feature #181, correctly a minor bump, while #168 is a test and correctly omitted); nothing rode along, the diff is version strings and the changelog only.

One non-blocking follow-up, not for this PR: release-please isn't bumping Cargo.lock, so the lock now trails the manifest (0.5.0 vs 0.6.0). Nothing builds with --locked today (CI and the release image build unlocked, and main is green) so it's harmless, but it compounds every release. The cause is in release-please-config.json: release-type is 'simple' and its extra-files cover the five Cargo.toml but not the lock. Candidate directions, not yet verified against our config: the rust release-type, or a post-generation step that updates and commits the lock. That is separate from cutting this release.