jincheng-xydt 356a199bd4 fix: default cron runMode to "due" instead of "force" (#94270) (#94453) ...

* fix: default cron runMode to 'due' instead of 'force'

When the runMode parameter is omitted from a cron 'run' action,
the default value now respects schedule guards ('due') instead
of bypassing them ('force'). This prevents unintended execution
of scheduled jobs outside their configured time windows.

Fixes #94270

Co-Authored-By: Claude <noreply@anthropic.com>

* test: update runMode expectations for default 'due' (#94270)

* ci: trigger re-evaluation of real behavior proof

* fix(cron): document due-by-default agent runs

Signed-off-by: sallyom <somalley@redhat.com>

---------

Signed-off-by: sallyom <somalley@redhat.com>
Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: sallyom <somalley@redhat.com>

2026-06-18 23:53:17 -04:00

..

agents/prompt-snapshots

fix: default cron runMode to "due" instead of "force" (#94270) (#94453)

2026-06-18 23:53:17 -04:00

child-process-bridge

…

hooks-install

…

plugins-install

…

ts-topology/basic

docs: document test helpers

2026-06-04 20:42:26 -04:00

cli-startup-bench.json

…

exec-allowlist-shell-parser-parity.json

…

exec-wrapper-resolution-parity.json

…

plugin-extension-import-boundary-inventory.json

…

system-run-approval-binding-contract.json

…

system-run-approval-mismatch-contract.json

…

system-run-command-contract.json

…

talk-config-contract.json

…