it just doesn't want to stop

## Problem

when it's processing something you sent and preparing for response or in middle of response and you stop it, it shows it stopped, but few moments later it continues typing or editing files.

The report names no files, tests, or entry points. Start by reproducing the stop action while a response or file edit is in progress, then trace the relevant Amazon Q processing flow. Done means stopping reliably prevents later typing or file edits.

Written by the indexing model from the issue text.