v0.7.0 — Artist-first add flow

New

• The Add screen now leads with artist search. Type an artist name and browse their catalog to add a release. The camera, barcode scanner, and file upload are still there — tucked behind a toggle rather than competing for space on the main screen.
• Artist name type-ahead is live: start typing and matching artists appear as a dropdown. (If nothing comes back, the catalog may not have that artist yet — see below.)
• Barcode scanning now resolves directly against the catalog.
• Camera capture feeds into catalog classification.
• Owned releases are marked in search results, release-type filtering is available, and keyboard navigation works through the artist/album picker.

Fixed

• Artist type-ahead was returning “not in catalog” for a range of common queries instead of showing results. Fixed.
• A price parsing error was misreading thousands separators — a record valued at $1,250 was being stored as $1.25. Fixed.
• Async route handlers that threw an unhandled error were leaving the request hanging indefinitely rather than returning a 500. Fixed.
• A new deployment can now fail its health check if the database is missing a migration the code depends on, rather than starting up silently in a broken state.

Improved

• Validation is now wired through the account, profile, catalog, and session layers, with two previously known schema mismatches corrected.
• The web API now has a published OpenAPI 3.1 spec generated from the app’s own schemas; CI will fail if the spec drifts from the code.
• Write operations that are safe to retry now use an idempotency key to prevent duplicate entries on retry.
• Delta sync is in place: the API tracks updated_at on records and maintains deletion tombstones, so a future second client can sync incrementally rather than pulling everything.
• Search queries and thumbs-up/thumbs-down signals from the artist search surface are now captured to feed back into catalog quality over time.