coldxiangyu 7527961b19 fix(cron): drop top-level oneOf so OpenAI Codex/Responses accept tool schema ...

PR #3125 added a top-level `oneOf` branch to `_CRON_PARAMETERS` to
advertise per-action required fields. OpenAI Codex/Responses rejects
`oneOf`/`anyOf`/`allOf`/`enum`/`not` at the root of function
parameters, so any agent that registers the cron tool now fails to
start with:

    HTTP 400: Invalid schema for function 'cron': schema must have
    type 'object' and not have 'oneOf'/'anyOf'/'allOf'/'enum'/'not'
    at the top level.

Remove the top-level `oneOf`. The original intent of #3125 (stop LLMs
from looping on the #3113 contract mismatch) is preserved by:

  - `validate_params` — runtime-enforces `message` for `action='add'`
    and `job_id` for `action='remove'`
  - field descriptions — each schema field already flags
    "REQUIRED when action='...'" so the LLM sees the contract

The regression test is updated to lock the invariant in the other
direction: the top-level schema must not contain
`oneOf`/`anyOf`/`allOf`/`not`, and the REQUIRED hints must stay on
`message` and `job_id`.

Verified:
  - tests/cron/              70 passed
  - tests/agent/test_loop_cron_timezone.py + tests/providers/  232 passed

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>

2026-04-19 21:54:38 +08:00

..

test_cron_service.py

test: speed up cron and restart timing tests

2026-04-19 12:35:57 +00:00

test_cron_tool_list.py

fix(cron): drop top-level oneOf so OpenAI Codex/Responses accept tool schema

2026-04-19 21:54:38 +08:00

test_cron_tool_schema_contract.py

fix(cron): state per-action requirements in descriptions, keep list/remove callable

2026-04-17 22:52:48 +08:00