Greptile Summary

This PR fixes a bug where the deliverViaDirect path in cron delivery was sending raw response text without applying the configured responsePrefix, while the interactive reply path was already applying it correctly via resolveEffectiveMessagesConfig. The fix resolves the prefix for the delivery channel/account and prepends it to each payload's text, with a startsWith guard to prevent double-prefixing.

Key changes:

• Imports resolveEffectiveMessagesConfig from ../../agents/identity.js
• Calls resolveEffectiveMessagesConfig at the top of deliverViaDirect (outside the try block, consistent with the existing resolveAgentOutboundIdentity call)
• Constructs rawPayloads first, then maps them with applyPrefix only when responsePrefix is truthy
• applyPrefix handles undefined text, falsy prefix, and already-prefixed text safely

The implementation is symmetric with the interactive reply path and also correctly applies to the fallback case (announce fails → direct delivery), since deliverViaDirect reads the outer closure's deliveryPayloads which may have been updated by deliverViaAnnounce.

Confidence Score: 4/5

• This PR is safe to merge — it is a targeted, one-file bug fix with no structural changes.
• The change is small and well-scoped: it mirrors the existing responsePrefix logic used in the interactive reply path. The startsWith guard prevents double-prefixing, the !responsePrefix falsy guard handles unconfigured cases, and the placement of resolveEffectiveMessagesConfig outside the try block is consistent with the pre-existing pattern. No new permissions or secrets handling. The one minor caveat is there are no automated tests covering the new code path in this diff, but the logic is straightforward enough to have high confidence.
• No files require special attention.

_{Last reviewed commit: 0aed3a7}