feat(chat): explain a turn-limit stop instead of reporting it as a failure - #63

Open

zaytcevcom wants to merge 14 commits into

mainfrom

duck/-5362116338/explain-turn-limit-stop

Commits on Jul 27, 2026

refactor(chat): pass run limits into the terminal renderer
zaytcevcom
committed
bd4bf06
feat(chat): explain a turn-limit stop with the knob and its current value
zaytcevcom
committed
8c8c3e2
feat(config): name the turn-limit env var for the terminal message
zaytcevcom
committed
0d738bb
feat(bot): wire the turn-limit knob name into the chat service
zaytcevcom
committed
e889b4d
test(chat): assert the delivered turn-limit message carries the runtime cap
zaytcevcom
committed
139f4eb
fix(chat): render the turn count only when it corroborates the cap
zaytcevcom
committed
2cf0412
fix(chat): stop reporting a turn-limit stop as a failure
zaytcevcom
committed
d419928
fix(chat): say whose limit bound a run with no configured cap
zaytcevcom
committed
36e4421
fix(chat): stop echoing the provider's turn-limit boilerplate
zaytcevcom
committed
5870c63
docs(chat): correct why the turn-limit message keeps the raw subtype
zaytcevcom
committed
b57a425
test(chat): check the turn-limit message as a code span, not a stage line
zaytcevcom
committed
ad88263
test(airunner): pin the turn-cap knob to what providers actually enforce
zaytcevcom
committed
488d653
test: close the gaps the previous round's test hardening left
zaytcevcom
committed
15f3fc1
test(chat): pin the notice wording when a stop lands after a turn-limit result
zaytcevcom
committed
03537f2