mirror of
https://github.com/multica-ai/multica.git
synced 2026-07-13 05:16:29 +02:00
* feat(integrations): add platform-agnostic channel foundation Introduce server/internal/integrations/channel — the contract every inbound IM integration implements, so the core never learns a platform's event JSON. Four pieces: - Channel interface (Type/Connect/Disconnect/Send/Capabilities) + Factory + Config (channel_type + opaque JSON blob, maps to channel_installation). - Normalized InboundMessage/OutboundMessage envelopes + Source/MediaRef/ ReplyCtx/MsgType/ChatType. Envelope holds only cross-platform-true fields; platform specifics live in Raw, read only by the adapter. - Capability bitmask: declaration only, no degrade logic in core. - Registry: Type->Factory map, last-writer-wins, concurrency-safe. Pure package (no DB/network/platform deps). Foundation for MUL-3515; the lark cutover + lark_*->channel_* generalization land in follow-up PRs. MUL-3515 Co-authored-by: multica-agent <github@multica.ai> * feat(channel): generalize lark_* tables into channel_* (DB layer) Migration 123 creates channel_installation / channel_user_binding / channel_chat_session_binding / channel_inbound_message_dedup / channel_inbound_audit / channel_outbound_card_message / channel_binding_token. Each carries a channel_type discriminator and a JSONB config for platform-specific identifiers/credentials; cross-platform columns stay flat. Existing Feishu rows are backfilled (channel_type= 'feishu', app_secret_encrypted via base64). NO foreign keys / cascades (MUL-3515 §4) — integrity moves to the app layer in the cutover. queries/channel.sql ports the lark query surface to channel_*, JSONB-aware, plus DeleteChannelUserBindingsByWorkspaceMember / DeleteChannelChatSessionBindingBySession for the app-layer cleanup that replaces the removed cascades. lark_* tables/queries are left in place here and removed once the Go cutover lands, so this commit ships green on its own. Verified: sqlc generate, go build ./..., full migrate chain (1..123) on Postgres 17, and a real-data backfill spot-check (base64 round-trip, NULL-strip, functional unique index on (channel_type, app_id)). MUL-3515 Co-authored-by: multica-agent <github@multica.ai> * fix(channel): name app_id query param + multi-IM install key + null-safe binding merge Addresses review on MUL-3515 (PR #4412): - GetChannelInstallationByAppID: explicitly name params and cast app_id to ::text so sqlc emits AppID string. A bare $2 next to `config ->> 'app_id'` was mis-attributed to the JSONB config column, generating Config []byte. - channel_installation uniqueness -> (workspace_id, agent_id, channel_type), with the UpsertChannelInstallation conflict key matched. Lets one agent hold one installation per IM (feishu + slack + ...) instead of a later install clobbering an earlier one. Behaviorally identical in the current feishu-only world; "one agent, at most one IM overall" stays an app-layer rule per MUL-3515 §4, not a DB constraint. - CreateChannelUserBinding merges jsonb_strip_nulls(EXCLUDED.config) so a re-bind carrying {"union_id": null} no longer erases an already-captured union_id, restoring the old COALESCE(EXCLUDED.union_id, ...) semantics. Regenerated with sqlc v1.31.1. Verified on PG17: re-install replaces in place, feishu+slack coexist, null re-bind keeps union_id, real union_id wins. Co-authored-by: multica-agent <github@multica.ai> * feat(lark): channel-backed Feishu store + fix base64 backfill wrapping Cutover step 1 of switching the lark Go code from lark_* onto the channel_* tables (MUL-3515). Introduces the JSONB config boundary the rest of the cutover sits on, and fixes a latent backfill bug surfaced while building it. - migration 123: strip newlines from the app_secret_encrypted base64 backfill. PostgreSQL encode(...,'base64') MIME-wraps at 76 chars, and a secretbox- sealed ~72-byte secret exceeds that. Go's encoding/json decodes a JSON string into []byte with base64.StdEncoding, which rejects embedded newlines, so without the strip every migrated installation would fail to decrypt its app secret once reads move to channel_installation.config. - store.go: flat domain types (Installation / UserBinding / ChatSessionBinding) with field parity to the retired db.Lark* rows, plus the feishu config codec. Row->domain mappers decode the JSONB config; the secret decoder is whitespace-tolerant so legacy MIME-wrapped data still round-trips, while the encoder emits unwrapped base64. Binding config encodes an absent union_id as "{}" so the upsert's jsonb_strip_nulls merge never clobbers a stored union_id. - store_test.go: 72-byte secret round-trip, MIME-wrapped tolerance, optional null-strip, and flat-column preservation. Verified on PG17. Field parity keeps the upcoming ~190 db.LarkInstallation call sites a mechanical rename. No call sites switched yet; behavior unchanged. Co-authored-by: multica-agent <github@multica.ai> * feat(lark): route inbound integration onto channel_* + explicit membership checks Cutover step 2 (MUL-3515): switch the Feishu Go code from the lark_* queries to channel_* via a ChannelStore adapter, and replace the removed member foreign key with explicit application-layer membership checks. No user-visible behavior change. - channel_store.go: ChannelStore embeds *db.Queries and SHADOWS the ~24 lark query methods with channel_*-backed equivalents, keeping the db.Lark* signatures so the dispatcher/hub/services and their ~20k lines of tests stay untouched; the feishu JSONB config is (de)coded by store.go. Adds IsWorkspaceMember and a tx-aware WithTx. Only production wiring swaps *db.Queries for *ChannelStore. - Membership re-check (§4 removed the lark_user_binding -> member FK, so a binding row no longer proves current membership): * the dispatcher inbound identity step verifies membership after the binding lookup; a former member's stale binding is dropped as non_workspace_member + audited and never reaches chat_session (§4.3 safety property). * RedeemAndBind and BindInstallerTx replace the now-dead FK (23503) branch with an explicit IsWorkspaceMember gate, preserving the existing ErrBindingNotWorkspaceMember outcome without burning the token. - router wires the ChannelStore into the patcher, typing indicator, dispatcher, hub, and the union_id/region backfills; constructor-based services wrap *db.Queries internally so their signatures and nil-check tests are unchanged. Verified: go build ./... ; go vet ; gofmt ; go test -race ./internal/integrations/... (full lark suite green unchanged + new membership drop/error tests). Adapter field mappings (secret base64, union_id RMW, chat-id/open-id remaps, dedup, token, card) checked end-to-end against a PG17 channel_* schema. lark_* tables and queries remain (unused at runtime) until the S3 cleanup-hooks and S4 drop-tables/rename commits. Co-authored-by: multica-agent <github@multica.ai> * fix(channel): renumber generalization migration 123 -> 124 main merged 123_issue_stage after this branch forked, so the branch's 123_channel_generalization now collides on the migration number. The runner keys schema_migrations by full version string and would still apply both, but a duplicate number is a merge hazard and convention violation, so move the channel migration to the next free slot (124). issue_stage (ALTER issue ADD COLUMN stage) and the channel generalization touch disjoint tables; verified on PG17 that 123_issue_stage applies cleanly on a DB already carrying 124_channel_generalization, so the two are order-independent. sqlc regenerated (v1.31.1): only the migration-number comment changed. MUL-3515 Co-authored-by: multica-agent <github@multica.ai> * feat(channel): prune channel bindings on member removal + chat session delete MUL-3515 §4 dropped every channel_* foreign key, so the old ON DELETE CASCADE that cleared a user's channel_user_binding when they left a workspace, and a chat's channel_chat_session_binding when its chat_session was deleted, no longer fires. Re-establish that integrity in the application layer, inside the existing transactions: revokeAndRemoveMember -> DeleteChannelUserBindingsByWorkspaceMember, DeleteChatSession -> DeleteChannelChatSessionBindingBySession. Adds real-DB tests for both paths, including a scoping check that a remaining member's binding survives the prune. Verified on PG17: both new tests plus the existing revocation tests and the full handler package pass. MUL-3515 Co-authored-by: multica-agent <github@multica.ai> * fix(channel): scope Lark/Feishu store reads to channel_type='feishu' The S2 cutover routed the Feishu integration onto channel_*, but the Lark-facing ChannelStore wrappers read installation / chat-session-binding / outbound-card rows across ALL channel_type values. Once a second IM exists, that would let the Lark hub supervise a non-Feishu installation, the Lark install list show it, /lark/installations/{id} revoke another channel's row, and the outbound patcher / typing indicator act on a non-Feishu chat binding or card. Add a channel_type predicate to the six read/list channel queries and pass channelTypeFeishu from every wrapper: GetChannelInstallation, GetChannelInstallationInWorkspace, ListChannelInstallationsByWorkspace, ListActiveChannelInstallations, GetChannelChatSessionBindingBySession, GetChannelOutboundCardByTask. The S3 cleanup deletes (DeleteChannelUserBindingsByWorkspaceMember / DeleteChannelChatSessionBindingBySession) stay all-channel on purpose: a member leaving or a chat_session being deleted should clear every IM's binding. Adds a real-DB test that seeds a Slack installation/binding/card next to the Feishu ones and asserts the Lark wrappers never return them. MUL-3515 Co-authored-by: multica-agent <github@multica.ai> * refactor(channel): replace db.Lark* translation layer with lark domain types S2 introduced ChannelStore as a translation layer that read/wrote channel_* but kept the retired db.Lark* struct/param shapes so the dispatcher/hub/services and their ~20k lines of tests did not have to change. This collapses that layer: the store now takes and returns the package's flat domain types (Installation, UserBinding, ChatSessionBinding, InboundMessageDedup, BindingTokenRow, OutboundCardMessage) and the *Params types in params.go, with channel-neutral field names (ChannelUserID / ChannelChatID / ...). All call sites, fakes, and tests move to the domain types. No behavior change: only channel_* is read/written (as before); db.Lark* is now unused, and the lark_* tables + queries/lark.sql are removed in the next commit. Verified on PG17: go build / vet / gofmt clean, go test -race ./internal/integrations/... green (the ~20k-line fake suite), and the lark + handler suites pass. MUL-3515 Co-authored-by: multica-agent <github@multica.ai> * refactor(channel): drop lark_* tables and queries (remove old path) The Go cutover (previous commit) moved the lark package entirely onto channel_* and the domain types, leaving the lark_* tables, queries/lark.sql, and the generated db.Lark* models unused. Remove them per the design (§5: replace, do not keep both): migration 125 drops the seven lark_* tables (data already lives in channel_* since migration 124), and queries/lark.sql is deleted + sqlc regenerated, removing the db.Lark* models and lark query methods. The 125 down recreates the authoritative pre-drop schema (bot_union_id, region, per-installation dedup PK, thread-reply columns). Verified on PG17: fresh migrate up ends with lark_* gone + channel_* present; isolated 125 down/up round-trips correctly; go build / vet / gofmt clean; go test -race ./internal/integrations/... and the handler suite pass. MUL-3515 Co-authored-by: multica-agent <github@multica.ai> * fix(migrations): remove trailing blank line at EOF of 125 down migration git diff --check flagged a blank line at EOF of 125_drop_lark_tables.down.sql (a pg_dump-generation artifact). Whitespace only; the recreate SQL is unchanged. MUL-3515 Co-authored-by: multica-agent <github@multica.ai> * refactor(channel): defer lark_* table drop to a follow-up migration Preflight deploy review: dropping lark_* in the same release that cuts over (old migration 125) is not rollback/rolling-safe — the v0.3.27 release still reads lark_*, so a rolling deploy or a post-deploy code rollback would hit "relation does not exist". Remove the drop and keep the old tables for one release (standard expand/contract): migration 124 already backfilled lark_* -> channel_*, the new code reads/writes only channel_*, and the physical drop moves to a separate cleanup migration once this ships and is observed. The lark_* tables remain in the schema, so sqlc regenerates the (now unused) db.Lark* models; queries/lark.sql stays deleted (the new code uses channel_*). No code path reads lark_* — only the destructive drop is deferred, keeping the design's no-compat-layer / no-dual-write rule while being deploy-safe. MUL-3515 Co-authored-by: multica-agent <github@multica.ai> * fix(channel): skip orphaned installations in hub-boot active scan Preflight deploy review: channel_installation dropped the workspace/agent FK (MUL-3515 §4), so unlike lark_installation it does not cascade away when its workspace is deleted or its agent is hard-deleted (e.g. runtime teardown). The hub-boot query then keeps opening a WebSocket for a bot whose owner is gone. JOIN ListActiveChannelInstallations to live workspace + agent so an orphaned installation is never connected, uniformly for every deletion path. The JOIN matches the old ON DELETE CASCADE semantics (row existence, not agent archival), so an archived-but-present agent's installation is still listed; the orphaned row's encrypted secret is thereby never decrypted/used. Tests: a real-DB handler test asserts a deleted-workspace/agent installation and a non-Feishu one are both excluded; the lark scope test's active-list assertion moved there since the JOIN now needs real workspace/agent fixtures. (Physically deleting dormant orphaned channel rows on workspace/agent deletion is a separate app-layer-cleanup follow-up.) MUL-3515 Co-authored-by: multica-agent <github@multica.ai> * docs(channel): document non-rolling cutover constraint for the lark->channel migration Elon deploy review: keeping the lark_* tables (deferred drop) stops old v0.3.27 code from crashing, but is not full expand/contract. Migration 124 is a one-time backfill; afterwards new code runs on channel_* (lease + dedup on channel_*) while pre-cutover code runs on lark_* (lease + dedup on lark_*). If both run concurrently during a rolling deploy, each side claims the same Feishu bot's WS lease on its own table and double-processes inbound events. This release therefore requires a NON-ROLLING cutover (stop the old hub before applying migration 124 + starting new code; rollback is not lossless once new code writes channel_*). Documented where deployers/reviewers see it: migration 124 header gains a ROLLOUT note; the channel_store.go header is corrected (lark_* tables are retained one release for rollback safety, not "gone"; the store still never touches them). Comment-only — no schema/codegen/behavior change. MUL-3515 Co-authored-by: multica-agent <github@multica.ai> * feat(lark): add MULTICA_LARK_HUB_DISABLED switch for the channel cutover The lark_*->channel_* cutover needs a way to make the Feishu bot briefly unavailable WITHOUT taking down the whole multica-api process — the Lark hub is a goroutine inside it, not a separate Deployment. MULTICA_LARK_HUB_DISABLED=true parks the hub at startup: the API serves HTTP normally but never claims a WS lease or opens a Feishu connection. Rollout (see migration 124 ROLLOUT note): ship the new release with the flag SET so new pods run API-only while old pods (hub on lark_*) drain during the rolling deploy — the two hubs never overlap. After the old pods are gone and migration 124 has run, flip the flag off; the new hub comes up on channel_*. The old backend does NOT need this switch — its hub stops when k8s terminates the old pods, not via a flag. Nil-ing LarkHub reuses the existing not-configured path so both the startup start and the shutdown join skip it. MUL-3515 Co-authored-by: multica-agent <github@multica.ai> * docs(channel): point migration 124 ROLLOUT note at the hub-disable switch Refine the rollout note to use MULTICA_LARK_HUB_DISABLED for a bot-only cutover (new pods serve API with the hub parked while old pods drain; flip the switch off after the migration), instead of the earlier whole-API recreate. Comment-only. MUL-3515 Co-authored-by: multica-agent <github@multica.ai> * docs(channel): fix migration 124 rollout order and document self-host cutover The previous ROLLOUT note shipped the new (channel_*) build before running migration 124, so the channel_*-backed HTTP paths (installation list/install/revoke, chat-session delete, member revoke) would 500 in the window between new-pod boot and the deferred migration. Restate the runbook around two explicit invariants — channel_* must exist before the new build serves those paths, and the old/new hubs must never overlap — and order the steps so channel_* is created first (park old hub -> snapshot -> deploy parked new build -> unpark). Document that default self-host (entrypoint migrate + single-replica Recreate) satisfies both invariants automatically and needs no manual steps; only prd / multi-replica rolling self-host needs the switch procedure. Clarify in main.go that the hub-park switch is generation-agnostic (parks whichever hub the build carries), which is what enables the preparatory release. Refs MUL-3515 Co-authored-by: multica-agent <github@multica.ai> --------- Co-authored-by: J <j@multica.ai> Co-authored-by: multica-agent <github@multica.ai>
356 lines
14 KiB
SQL
356 lines
14 KiB
SQL
-- 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: 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: 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: 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: 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;
|
|
|
|
-- =====================
|
|
-- channel_chat_session_binding
|
|
-- =====================
|
|
|
|
-- name: CreateChannelChatSessionBinding :one
|
|
INSERT INTO channel_chat_session_binding (
|
|
chat_session_id, installation_id, channel_type, channel_chat_id, chat_type
|
|
) VALUES (
|
|
$1, $2, $3, $4, $5
|
|
)
|
|
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;
|
|
|
|
-- =====================
|
|
-- 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;
|
|
|
|
-- =====================
|
|
-- 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;
|
|
|
|
-- =====================
|
|
-- 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. 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, $6
|
|
)
|
|
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;
|