[Bug]: Resuming or replacing a goal requires stopping the thread first #25951

Resuming or replacing an unfinished goal requires me to stop the thread first. Some resume attempts still fail after that extra step. This is the most disruptive problem in these reports.

Reproduction

1. Open a thread with an unfinished goal while another turn is running.
2. Try to resume the goal or replace its objective.
3. Compare the available actions before and after pressing Stop.

The goal action should perform the required transition itself. A separate manual Stop should not be required. The exact error behind the intermittent failed resumes has not been isolated.

Code and release status

#25426 added server handling that stops the active turn when a new goal or /goal resume starts, unless the command is queued. It is in v0.1.4-nightly.20261027.3770 and absent from v0.1.2.

The nightly still has a separate UI restriction: goalNowItem only shows Resume when !isWorking. A browser regression test confirms that a paused goal loses its Resume button during another turn. Removing that condition makes the existing server transition reachable.

The connected server is v0.1.2 on Ubuntu 24.04.5 x86_64. The browser client build and browser version remain unknown. Server version must not be treated as the browser build.

The UI fix addresses the extra Stop step. The intermittent native resume failure remains unconfirmed. #20232 and #22397 describe specific goal errors, but neither error has been established here. Claude's different goal behavior is tracked separately in #25956.

Implementation PR: #26022. The change is proposed and has not shipped.