Web runs from Studio end when the browser visits a custom HTTP endpoint

Running a Web project from Studio that has an HTTP request handler ends the run when the browser visits one of the project's custom HTTP endpoints in the same tab.

Steps: run the bundled HTTP Endpoint Demo from Studio and, as its page instructs, replace the browser address path with /hello?name=Objo. The endpoint reply is served correctly, but a few seconds later the run ends and the application shuts down. The rest of the demo walkthrough — reloading the reply with a different query and using Back to return to the application page — then fails, because the server is gone.

Expected behaviour: after the browser visits a custom endpoint, the run should keep serving both the endpoint and the application page until it is stopped from Studio or the browser session genuinely ends.

Impact: any mixed browser/API Web project loses its Studio run while the user is reading an endpoint response, and the bundled demo's guided walkthrough is broken. Published (deployment) web applications are unaffected; this only affects runs started from the Studio IDE.