v1.2.0

What's Changed

🚀 Features

• Support multiple bikes per account — each Cowboy account now maps to its own config entry. Run the "Add Integration" flow once per account (Cowboy allows one bike per account). Closes #120.
• Firmware update entity — a dedicated Update entity with installed vs. latest version and release notes. The old binary_sensor.update_available is now disabled by default (still available for existing automations).
• Diagnostics with PII redaction — download a redacted JSON dump from the integration page, safe to paste into bug reports. Closes #99.
• Options flow: polling interval — configure bike-coordinator polling between 1 and 60 minutes.
• Trips data — new sensors: Last trip distance / ended / duration / CO₂ / calories / title, plus Distance today.
• More bike sensors — Last seen, Last ride mode (enum with per-state icons), Last crash, Warranty ends, Auto-lock, Speed limit.

🐛 Fixes

• Firmware update logic no longer renders unknown when the API returns "firmware": null.
• Entry unload now actually invalidates the Cowboy session (was silently failing).
• Device-tracker entities no longer collide when multiple bikes share a title.
• Token renewal no longer relies on uid happening to equal the email.
• Device-tracker unique ID is entry-scoped, not title-based.

🧰 Maintenance

• Dropped dead get_bike_status (endpoint 404s).
• PARALLEL_UPDATES = 1 on polling platforms.
• CI: removed the broken claude-code-review workflow that was blocking renovate auto-merges.
• README note on using multiple Cowboy accounts for multi-bike households.

⚠️ Migration

Existing entries are migrated automatically from v1 to v2 on first load — no action needed. Device registry and entity unique IDs are preserved across the upgrade. If you were relying on binary_sensor.*_update_available in an automation, consider switching to the new Update entity.