feat(cron): per-job max_turns override (CLI-only, mirrors reasoning_effort)

[dkswhale]

Summary

Let a cron job carry its own agent turn budget: hermes cron create/edit --max-turns N.

Long multi-phase jobs (browse → plan → generate → QA) legitimately need more turns than the shared agent.max_turns default. Today the only lever is the global value, which spends the same budget on every other job and on every interactive session. This mirrors the existing per-job reasoning_effort override end to end.

Changes

• cron/jobs.py — _normalize_job_max_turns validates at the store choke point: positive int stored; 0/empty clears; anything else raises before the merge so nothing invalid persists. create_job(max_turns=) persists the key only when set, so pre-feature records stay byte-identical.
• cron/scheduler.py — _resolve_job_turn_limit(job, config_limit): the job's value wins over the config-resolved limit and is logged (Job 'x': per-job max_turns override -> N) so an operator can verify it applied from the run log. A garbage value in a hand-edited store warns and follows config instead of killing the tick.
• CLI — --max-turns on cron create and cron edit (0 clears on edit); Max turns: shown in the create/edit summaries.
• tools/cronjob_tools.py — plumbed through cronjob() for the CLI, but deliberately absent from CRONJOB_SCHEMA: same CLI-only lane as reasoning_effort — a turn budget is a spend decision, so the model never sets it.
• tests/cron/test_cron_job_max_turns.py — store contract + scheduler precedence (21 cases).

Motivation (real incident)

A three-phase daily content pipeline ran under max_turns: 160/110/200 set directly in jobs.json (a local patch). After an update dropped the patch, every phase silently ran at the global 60 and the planner phase stopped mid-write two days in a row with reached the iteration limit. Raising the global to 200 works but is the wrong tool — it changes every job and every chat session.

Test plan

• pytest tests/cron/test_cron_job_max_turns.py tests/cron/test_scheduler.py tests/cron/test_jobs.py tests/cron/test_cron_reasoning_effort.py tests/tools/test_cronjob_tools.py → all pass (375).
• hermes cron create --help shows --max-turns.

🤖 Generated with Claude Code

https://claude.ai/code/session_01HQ7VR1qRcF6jQjQ7h6jsd1

[alt-glitch]

This was generated by AI during triage.

Related: #45809 and #57285 also implement per-job cron turn budgets. This PR deliberately keeps the setting CLI-only and omits the wall-clock timeout path, so it is a narrower competing design rather than a duplicate.