SurrealDB client read timeout leaves server-side query running

I need to determine whether a SurrealDB client timeout aborts the corresponding server-side query execution or only closes the client connection while the server continues processing. SurrealQL supports CANCEL TRANSACTION for explicit multi-statement transactions, but there is no confirmed standalone statement for cancelling an arbitrary long-running non-transactional query. SDKs expose connection and request timeout settings, yet flag names, defaults, and units vary by language and SurrealDB version.

Because the research does not confirm whether a client-side deadline instructs the server to stop work, I need to clarify the cancellation boundary before relying on timeouts for long-running queries.

• Does a SurrealDB client read or request timeout propagate to the server and abort the active query?
• If the server continues execution after client disconnect, what server-side mechanism can cancel the query?
• Which SurrealDB version and SDK timeout settings govern this behavior?