diff --git a/KERNEL_REV b/KERNEL_REV
index 65457d79..5315ee8b 100644
--- a/KERNEL_REV
+++ b/KERNEL_REV
@@ -1 +1 @@
-80b68e1eef3b613910183a50dfa4dace854d50dd
+9c2e2378f9a0bcee7d2750371392c07cac38fc3d
diff --git a/native/sea/index.d.ts b/native/sea/index.d.ts
index f8105ff6..2829489c 100644
--- a/native/sea/index.d.ts
+++ b/native/sea/index.d.ts
@@ -332,6 +332,34 @@ export interface ConnectionOptions {
    *   `User-Agent` entry here.
    */
   customHeaders?: Array<HeaderEntry>
+  /**
+   * Retry/backoff tuning — all optional. An unset field keeps the kernel's
+   * built-in policy (1s/60s exponential backoff, 6 total attempts, 900s
+   * budget). Mirrors the pyo3 binding's `retry_*` kwargs so the Node.js
+   * driver can forward the same retry knobs the Python connector does.
+   *
+   * Lower bound of the exponential backoff (also clamps a server
+   * `Retry-After`). Maps onto [`HttpConfig::retry_min_wait`].
+   */
+  retryMinWaitSecs?: number
+  /**
+   * Upper bound of the exponential backoff. Maps onto
+   * [`HttpConfig::retry_max_wait`].
+   */
+  retryMaxWaitSecs?: number
+  /**
+   * **Total** number of attempts (matching the connector's
+   * `_retry_stop_after_attempts_count` and JDBC count semantics). The
+   * kernel's [`HttpConfig::retry_max_retries`] counts retries *after* the
+   * first attempt, so this is converted with `max(0, attempts - 1)` in
+   * [`build_http_config`] — `0` / `1` both mean a single attempt, no retry.
+   */
+  retryMaxAttempts?: number
+  /**
+   * Overall retry budget in whole seconds. Maps onto
+   * [`HttpConfig::overall_timeout`].
+   */
+  retryOverallTimeoutSecs?: number
 }
 /**
  * Open a Databricks SQL session and return an opaque `Connection`
@@ -505,6 +533,17 @@ export declare class AsyncStatement {
    * that only need the state name.
    */
   status(): Promise<string>
+  /** Rows modified by the statement (UPDATE / INSERT / DELETE / MERGE). */
+  numModifiedRows(): Promise<number | null>
+  /**
+   * Server-supplied user-facing message (may contain SQL fragments —
+   * redact before centralised logging).
+   */
+  displayMessage(): Promise<string | null>
+  /** Server-supplied diagnostic detail. */
+  diagnosticInfo(): Promise<string | null>
+  /** Server-supplied structured error detail (JSON), when enabled. */
+  errorDetailsJson(): Promise<string | null>
   /**
    * Block until the server reaches a terminal state, then return
    * an `AsyncResultHandle` that wraps the materialised result