-- 0007_chat_adapter: tag every chat message with the adapter (platform + account)
-- that received it, e.g. "kook:3bef..." for a multi-account channels.json registration
-- or a bare platform name (e.g. "kook") when the account comes from env. It lets the
-- admin panel query the message send/receive log per independent adapter config, and
-- the full adapter overview (adapter_id != '').
--
-- IM adapter-originated messages carry this tag; Web main-session messages stay empty,
-- so only IM adapter sources are surfaced. The 0006 chat_messages table already exists
-- at this point, so ALTER ADD COLUMN is the correct, non-destructive step. The
-- canonical schema (including this column) is also re-issued idempotently by
-- internal/runtime/history.NewStore so a fresh in-memory store used by tests stays
-- self-contained; the migration is the authoritative path for an existing database.

ALTER TABLE chat_messages ADD COLUMN adapter_id TEXT NOT NULL DEFAULT '';
CREATE INDEX IF NOT EXISTS idx_chat_msgs_adapter_created ON chat_messages (adapter_id, created_at DESC);