Two things from stopping one by hand.
── It restarted itself ──
Pressing stop produced the exit notification, and the agent read that as a crash:
it brought the server back up, then wrote three paragraphs theorising that
"something outside this conversation sent that SIGTERM" and counting it as the
third external touch on the repo today.
It was not wrong about the signal. It could not have been right about the cause,
because the stop button did not exist when the preamble was written, and the
preamble said only "report" — leaving what to do with an exit entirely open.
So it now says: on exit, one line, and STOP. Do not restart. Do not diagnose. Do
not theorise about what else on the machine might have touched it. A job I stopped
that comes back on its own is the opposite of a stop button — and an exit is at
least as likely to be me as a failure now that pressing a button is how you end
one.
Deliberately not written as "ignore exit code 143": the phrasing is about intent,
not signal numbers, so it holds whether the job dies by SIGTERM, SIGKILL or its
own hand.
── Stop, labelled, in the expanded panel ──
The chip keeps its icon; the panel gets a bordered button that says "Stop". The
panel is where you go to decide whether something should keep running, and the
control that ends it should not be a glyph you have to hover to identify. Both
appear only while the task is running.
tsgo clean, frontend builds, 851 pass / 7 fail unchanged.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
pastilhasandClaude Opus 5
1a9b162615