Under the hood
Async REPL's queue-depth limit logic moved to a new internal function, same behavior
What
The check that rejects a new asynchronous REPL (code execution) request when too many evaluations are already queued or running, along with its "async REPL dispatch rejected" message, was moved into a new internal function that is now invoked through the call.runEngine execution path. The wording and the logic itself are unchanged.
Why
This is a code relocation tied to the broader REPL tool restructuring in this release, with no change in behavior: the same queue-depth limit still applies.