Problem

Cron jobs created via API/tool without an explicit enabled flag are silently disabled. The scheduler treats undefined as disabled, causing jobs to never run with no error or warning.

Solution

Default enabled to true in normalizeCronJobInput when applyDefaults is true and enabled is not explicitly set as a boolean.

Changes

• src/cron/normalize.ts: Add default enabled: true when not provided
• src/cron/normalize.test.ts: Add tests for default behavior and explicit false override

Testing

npx vitest run src/cron/normalize.test.ts

fixes #6988

Greptile Overview

Greptile Summary

This PR changes cron job normalization so that when applyDefaults is enabled (used by normalizeCronJobCreate), a missing or non-boolean enabled value is defaulted to true. This aligns API/tool-created jobs (which may omit enabled) with the expected “jobs run by default” behavior, and adds Vitest coverage to ensure the default and an explicit enabled: false override are preserved.

The change is localized to src/cron/normalize.ts’s normalizeCronJobInput defaulting block, and tests are added in src/cron/normalize.test.ts under the existing normalizeCronJobCreate suite.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk.
• The behavior change is narrowly scoped to the applyDefaults path in cron job normalization, matches the described bug, and is covered by targeted tests verifying both the new default and explicit false behavior.
• No files require special attention