Two related follow-ups for the 3 000+ groups-per-account scale path:
1. New B-tree index on whatsapp_groups (account_id, name) (migration
0014). Covers the groups list page's
`WHERE account_id=? ORDER BY name ASC LIMIT 200` query so PG
streams pre-sorted from the index instead of pulling all rows
then sorting. The unique (account_id, wa_group_jid) was the only
prior B-tree on this table; it backed the WHERE prefix but not
the ORDER BY.
2. listGroupsForAccount now filters `is_archived = false` in both
the search and the no-search branch. Soft-archived groups
(set when group-sync sees them disappear from the live
participant list, or when an operator unpairs the account) used
to leak into the wizard picker, letting operators pick a group
the bot can no longer reach. Archived rows still exist in DB so
reminders that target them keep working; a re-pair flips them
back via the on-conflict upsert.
README "Deferred" entry for the composite index removed (it's
shipped). Search-as-you-type in the wizard picker stays deferred.
482 web + 88 bot tests still green; typecheck clean.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
