Feature request: Remove stop hook suppression.

[KJ7LNW]

Certain cases like rate limiting and five hour or weekly usage limits now suppress stop hook triggers.

They used to work in 2.1.50, and they no longer work in 2.1.101: This means stop hooks are no longer capable of detecting a problem and delaying with reasonably appropriate retry.

In the hourly limit case, it was capable of sleeping until the limit was done. In the rate limit case, it could just back off a few minutes at a time to retry and wait until it's done being rate limited.

eg:

  {                                                           
     "hook_event_name" : "Stop",                                                                                     
     "last_assistant_message" : "You've hit your limit · resets 8pm (America/Los_Angeles)",
     "permission_mode" : "acceptEdits",                                                                            
     "stop_hook_active" : false                                                                                      
  }        

or, eg "API Error: Request rejected (429) · Rate limited"

But now it doesn't trigger the stop hook at all.

I'm guessing there's just an early return gate for certain conditions like this that's probably trivial to clear.

[KJ7LNW]

It turns out StopFailure is the hook that triggers this now, but its responses are ignored.

If you could trivially route StopFailure to Stop's handler so it respects the block:message response---or route StopFailure's response so it is respected like any other hook (block:msg, continue:bool, etc) then that would also solve the problem.

Ultimately the goal is to get control of interactive response on an API failure.