ALTER TABLE ADD CONSTRAINT validates existing rows immediately, so the
UPDATE must run first to migrate 'standard' → 'bronze' before the new
constraint is applied.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
The guests table had CHECK (loyalty_tier IN ('standard','silver','gold','platinum'))
but the UI expects 'bronze' not 'standard'. Drop the old constraint, migrate
'standard' rows to 'bronze', then add the correct constraint.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- LoyaltyPage: levelBadge() now falls back to bronze for unknown tiers
(DB had loyalty_tier='standard' from old seed data)
- migration 040: deduplicate general chat rooms + add unique index,
normalize loyalty_tier to bronze for non-standard values
- chat.ts: ON CONFLICT clause now targets the new partial unique index
- Sidebar: DEFAULT_GROUPS only opens 'basics' by default; bump
localStorage key to sidebarGroups_v2 to clear stale stored state
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
