fix(cron): normalize string repeat values

[ARegalado1]

Summary

• Normalize cron repeat values before numeric comparisons.
• Accept integer-like strings such as "3" and coerce them to integers.
• Treat non-numeric strings such as "once" and "forever" as unset instead of crashing.
• Preserve one-shot schedule behavior by auto-setting unset repeat values to 1.
• Reuse the same normalization in the cronjob update flow.
• Add regression tests for create, update, numeric-string, and non-numeric-string paths.

Context

LLMs can still pass repeat as a string even though the tool schema declares it as an integer. Before this patch, create/update paths could compare a string to 0 and raise:

TypeError: '<=' not supported between instances of 'str' and 'int'

Refresh note: this branch was rebased onto current main and rewritten as a clean cron-only PR. An unrelated GitHub/local terminal environment commit that was previously on the branch was dropped.

Closes #7142

Test Plan

• python -m py_compile cron/jobs.py tools/cronjob_tools.py
• python -m pytest tests/cron/test_jobs.py tests/cron/test_cron_script.py tests/tools/test_cronjob_tools.py -q -o 'addopts=' — 135 passed
• git diff --check upstream/main...HEAD

[ARegalado1]

Refresh update:

• Rebased onto current main.
• Rewrote the branch as a clean cron-only PR and dropped the unrelated GitHub/local terminal environment commit that was previously included.
• Confirmed [TESTED FIX] TypeError when repeat='once' passed to cronjob create (string-to-int coercion missing) #7142 is still open; fix(cron): coerce repeat parameter to int to prevent TypeError #7589 is closed and fix: 5 bug fixes — cron type coercion, memory hooks, delegate logging, browser cleanup #7424 is a broader batch PR, so this remains useful as the narrow fix.
• Added coverage for:
  • repeat="once" on one-shot create
  • repeat="forever" on recurring create
  • numeric string repeats like "3" / "5"
  • update path string normalization
• Verified locally:
  • python -m py_compile cron/jobs.py tools/cronjob_tools.py
  • python -m pytest tests/cron/test_jobs.py tests/cron/test_cron_script.py tests/tools/test_cronjob_tools.py -q -o 'addopts=' — 135 passed
  • git diff --check upstream/main...HEAD

No GitHub CI checks are currently attached to this fork PR.

[teknium1]

Thanks for the focused fix. The reported failure is present on current main: cron/jobs.py:1009 compares repeat <= 0 during creation, and tools/cronjob_tools.py:946 does the same during tool-driven update. A string supplied despite the schema therefore raises before the existing one-shot/default handling can run.

The PR’s shared normalizer addresses both verified sites and preserves existing semantics for non-positive values and one-shot defaults. The added create/update regressions match the two paths. This is an automated hermes-sweeper review.