Best possible solution:

Close this branch and keep shared empty-identity accounting review on #79811; keep live QQBot cron auto-TTS delivery review on #92947.

Do we have a high-confidence way to reproduce the issue?

Yes, from source inspection: current main can push a media adapter result with an empty messageId, making durable send see a non-empty result set. I did not run a live QQBot cron reproduction for this branch.

Is this the best way to solve the issue?

No, not as the best landing path. The patch is plausible for media-only accounting, but the broader open PR is the better canonical fix because it applies the same identity contract across sibling outbound result paths.

Security review:

Security review cleared: The diff only changes TypeScript delivery accounting and a colocated regression test; it does not touch dependencies, workflows, credentials, auth, secrets, or supply-chain execution.

AGENTS.md: found and applied where relevant.

What I checked:

• Current main media accounting gap: On current main, the media branch still pushes each adapter media result before checking delivery identity, so a result object with an empty messageId can make the returned result set non-empty. (src/infra/outbound/deliver.ts:1894, 9ba6ed1d5cb8)
• Existing identity invariant: The neighboring sendPayload path already suppresses results that fail hasDeliveryResultIdentity, which is the invariant this PR applies only to the media branch. (src/infra/outbound/deliver.ts:1730, 9ba6ed1d5cb8)
• Canonical broader accounting PR: fix(cron): avoid delivered status for empty outbound receipts #79811 is open, mergeable clean, has positive real-behavior proof, and applies the identity-required contract across shared text, formatted-text, and media result collection rather than only this media path. (e046c2868b6a)
• Prior duplicate precedent: fix(outbound): suppress media sends without delivery identity #92826 was the same media-only accounting shape and was already closed as superseded by the broader accounting PR. (src/infra/outbound/deliver.ts:1891, 9b1590c09488)
• Complementary live QQBot delivery fix: fix(qqbot): deliver cron auto-TTS voice by trusting OpenClaw temp root #92947 is open, mergeable clean, has live QQBot proof, and handles the actual cron auto-TTS temp-root media delivery path separately from shared accounting. (56567160ed1d)
• Current PR proof state: The current PR body lists install, focused Vitest, and diff-check commands but no after-fix real behavior proof; the live PR status includes a failed Real behavior proof check. (774c24ad5cff)

Likely related people:

• indulgeback: Authored the broader open accounting PR that covers this PR's media branch plus sibling text and formatted-text empty-identity paths. (role: canonical open fix author; confidence: high; commits: e046c2868b6a; files: src/infra/outbound/deliver.ts, src/infra/outbound/deliver.test.ts, src/cron/isolated-agent.direct-delivery-core-channels.test.ts)
• steipete: GitHub path history shows repeated foundational work on shared outbound delivery, channel delivery seams, and related state/refactor surfaces. (role: feature-history owner; confidence: medium; commits: 5a6eddf5d0d5, f91de52f0d23, 1507a9701b83; files: src/infra/outbound/deliver.ts, src/channels/message/send.ts, extensions/qqbot/src/channel.ts)
• cxyhhhhh: Merged QQBot group/chat media work introduced much of the unified media upload and local media handling surface connected to this bug path. (role: original QQBot media contributor; confidence: high; commits: 5ccf179a34a9; files: extensions/qqbot/src/engine/messaging/outbound-media-send.ts, extensions/qqbot/src/channel.ts)
• zhangguiping-xydt: Recently touched QQBot media failure surfacing near the no-identity media result shape used by the linked report. (role: recent QQBot media contributor; confidence: medium; commits: 650c5cac3326; files: extensions/qqbot/src/channel.ts)

Codex review notes: model internal, reasoning high; reviewed against 9ba6ed1d5cb8.