Match the real-model conformance cadence to the dev/loop velocity so live
regressions and provider drift surface within the hour instead of up to 24h.
The mock harness already runs on every push/PR; this only changes the live
(credentialed) schedule.
Co-authored-by: Claude <noreply@anthropic.com>
* atlascloud: env-selectable chat model; run conformance on a stronger model
The daily provider-conformance harness fails 4/5 harnesses on Atlas Cloud —
its default chat model answers agent/tool-use conformance prompts
conversationally instead of performing the task. Atlas is currently the only
provider with a key configured, so the whole live run is red.
Make the Atlas Cloud provider honor an ATLASCLOUD_MODEL env override (falling
back to the existing default), and set it in the harness workflow to a
stronger tool-use model (Qwen3, overridable via an Actions variable). No
change to the default for normal use.
* atlascloud: use minimaxai/minimax-m3 for conformance model
---------
Co-authored-by: Claude <noreply@anthropic.com>
Asim Aslam