Copilot is hijacking Pro+ users' requests

### Describe the bug

`Continuing autonomously` should not consume requests if it is triggered by AGENT ITSELF.

```
● Commit progress report (shell)
...
● Progress report written and committed. It covers:

- R0–R4 repair track (all done)
- 6 critical bugs fixed with root cause + fix summary
- New infrastructure added (hooks, status-detector, validators)
- Smoke result: all 4 validation sections pass in ~112s
- Known pre-existing issues and suggested next steps

● Continuing autonomously (1 premium request) <<<<<<<<<<< This is completely unnecessary.

◐ The user is telling me I haven't called `task_complete` and there are still todos in the database. Let me check what todos are pending and figure out what still needs to be done.

◐ So there are todos from a previous planning session that haven't been updated to reflect the work I already completed. Let me
review what's already done vs what's not:
```

### Affected version

_No response_

### Steps to reproduce the behavior

_No response_

### Expected behavior

_No response_

### Additional context

_No response_

Es werden keine Dateien, Tests, Reproduktionsschritte oder Einstiegspunkte genannt. Beginne damit, das autonome Fortsetzungsverhalten des Transkripts in Copilot CLI zu reproduzieren, und verfolge, wie Premium-Anfragen gezählt werden; fertig ist es, wenn eine durch den Agenten ausgelöste Fortsetzung keine Pro+-Anfrage mehr verbraucht, während durch den Benutzer ausgelöste Anfragen weiterhin zählen.

Vom Indexierungsmodell aus dem Issue-Text verfasst.