Fixed
run_timeout_seconds can now be disabled. v1.2.0 documented max_turns: off but had no equivalent for the model run timeout, so a consumer wanting an
uncapped review could only raise the number, never lift it. off, none,
false, disabled, and 0 are now accepted and leave the run unbounded — the
same vocabulary max_turns already used.
Consumers pinning v1.2.0 and passing run_timeout_seconds: off were falling
back to the 600-second default rather than running uncapped. Repin to this tag
if you rely on that.
Note on lifting the cap
elek normally reports a failure review shortly before its own run timeout so the
tracking comment is not left stale. With the timeout disabled there is nothing
for it to fire ahead of, so a wedged run is ended by the outer GitHub job
ceiling instead, and that path does leave the tracking comment behind. Worth
keeping a job-level timeout-minutes if a stale comment matters more than an
uncapped review.