Libra CodeHub

CedarCopilot/cedar-mail

CodePull requests7CommitsInsightsRuns
cedar-mail/aws/__tests__/__snapshots__
conversation-sync-state-machine.jsonfix(conversation-sync): thread connectionId into search-sync Map via KV context The search Map iterated over query strings and (via createMapWithContext) passed only the bare query as $.item, so conversationSyncSearch got an empty connectionId on the Step Functions path and every provider lookup ran WHERE id = ''. Mirror the meeting-sync workaround: conversation-sync.setup stashes a run:{id}:search-map-ctx KV blob (connectionId, connectionData, maxResults, folder, queryContexts), the search Map wraps each query into { query }, and conversationSyncSearch hydrates the connection context from KV when connectionId is absent (local runtime path still passes it directly). Adds a hydration regression test and updates the CDK snapshot.Jul 13, 2026, 9:01 PM