Rate Limiting: Stop Interrupting the Task Flow!

### Describe the bug

When I run commands using `/fleet`, I occasionally encounter rate limiting. Is it really that difficult to avoid abruptly interrupting the workflow? Couldn't you just implement a client-side `sleep` or a "retry after x seconds" mechanism? Instead, you just cut off the entire process?!

### Affected version

_No response_

### Steps to reproduce the behavior

_No response_

### Expected behavior

_No response_

### Additional context

_No response_

Start at the /fleet command entry point and trace how rate-limit responses are handled when a task is running. Reproduce the interruption if possible, then compare the behavior with the requested retry-after or client-side delay. Done means rate limiting no longer abruptly cuts off the /fleet workflow.

Scritto dal modello di indicizzazione a partire dal testo della issue.