fix(cron): keep deliberate delivery-target refusals as error status

Alix-007 · Alix-007 · commit cbe864868b76 · 2026-06-21T15:20:05.000+08:00
The #94058 fix kept isolated turn status=ok when post-run delivery fails, but the broad `status === "error"` check also caught the #91613 keyless implicit last-target refusal, which is a deliberate delivery-target guard (errorKind "delivery-target") and must stay status=error. Exclude that errorKind so genuine delivery dispatch failures still become ok while target-guard refusals remain errors.
diff --git a/src/cron/isolated-agent/run.ts b/src/cron/isolated-agent/run.ts
@@ -1323,8 +1323,12 @@ async function finalizeCronRun(params: {
       // execution status made the outer scheduled run report `status=error`
       // for a session that actually ended successfully (#94058). Delivery
       // failure is recorded separately via `delivered`/`deliveryAttempted` and
-      // delivery diagnostics, which drive the decoupled run-log delivery status.
-      if (deliveryResult.result.status === "error" && !params.isAborted()) {
+      // delivery diagnostics, while deliberate target-guard refusals stay errors.
+      if (
+        deliveryResult.result.status === "error" &&
+        deliveryResult.result.errorKind !== "delivery-target" &&
+        !params.isAborted()
+      ) {
         return resolveRunOutcome({
           delivered: resultWithDeliveryMeta.delivered ?? deliveryResult.delivered,
           deliveryAttempted: resultWithDeliveryMeta.deliveryAttempted,
