An instruction to keep improving can turn a bounded task into an endless process. Define what the system must produce and how it can tell that the work is complete.

Set limits on time, spend and retries. Decide what evidence to preserve when a limit is reached, and tell the user which parts remain unfinished. A failed attempt can still leave a useful draft, but it should not be labeled complete.

For actions with real consequences, distinguish preparing a change from executing it. The stopping point may be a reviewable proposal rather than an automatically published result.