0.6.0

Added

• Per-user profile preferences (last_sport_type, last_equipment_by_sport): file driver users/<nickname>/profile.yaml, bbolt bucket user_profiles; GET /api/v1/profile
• Creating a workout without equipment_ids uses equipment from the user's profile for that sport_type (explicit [] still means none)
• Workout likes with counts and liker lists in the list/detail UI; local + federated Like/Undo, file likes.yaml, bbolt likes buckets, and GET/POST/DELETE /api/v1/workouts/{id}/likes
• Workout comments (add/list/delete) on own and others' workouts; file comments.yaml, bbolt comment buckets, GET/POST/DELETE /api/v1/workouts/{id}/comments, federated Create/Delete Note with inReplyTo, and comments snapshot on Workout Update; UI comment control next to likes

Changed

• Breaking: last_equipment_by_sport removed from user identity responses (/auth/me, login, register); clients should use GET /api/v1/profile
• New workout form defaults sport and equipment from GET /api/v1/profile (no extra own-workouts list for last sport)
• last_sport_type is the sport of the chronologically newest workout (start_date, then id); refreshed asynchronously after create/update/delete, and once at the end of a Strava import job
• File-driver outbound Like activity ids are stored as YAML (object_id + activity_id); plain-text activity-id-only files are still read and migrate via inbox reconstruction

Fixed

• Android/iOS: tighter workout like/comment bar spacing (no bottom pad; IconButton vertical pad 8 with shrinkWrap)
• Federated workout comment/like avatars: recompute is_local from handle domain (ignore origin flag), store/export public avatar URLs, lazy-cache remote author avatars when listing, and warm avatar cache from workout comment/like snapshots
• grom migrate-storage now copies workout likes (local, federated cache, and outbound Like activity ids) between file and bbolt
• grom migrate-storage copies workout comments (local, federated cache, and outbound Create Note activity ids) between file and bbolt