Summary

• fix cron.update compatibility for payload patches that include agent-turn fields (for example payload.model) without an explicit payload.kind
• infer payload.kind = "agentTurn" during cron patch normalization when agent-turn-only hints are present
• add regression coverage in both normalization unit tests and gateway cron e2e flow

Problem

cron.update can receive partial payload patches from clients/tools. When a patch contains only agent-turn fields (like model) and omits kind, request validation rejects
it because payload.kind is required by schema.

Root Cause

Cron patch normalization inferred payload kind for message/text cases, but did not infer kind for model/thinking/timeout/delivery-only agent-turn patches.

Fix

• extend normalizeCronJobPatch path (normalizeCronJobInput -> coercePayload) to infer kind: "agentTurn" when kind is missing and payload contains agent-turn-specific
  fields
• preserve existing behavior for requests that already include kind

Changes

• src/cron/normalize.ts
  • infer agent-turn kind for payload patches containing agent-turn hints
• src/cron/normalize.test.ts
  • add unit regression: model-only payload patch infers kind: "agentTurn"
• src/gateway/server.cron.e2e.test.ts
  • add e2e regression: cron.update accepts model-only payload patch, keeps existing message, updates model

Safety

• inference is applied only when payload.kind is missing
• no behavior change for valid explicit-kind requests
• strict schema validation remains unchanged

Testing

• pnpm test src/cron/normalize.test.ts
• pnpm vitest run --config vitest.e2e.config.ts src/gateway/server.cron.e2e.test.ts

Greptile Overview

Greptile Summary

This PR extends cron patch normalization so cron.update can accept payload patches that only include agent-turn fields (e.g. payload.model) without explicitly providing payload.kind. The core change is in src/cron/normalize.ts where coercePayload infers kind: "agentTurn" when certain agent-turn “hints” are present, and new unit + e2e tests cover the model-only patch scenario through the gateway handler.

Confidence Score: 4/5

• Mostly safe to merge, but kind inference logic may be too permissive for delivery-only payload patches.
• Change is small and covered by new unit + e2e tests, but the new agentTurn inference triggers on legacy delivery fields (channel/to/deliver/bestEffortDeliver) which can unintentionally coerce otherwise-invalid/ambiguous patches into agentTurn payloads. If that broadening is unintended, it should be tightened before merging.
• src/cron/normalize.ts

_{Last reviewed commit: bc3d639}