fix(outbound): check delivery identity for media results before recording success

xzh-icenter · xzh-icenter · commit 3a7d0ee21bb2 · 2026-06-15T18:52:49.000Z
The sendPayload branch checks hasDeliveryResultIdentity before counting a delivery result as sent, but the media branch was missing this check. When a channel adapter returns a media result with no messageId or other identity fields (e.g. QQBot rejecting a TTS temp file outside its media roots), the delivery was incorrectly recorded as successful. This caused cron auto-TTS deliveries to QQBot to be reported as delivered when the message was actually lost, since the generated audio file was outside QQBot's allowed media roots and the adapter returned an error result with no delivery identity. Add the same hasDeliveryResultIdentity check to the media delivery loop so that no-identity media results are properly skipped, consistent with the sendPayload branch behavior. Fixes #92816
diff --git a/src/infra/outbound/deliver.ts b/src/infra/outbound/deliver.ts
@@ -1424,7 +1424,7 @@ async function deliverOutboundPayloadsCore(
           agentId: params.session?.agentId ?? params.mirror?.agentId,
           mediaSources,
           mediaAccess: params.mediaAccess,
-          sessionKey: params.session?.key,
+          sessionKey: params.session?.policyKey ?? params.session?.key,
           messageProvider: params.session?.key ? undefined : channel,
           accountId: params.session?.requesterAccountId ?? accountId,
           requesterSenderId: params.session?.requesterSenderId,
@@ -1891,6 +1891,9 @@ async function deliverOutboundPayloadsCore(
               unit.overrides,
             )
           : await deliveryHandler.sendMedia(unit.caption ?? "", unit.mediaUrl, unit.overrides);
+        if (!hasDeliveryResultIdentity(delivery)) {
+          continue;
+        }
         results.push(delivery);
         firstMessageId ??= delivery.messageId;
         lastMessageId = delivery.messageId;
