Greptile Summary

This PR fixes a bug where resolveDeliveryTarget() was called unconditionally in runCronIsolatedAgentTurn, allowing the channel:last fallback path to leak into routing even when delivery.mode was "none". The fix guards the call behind deliveryRequested and substitutes a typed ok: false stub so messageChannel and agentAccountId remain undefined in the embedded agent invocation when delivery is disabled.

Key changes:

• run.ts: resolveDeliveryTarget is now only awaited when deliveryRequested === true; otherwise a minimal { ok: false, mode: "implicit", error } value satisfies the DeliveryTargetResolution type without triggering channel lookups
• run.test-harness.ts: resolveCronDeliveryPlanMock and resolveDeliveryTargetMock are now exported as independently controllable mocks; the old hardcoded "discord" channel return is removed and replaced with a correct no-delivery default
• New regression test: Directly covers the delivery.mode=none + channel:last scenario from issue Bug: Cron delivery mode 'none' + channel 'last' causes Message failed #30393, asserting resolveDeliveryTarget is never called and messageChannel passed to the embedded agent is undefined

Confidence Score: 5/5

• This PR is safe to merge — the fix is minimal, well-scoped, and directly tested against the regression scenario.
• The change is a targeted conditional guard around a single function call. The stub value correctly satisfies the DeliveryTargetResolution discriminated union type. All downstream consumers of resolvedDelivery are either already gated on deliveryRequested or operate safely with undefined channel/accountId fields. The new regression test and the refactored harness improve confidence that the fix works and that future changes to delivery logic won't regress silently.
• No files require special attention.

_{Last reviewed commit: 58a2f2d}

This pull request has been automatically marked as stale due to inactivity.
Please add updates or it will be closed.