-- Platform-agnostic inbound channel queries (MUL-3515). These operate on -- the channel_* tables created in migration 124. Each installation carries -- a `channel_type` discriminator and a JSONB `config` blob for -- platform-specific identifiers/credentials; the cross-platform columns -- stay flat. The Go layer owns building/parsing config — these queries -- treat it as opaque JSON except for the routing index on config->>'app_id'. -- -- No foreign keys exist on these tables (MUL-3515 §4): the integrity the -- old composite FKs enforced (binding workspace matches installation; -- binding dies with membership / chat_session) is maintained in the -- application layer via the membership check in the inbound identity step -- and the *DeleteChannel*BindingsBy* cleanup queries below. -- ===================== -- channel_installation -- ===================== -- name: UpsertChannelInstallation :one -- Install / re-install path. `config` is the opaque per-channel JSONB the -- Go layer assembles (for feishu: app_id, app_secret_encrypted, tenant_key, -- bot_open_id, bot_union_id, region). Re-installing the same agent on the -- same channel_type replaces the whole config and forces status back to -- 'active'. The conflict key is (workspace_id, agent_id, channel_type) so an -- agent may hold one installation per channel_type (feishu + slack + ...) -- without one install clobbering another. The WS lease is intentionally NOT -- reset here — the inbound hub owns lease lifecycle. INSERT INTO channel_installation ( workspace_id, agent_id, channel_type, config, installer_user_id ) VALUES ( $1, $2, $3, $4, $5 ) ON CONFLICT (workspace_id, agent_id, channel_type) DO UPDATE SET channel_type = EXCLUDED.channel_type, config = EXCLUDED.config, installer_user_id = EXCLUDED.installer_user_id, status = 'active', installed_at = now(), updated_at = now() RETURNING *; -- name: UpsertChannelInstallationByAppID :one -- Team-keyed install / re-install for channels whose natural identity is the -- platform workspace, not the (agent) pairing. Slack: one Slack workspace -- (team_id, stored as config->>'app_id') maps to exactly one installation, so -- re-connecting it — even to represent a DIFFERENT agent in the SAME Multica -- workspace — UPDATES the existing row (moving agent_id) instead of colliding -- with the (channel_type, app_id) unique index. Contrast UpsertChannelInstallation, -- whose conflict key is (workspace_id, agent_id, channel_type): right for Feishu -- (one app per agent), wrong for Slack. -- -- The `WHERE channel_installation.workspace_id = EXCLUDED.workspace_id` fences -- the conflict update to the SAME Multica workspace: a team already owned by a -- DIFFERENT workspace updates no row and RETURNING is empty (pgx.ErrNoRows), -- which the caller maps to ErrTeamOwnedByAnotherWorkspace. This is the ATOMIC -- cross-workspace guard — a plain SELECT before the upsert cannot stop two -- workspaces racing to OAuth the same team (both read no rows, then one inserts -- and the other's conflict-update would silently steal it). A re-connect that -- would move the team to an agent already holding a different Slack install in -- the same workspace still trips the (workspace_id, agent_id, channel_type) -- unique constraint — a genuine conflict the OAuth callback turns into a redirect. INSERT INTO channel_installation ( workspace_id, agent_id, channel_type, config, installer_user_id ) VALUES ( $1, $2, $3, $4, $5 ) ON CONFLICT (channel_type, (config ->> 'app_id')) DO UPDATE SET agent_id = EXCLUDED.agent_id, config = EXCLUDED.config, installer_user_id = EXCLUDED.installer_user_id, status = 'active', installed_at = now(), updated_at = now() WHERE channel_installation.workspace_id = EXCLUDED.workspace_id RETURNING *; -- name: GetChannelInstallation :one -- Scoped by channel_type: a per-channel caller (e.g. the Feishu store) -- must never resolve another channel's installation by guessing its UUID. SELECT * FROM channel_installation WHERE id = sqlc.arg('id') AND channel_type = sqlc.arg('channel_type'); -- name: GetChannelInstallationInWorkspace :one SELECT * FROM channel_installation WHERE id = sqlc.arg('id') AND workspace_id = sqlc.arg('workspace_id') AND channel_type = sqlc.arg('channel_type'); -- name: GetChannelInstallationByAppID :one -- Inbound routing. The platform event carries only the channel's app -- identifier (Feishu app_id); the dispatcher's installation resolver routes -- on (channel_type, config->>'app_id'). Backed by the functional unique -- index idx_channel_installation_type_appid. -- -- Both params are named + explicitly typed: `config ->> 'app_id'` makes sqlc -- attribute a bare `$2` to the JSONB `config` column (it would emit -- `Config []byte`), so we pin the app_id arg to ::text to get AppID string. SELECT * FROM channel_installation WHERE channel_type = sqlc.arg('channel_type') AND config ->> 'app_id' = sqlc.arg('app_id')::text; -- name: GetChannelInstallationOwnerByAppID :one -- Identifies the LIVE owner of a (channel_type, config->>'app_id') routing slot -- so the install path can refuse a rebind with an ACCURATE message instead of the -- old catch-all "connected to a different Multica workspace". Meant to be read -- only after ReclaimDeadChannelInstallationByAppID has removed every DEAD owner, -- so a returned row is a live active owner. `agent_archived` distinguishes an -- archived (reversible) owner — its bot stays owned, recovered by unarchiving the -- agent or disconnecting the bot — from a plain active one. The JOIN drops a row -- whose agent no longer exists (an orphan the reclaim gate should already have -- cleared), so a missing row (pgx.ErrNoRows) means "no live owner". The caller -- reads agent_archived_at.Valid to tell an archived (reversible) owner apart. SELECT ci.workspace_id, ci.agent_id, a.archived_at AS agent_archived_at FROM channel_installation ci JOIN agent a ON a.id = ci.agent_id WHERE ci.channel_type = sqlc.arg('channel_type') AND ci.config ->> 'app_id' = sqlc.arg('app_id')::text; -- name: ReclaimDeadChannelInstallationByAppID :one -- Rebind cleanup gate. Frees the (channel_type, config->>'app_id') routing slot -- so a valid new agent can (re)bind a bot whose previous owner is DEAD, and, in -- the same statement, clears every application-owned dependent row of the removed -- installation (channel_* has no FK/cascade, MUL-3515 §4). Returns the removed id -- (pgx.ErrNoRows when nothing was dead — a no-op the caller treats as success). -- -- "Dead" is exactly one of: -- 1. a REVOKED placeholder held by ANY agent OTHER than the caller's own -- (workspace, agent) pair. Disconnect only flips status to 'revoked' — no -- product path ever hard-deletes the row — so a revoked row would otherwise -- pin the bot's app_id slot forever with no self-serve recovery, even across -- workspaces (workspace A disconnects; workspace B, which proves control by -- holding the same app credentials, rebinds). Revoke is the owner's explicit -- "I'm done with this bot", so any revoked row is reclaimable — only the -- caller's OWN revoked row is spared (reactivated in place; see below). -- 2. an ORPHAN whose owning workspace OR agent row no longer exists — the -- workspace was deleted, or the agent was hard-deleted on runtime teardown. -- With no FK the installation outlives its owner and keeps occupying the -- app_id slot: the "ghost binding" that made a bot un-rebindable (#4810). -- -- Deliberately NOT dead (the caller refuses these with an accurate conflict): -- - the SAME agent's own revoked row (agent_id = @agent_id): the upsert -- reactivates it in place, preserving its installation_id and every binding; -- - a live ACTIVE owner whose agent still exists — INCLUDING an ARCHIVED agent: -- archive is reversible, so its bot stays owned rather than being silently -- stolen. Only a hard delete frees the slot. -- -- The guard lives in the DELETE predicate (not a prior SELECT) so under READ -- COMMITTED the row is re-checked at execution (EvalPlanQual): a concurrent -- same-agent reconnect that flips the revoked row back to 'active' first makes -- the predicate re-check fail, this deletes nothing, and no dependents are -- touched — closing the read-then-delete TOCTOU. Dependent cleanup keys off the -- actually-deleted id (the `dead` CTE), so it runs ONLY for a row this statement -- removed. The (channel_type, app_id) unique index guarantees at most one match. WITH dead AS ( DELETE FROM channel_installation ci WHERE ci.channel_type = sqlc.arg('channel_type') AND ci.config ->> 'app_id' = sqlc.arg('app_id')::text AND ( (ci.status = 'revoked' AND NOT (ci.workspace_id = sqlc.arg('workspace_id') AND ci.agent_id = sqlc.arg('agent_id'))) OR NOT EXISTS (SELECT 1 FROM workspace w WHERE w.id = ci.workspace_id) OR NOT EXISTS (SELECT 1 FROM agent a WHERE a.id = ci.agent_id) ) RETURNING ci.id ), cleared_chat_sessions AS ( DELETE FROM channel_chat_session_binding WHERE installation_id IN (SELECT id FROM dead) RETURNING chat_session_id ), cleared_outbound_cards AS ( -- channel_outbound_card_message is keyed by chat_session_id (no installation_id, -- no FK), so it is reached through the just-removed chat-session bindings. On an -- orphan reclaim the chat_session row itself is already cascade-gone, but its -- binding survived and still carries the id — the only reliable link back. DELETE FROM channel_outbound_card_message WHERE chat_session_id IN (SELECT chat_session_id FROM cleared_chat_sessions) ), cleared_binding_tokens AS ( DELETE FROM channel_binding_token WHERE installation_id IN (SELECT id FROM dead) ), cleared_user_bindings AS ( DELETE FROM channel_user_binding WHERE installation_id IN (SELECT id FROM dead) ), cleared_inbound_dedup AS ( DELETE FROM channel_inbound_message_dedup WHERE installation_id IN (SELECT id FROM dead) ), detached_audit AS ( -- Reclaim keeps the DETACH semantics: the workspace still exists, so a -- NULL-installation audit row stays meaningful for operator triage. The hard- -- delete paths (DeleteWorkspace / runtime teardown) purge audit outright. UPDATE channel_inbound_audit SET installation_id = NULL WHERE installation_id IN (SELECT id FROM dead) ) SELECT id FROM dead; -- name: DeleteChannelInstallationsByArchivedRuntimeAgents :exec -- Application-layer replacement for the (deliberately absent, MUL-3515 §4) -- workspace/agent ON DELETE CASCADE: on runtime teardown, before the archived -- agents are hard-deleted, remove every channel installation they own — plus all -- of each installation's dependent rows — so no orphaned installation keeps -- occupying its bot's (channel_type, app_id) routing slot after its agent is gone -- (#4810). MUST run in the same tx as, and BEFORE, DeleteArchivedAgentsByRuntime. -- Mirrors the agent hard-delete predicate (runtime_id, archived_at IS NOT NULL) -- exactly. WITH doomed AS ( SELECT id FROM channel_installation WHERE agent_id IN ( SELECT id FROM agent WHERE runtime_id = sqlc.arg('runtime_id') AND archived_at IS NOT NULL ) ), cleared_chat_sessions AS ( DELETE FROM channel_chat_session_binding WHERE installation_id IN (SELECT id FROM doomed) RETURNING chat_session_id ), cleared_outbound_cards AS ( -- Reach channel_outbound_card_message (keyed by chat_session_id, no FK) -- through the just-removed chat-session bindings, same as the reclaim path. DELETE FROM channel_outbound_card_message WHERE chat_session_id IN (SELECT chat_session_id FROM cleared_chat_sessions) ), cleared_binding_tokens AS ( DELETE FROM channel_binding_token WHERE installation_id IN (SELECT id FROM doomed) ), cleared_user_bindings AS ( DELETE FROM channel_user_binding WHERE installation_id IN (SELECT id FROM doomed) ), cleared_inbound_dedup AS ( DELETE FROM channel_inbound_message_dedup WHERE installation_id IN (SELECT id FROM doomed) ), cleared_audit AS ( -- Hard delete: purge audit rows rather than detaching them into permanently -- unattributable NULL rows (channel_inbound_audit has no workspace_id / reaper). DELETE FROM channel_inbound_audit WHERE installation_id IN (SELECT id FROM doomed) ) DELETE FROM channel_installation WHERE id IN (SELECT id FROM doomed); -- name: ListChannelInstallationsByWorkspace :many -- Scoped by channel_type so a per-channel management surface (e.g. the Lark -- installation list) only ever sees its own platform's installations. SELECT * FROM channel_installation WHERE workspace_id = sqlc.arg('workspace_id') AND channel_type = sqlc.arg('channel_type') ORDER BY created_at ASC; -- name: ListActiveChannelInstallations :many -- Boot path for a per-channel-type inbound hub: every active installation of -- the given channel_type, so a hub claims leases and opens connections only -- for its own platform and never supervises another channel's installation. -- -- The JOINs require the owning workspace and agent rows to still exist. -- channel_installation has no FK (MUL-3515 §4), so unlike the old -- lark_installation (which cascaded away on workspace/agent deletion) an -- installation can be orphaned when its workspace is deleted or its agent is -- hard-deleted (e.g. runtime teardown). Without this guard the hub would keep -- opening a WebSocket for a bot whose workspace/agent is gone. The JOIN matches -- the old ON DELETE CASCADE semantics: it filters on row existence, not agent -- archival, so an archived-but-present agent's installation is still listed. SELECT ci.* FROM channel_installation ci JOIN workspace w ON w.id = ci.workspace_id JOIN agent a ON a.id = ci.agent_id WHERE ci.status = 'active' AND ci.channel_type = sqlc.arg('channel_type') ORDER BY ci.created_at ASC; -- name: ListAllActiveChannelInstallations :many -- Boot path for the channel-agnostic engine Supervisor (MUL-3620): every -- active installation across ALL channel types, so one Supervisor drives every -- platform's connections rather than a per-platform hub. This is the de- -- hardcoded counterpart of ListActiveChannelInstallations — the Supervisor -- routes each row to its registered channel.Factory by channel_type, so it -- never needs to know which platforms exist. Same orphan guard as the per-type -- query: the workspace + agent JOINs drop installations whose owning rows are -- gone (channel_installation has no FK, MUL-3515 §4), matching the old ON -- DELETE CASCADE semantics (row existence, not agent archival). SELECT ci.* FROM channel_installation ci JOIN workspace w ON w.id = ci.workspace_id JOIN agent a ON a.id = ci.agent_id WHERE ci.status = 'active' ORDER BY ci.created_at ASC; -- name: SetChannelInstallationStatus :exec UPDATE channel_installation SET status = $2, updated_at = now() WHERE id = $1; -- name: SetChannelInstallationConfig :exec -- Replaces the whole config blob for one installation. Used by the -- operator backfills (e.g. setting a freshly-fetched bot_union_id) that -- read-modify-write the JSON in Go and persist it back atomically by id. UPDATE channel_installation SET config = $2, updated_at = now() WHERE id = $1; -- name: BackfillChannelInstallationRegionToFeishuLark :execrows -- Operator repair, feishu-only: flip every feishu installation still -- carrying region='feishu' to 'lark'. Called only on deployments whose -- legacy global base-URL override pointed at Lark international. Idempotent. UPDATE channel_installation SET config = jsonb_set(config, '{region}', '"lark"'), updated_at = now() WHERE channel_type = 'feishu' AND config ->> 'region' = 'feishu'; -- name: AcquireChannelWSLease :one -- Atomically claims the WebSocket lease. CAS predicate accepts when no -- holder exists, the holder expired, or the holder is us (renewal). UPDATE channel_installation SET ws_lease_token = sqlc.arg('new_token'), ws_lease_expires_at = sqlc.arg('new_expires_at'), updated_at = now() WHERE id = sqlc.arg('id') AND status = 'active' AND ( ws_lease_token IS NULL OR ws_lease_expires_at < now() OR ws_lease_token = sqlc.arg('new_token') ) RETURNING *; -- name: ReleaseChannelWSLease :exec -- Drops the lease iff we are still the holder. UPDATE channel_installation SET ws_lease_token = NULL, ws_lease_expires_at = NULL, updated_at = now() WHERE id = $1 AND ws_lease_token = sqlc.arg('current_token'); -- ===================== -- channel_user_binding -- ===================== -- name: CreateChannelUserBinding :one -- Records that a platform user id (per-installation; Feishu open_id) maps -- to a Multica user. The old composite member-FK is gone, so this no -- longer fails when the redeemer is not a workspace member — the caller -- (BindingTokenService.RedeemAndBind) validates membership explicitly -- before calling. ON CONFLICT DO UPDATE is still gated on multica_user_id -- matching, so a second redeemer cannot steal an already-bound user id; -- a cross-user conflict updates zero rows and the caller maps that to -- ErrBindingAlreadyAssigned. config carries secondary identity (union_id). INSERT INTO channel_user_binding ( workspace_id, multica_user_id, installation_id, channel_type, channel_user_id, config ) VALUES ( $1, $2, $3, $4, $5, $6 ) ON CONFLICT (installation_id, channel_user_id) DO UPDATE SET -- jsonb_strip_nulls(EXCLUDED.config) preserves the old lark semantics -- `union_id = COALESCE(EXCLUDED.union_id, lark_user_binding.union_id)`: -- a re-bind that carries `{"union_id": null}` (or omits the key) must NOT -- erase a union_id we already captured. Only non-null incoming keys win. config = channel_user_binding.config || jsonb_strip_nulls(EXCLUDED.config), bound_at = now() WHERE channel_user_binding.multica_user_id = EXCLUDED.multica_user_id RETURNING *; -- name: GetChannelUserBindingByUserID :one -- The inbound identity lookup: does this platform user id map to a Multica -- user for this installation? With the member-FK removed, a row's -- existence no longer proves current workspace membership — the dispatcher -- re-checks membership after this lookup. SELECT * FROM channel_user_binding WHERE installation_id = $1 AND channel_user_id = $2; -- name: FindReusableChannelUserBinding :one -- Cross-installation account-link reuse (MUL-3911). When a platform user -- messages an installation they have NOT linked, but the SAME user id is already -- bound to ANOTHER installation in the SAME Multica workspace + SAME Slack team, -- the inbound identity step reuses that link instead of re-prompting. Slack user -- ids are stable within a team, so an identical channel_user_id denotes the same -- human across that team's apps. The match is fenced to one workspace AND one -- team (installation config->>'team_id'): a Slack team can be connected to two -- different Multica workspaces, and a user may hold different Multica accounts in -- each, so reuse must cross neither boundary. Most-recently-bound wins. The -- caller re-checks membership and materializes a fresh per-installation binding. -- -- team_id is pinned ::text so sqlc types the arg as a string instead of -- attributing the bare param to the JSONB config column (mirrors -- GetChannelInstallationByAppID's app_id cast). SELECT b.* FROM channel_user_binding b JOIN channel_installation ci ON ci.id = b.installation_id WHERE b.workspace_id = sqlc.arg('workspace_id') AND b.channel_type = sqlc.arg('channel_type') AND b.channel_user_id = sqlc.arg('channel_user_id') AND ci.config ->> 'team_id' = sqlc.arg('team_id')::text ORDER BY b.bound_at DESC LIMIT 1; -- name: DeleteChannelUserBindingsByWorkspaceMember :exec -- Application-layer integrity (replaces the old member-FK ON DELETE -- CASCADE): prune every binding for a user who has been removed from a -- workspace, across all installations in that workspace. DELETE FROM channel_user_binding WHERE workspace_id = $1 AND multica_user_id = $2; -- name: DeleteChannelUserBindingsByInstallation :exec -- Application-layer integrity (schema has no FK/cascade, MUL-3515 §4): drop -- every member account link for an installation that is being hard-deleted. -- Rebinding a Feishu bot to a DIFFERENT agent starts a fresh installation, so -- old links do not follow — a different agent is a distinct connection and -- members re-establish their link on first contact. The rows could never be -- reused anyway (every Feishu identity lookup is installation_id-scoped, and -- FindReusableChannelUserBinding is Slack-only), so removing them just keeps -- dead rows from accumulating. DELETE FROM channel_user_binding WHERE installation_id = $1; -- ===================== -- channel_chat_session_binding -- ===================== -- name: CreateChannelChatSessionBinding :one -- channel_chat_id is the session-isolation key (one chat_session per -- (installation_id, channel_chat_id)): Feishu passes the chat id; Slack passes -- a stable key that, for channels, includes the thread root so each @bot thread -- is its own session. config carries any platform-specific outbound routing the -- key alone does not (e.g. Slack's real channel_id when the key is composite); -- it is opaque to the shared session service. INSERT INTO channel_chat_session_binding ( chat_session_id, installation_id, channel_type, channel_chat_id, chat_type, config ) VALUES ( $1, $2, $3, $4, $5, $6 ) RETURNING *; -- name: GetChannelChatSessionBinding :one -- Lookup-by-channel-chat: the inbound dispatcher finds the existing -- chat_session before deciding whether to create one. SELECT * FROM channel_chat_session_binding WHERE installation_id = $1 AND channel_chat_id = $2; -- name: GetChannelChatSessionBindingBySession :one -- Reverse lookup for the outbound patcher: given a chat_session_id, find -- its channel binding to know which (installation, chat_id) to send to. -- Scoped by channel_type so a future non-Feishu binding on the same -- chat_session is never treated as a Feishu reply target. SELECT * FROM channel_chat_session_binding WHERE chat_session_id = sqlc.arg('chat_session_id') AND channel_type = sqlc.arg('channel_type'); -- name: UpdateChannelChatSessionBindingReplyTarget :exec -- Records the most recent inbound trigger message + thread so the decoupled -- outbound patcher can thread its reply back into the originating topic. UPDATE channel_chat_session_binding SET last_message_id = sqlc.narg('last_message_id'), last_thread_id = sqlc.narg('last_thread_id') WHERE chat_session_id = $1; -- name: DeleteChannelChatSessionBindingBySession :exec -- Application-layer integrity (replaces the old chat_session-FK ON DELETE -- CASCADE): drop the binding when its chat_session is deleted. DELETE FROM channel_chat_session_binding WHERE chat_session_id = $1; -- name: DeleteChannelChatSessionBindingsByInstallation :exec -- Retire every chat-session binding for an installation. Used when an -- installation is re-pointed to a different agent (Slack re-connect): each -- existing chat_session is permanently tied to the agent it was created under, -- so reusing it would keep routing the conversation to the OLD agent. Dropping -- the bindings forces the next inbound message to create a fresh session under -- the new agent. The chat_session rows are preserved for history; only the -- channel binding is removed. DELETE FROM channel_chat_session_binding WHERE installation_id = $1 AND channel_type = $2; -- ===================== -- channel_inbound_message_dedup -- ===================== -- name: ClaimChannelInboundDedup :one -- Two-phase idempotency gate with owner fencing. Returns the row when a -- claim is acquired (fresh insert, or stale-reclaim of an in-flight claim -- older than 60s); returns no rows when terminal (processed) or actively -- in-flight. Every claim mints a fresh claim_token; Mark/Release are -- fenced on it. See the table comment in migration 124 / the lark -- predecessor for the full invariant set. INSERT INTO channel_inbound_message_dedup (installation_id, message_id, claim_token) VALUES ($1, $2, gen_random_uuid()) ON CONFLICT (installation_id, message_id) DO UPDATE SET received_at = now(), claim_token = gen_random_uuid() WHERE channel_inbound_message_dedup.processed_at IS NULL AND channel_inbound_message_dedup.received_at < now() - INTERVAL '60 seconds' RETURNING installation_id, message_id, received_at, processed_at, claim_token; -- name: MarkChannelInboundDedupProcessed :execrows -- Locks a claim in as permanently processed after a durable outcome. -- Invoked inside the chat_message tx (via qtx) on the ingest path so the -- durable write and the Mark commit atomically. Token mismatch returns -- zero rows (a reclaim happened); the caller rolls back its in-tx write. UPDATE channel_inbound_message_dedup SET processed_at = now() WHERE installation_id = $1 AND message_id = $2 AND claim_token = $3 AND processed_at IS NULL; -- name: ReleaseChannelInboundDedup :execrows -- Releases an in-flight claim when an infra error occurred before any -- durable side effect, so a retry can re-acquire immediately. Fenced on -- processed_at IS NULL and claim_token. DELETE FROM channel_inbound_message_dedup WHERE installation_id = $1 AND message_id = $2 AND claim_token = $3 AND processed_at IS NULL; -- name: PurgeChannelInboundDedup :exec -- Vacuum job: remove dedup rows older than the supplied cutoff (e.g. 24h). DELETE FROM channel_inbound_message_dedup WHERE received_at < $1; -- ===================== -- channel_inbound_audit -- ===================== -- name: RecordChannelInboundDrop :exec -- The only write path for dropped events. Deliberately carries no body -- column — only routing / identity / drop_reason / timestamp. INSERT INTO channel_inbound_audit ( installation_id, channel_type, channel_chat_id, event_type, channel_event_id, channel_message_id, drop_reason ) VALUES ( sqlc.narg('installation_id'), $1, sqlc.narg('channel_chat_id'), $2, sqlc.narg('channel_event_id'), sqlc.narg('channel_message_id'), $3 ); -- name: ListChannelInboundAuditByInstallation :many SELECT * FROM channel_inbound_audit WHERE installation_id = $1 ORDER BY received_at DESC LIMIT $2 OFFSET $3; -- name: NullChannelInboundAuditInstallationID :exec -- Application-layer stand-in for the old ON DELETE SET NULL (MUL-3515 §4, -- migration 124 keeps installation_id nullable for exactly this): before an -- installation row is hard-deleted, detach its inbound-audit rows by NULLing -- installation_id. The drop-audit history is preserved (channel_type, -- chat/message ids, drop_reason stay) without a dangling reference to a -- removed installation. UPDATE channel_inbound_audit SET installation_id = NULL WHERE installation_id = $1; -- ===================== -- channel_outbound_card_message -- ===================== -- name: CreateChannelOutboundCardMessage :one INSERT INTO channel_outbound_card_message ( chat_session_id, task_id, channel_type, channel_chat_id, channel_card_message_id, status ) VALUES ( $1, sqlc.narg('task_id'), $2, $3, $4, $5 ) RETURNING *; -- name: GetChannelOutboundCardByTask :one -- The partial unique index on (task_id) WHERE task_id IS NOT NULL -- guarantees at most one row. Scoped by channel_type so a future non-Feishu -- card for the same task is not patched as a Feishu card. SELECT * FROM channel_outbound_card_message WHERE task_id = sqlc.arg('task_id') AND channel_type = sqlc.arg('channel_type'); -- name: UpdateChannelOutboundCardStatus :exec UPDATE channel_outbound_card_message SET status = $2, last_patched_at = now() WHERE id = $1; -- name: DeleteChannelOutboundCardMessagesBySession :exec -- Application-layer integrity (channel_* has no FK/cascade, MUL-3515 §4): drop the -- outbound card-message rows for a chat_session being deleted. They are keyed by -- chat_session_id with no FK and no reaper, so the standalone chat-session delete -- path must prune them here alongside DeleteChannelChatSessionBindingBySession — -- otherwise deleting a chat session leaves them as permanent orphans (Elon's -- follow-up on #4810; the workspace/agent/reclaim sweeps already cover their -- paths). A card that survived its session could only mis-route a later patch. DELETE FROM channel_outbound_card_message WHERE chat_session_id = $1; -- ===================== -- channel_binding_token -- ===================== -- name: CreateChannelBindingToken :one -- Mints a single-use binding token for an unbound platform user. TTL cap -- (15 min) enforced by the table CHECK in lockstep with -- channel.BindingTokenTTL. Clamp against the database clock so small clock -- skew between an app node and Postgres cannot reject an otherwise valid -- 15-minute token. The HASH is stored, never the raw token. INSERT INTO channel_binding_token ( token_hash, workspace_id, installation_id, channel_type, channel_user_id, expires_at ) VALUES ( $1, $2, $3, $4, $5, LEAST(sqlc.arg('expires_at')::timestamptz, now() + INTERVAL '15 minutes') ) RETURNING *; -- name: ConsumeChannelBindingToken :one -- Atomic redemption: returns the row only if the hash exists, is -- unconsumed, and unexpired. Two simultaneous redemptions cannot both win. UPDATE channel_binding_token SET consumed_at = now() WHERE token_hash = $1 AND consumed_at IS NULL AND expires_at > now() RETURNING *; -- name: PurgeExpiredChannelBindingTokens :exec DELETE FROM channel_binding_token WHERE expires_at < $1; -- name: DeleteChannelBindingTokensByInstallation :exec -- Application-layer integrity (schema has no FK/cascade, MUL-3515 §4): drop -- every pending binding token for an installation that is being hard-deleted. -- A token stays redeemable for up to 15 min; without this a user who clicks a -- still-unexpired bind link right after the bot was rebound to another agent -- would consume the token and get a "bound" result written against a deleted -- installation — a link that never actually reaches the live bot. DELETE FROM channel_binding_token WHERE installation_id = $1;