Unclear Which control-request types are actually routed through the new generic dispatch path is not specified.
The loop that processes control requests (internal commands like interrupting a session, ending it, or changing its model or permission mode) now first checks whether a request matches a new generic dispatch path, optionally replying immediately through a callback, before falling back to the existing hardcoded checks for specific request types such as interrupt, end_session, initialize, set_permission_mode, set_model, and set_cwd.
This adds a general-purpose route for handling control requests ahead of the older per-type checks, likely making it easier to add new control-request types without extending the hardcoded chain, though the finding doesn't specify which requests currently take this new path.
Which control-request types are actually routed through the new generic dispatch path is not specified.