chore(release): prepare v0.2.0

[phil-accelbyte]

Summary

Bumps version 0.1.0 → 0.2.0 ahead of release.

Breaking changes in v0.2.0

Under semver 0.x convention, breaking CLI changes bump the minor.

1. auth login short-circuits when already authenticated (#9)

Pre-0.2.0, running ags auth login against a session with a valid access token would re-run the full grant — opening the browser for authorization-code or re-exchanging for client-credentials. Post-0.2.0 it short-circuits with ✔ Authenticated ({"status": "already_authenticated"} in JSON mode) and exits 0 without contacting the server. Scripts that called auth login as a "force-refresh" gesture will no longer trigger a re-login. To force a fresh grant, run ags auth logout first.

2. Two CLI commands renamed (#10)

• ags lobby blocks symc → ags lobby blocks sync (was a typo in the x-operationId)
• ags social stat-cycles export --api-scope public → ags social stat-cycles get --api-scope public (was misclassified; the admin variant is unchanged)

Additive in v0.2.0

• New ags basic profiles update-my-zip-code command — previously silently dropped at parse time because of the malformed x-operationId fixed in fix(catalogue): assert x-operationId shape and correct malformed ids #10.
• Documented JSON status values for auth login --format json: logged_in, already_authenticated, refreshed. These shapes are now contractual rather than incidental.
• Real token_expires_in / refresh_expires_in values in auth status --format json — the prior 0-sentinel could be misread as "expired" and is gone.

Side effect: free spec-cache invalidation

Cargo.toml version is checked in src/catalogue/cache.rs:59 to validate the on-disk parsed-spec cache. Bumping the version invalidates every existing user cache on first run post-upgrade, forcing a rebuild from the (now corrected) bundled specs. No need to ship a separate ags refresh-specs instruction.

Test plan

• cargo test --lib — 494 passed
• cargo run -- --version reports ags 0.2.0
• CI green on all platforms