Permission-negotiation ordering fix: abort now takes priority over the 'session committed' hang

When Claude Code decides whether to run a tool, there's a shared internal check for whether the session has already been "committed" to an answer; if so, it used to return a promise that never resolves, effectively hanging that path. Previously, the abort (cancel) path used a differently named function for this, and the order of checks meant a cancellation could still get caught by the "already committed" hang. Now both the abort path and the normal path use the same function, and the check for an abort signal runs before the "already committed" check.