Matysh a29df12e0b ci: raise the turn limit, bound the run by time instead ...

The r2 spec review on #104 produced a complete green verdict and then failed
on --max-turns 40 at turn 43, so the label step never ran and the transition
had to be reconciled by hand. Forty was a guess; a review that reads SCOPE,
AGENTS, PROCESS, the issue thread and the spec exceeds it routinely, and a
code review that also runs gates needs far more.

The real guard against a runaway run is the job timeout, not the turn count.

Issue: #114
User-Visible: no

2026-08-13 12:37:14 +03:00

..

announce.yml

Release v1.61.0-beta.5 candidate

2026-08-10 18:01:16 +03:00

performance.yml

Release v1.61.0-beta.5 candidate

2026-08-10 18:01:16 +03:00

process.yml

ci: raise the turn limit, bound the run by time instead

2026-08-13 12:37:14 +03:00

publish-prerelease.yml

Release v1.61.0-beta.4 candidate

2026-08-10 14:32:20 +03:00

release-zip.yml

chore(hacs): zip_release + workflow attaching houseplan.zip to every release

2026-08-08 19:43:24 +03:00

release.yml

Release v1.61.0-beta.7 candidate

2026-08-11 02:49:42 +03:00

validate.yml

fix: harden v1.62.0-beta.10 candidate

2026-08-13 00:14:51 +03:00