[SEA-NodeJS] rename misses from thorough review: use_sea→use_kernel, README SeaNativeLoader→KernelNativeLoader

Caught by a file-by-file pass (not grep-pattern matching):
- use_sea (snake_case Python flag) in 2 comments → use_kernel (matches the Python
  connector renamed flag); the camelCase useSEA sed had missed snake_case.
- native/kernel/README.md referenced SeaNativeLoader → KernelNativeLoader (the
  README is a committed doc, not regenerated by build:native).

Co-authored-by: Isaac
Signed-off-by: Madhavendra Rathore <madhavendra.rathore@databricks.com>

Author: msrathore-db

lib/DBSQLClient.ts

@@ -628,7 +628,7 @@ export default class DBSQLClient extends EventEmitter implements IDBSQLClient, I
     this.connectionProvider = this.createConnectionProvider(options);
 
     // M0: `useKernel` is consumed via a non-exported internal-options cast so it
-    // doesn't ship in the public `.d.ts`. Mirrors Python's `kwargs.get("use_sea")`
+    // doesn't ship in the public `.d.ts`. Mirrors Python's `kwargs.get("use_kernel")`
     // pattern (see databricks-sql-python/src/databricks/sql/session.py).
     const internalOptions = options as ConnectionOptions & InternalConnectionOptions;
     const backend = internalOptions.useKernel

lib/contracts/InternalConnectionOptions.ts

@@ -2,8 +2,8 @@
  * Internal, non-exported extension of `ConnectionOptions`. Carries M0-only
  * flags that should not appear in the published `.d.ts`.
  *
- * Matches the Python connector pattern: there, `use_sea` is consumed via
- * `kwargs.get("use_sea", False)` and is intentionally absent from the typed
+ * Matches the Python connector pattern: there, `use_kernel` is consumed via
+ * `kwargs.get("use_kernel", False)` and is intentionally absent from the typed
  * signature (see `databricks-sql-python/src/databricks/sql/session.py`).
  *
  * Callers cast `ConnectionOptions` to this type *only* at the read site

native/kernel/README.md

@@ -1,4 +1,4 @@
-# `native/sea/` — consumer-side directory for the Rust napi binding
+# `native/kernel/` — consumer-side directory for the Rust napi binding
 
 **The Rust binding source lives in the kernel repo** at
 `databricks-sql-kernel/napi/`. Building it requires a local checkout
@@ -27,7 +27,7 @@ and reintroduce the same clash. Standalone-workspace is the fix.
 
 ## What lives in this directory
 
-- `index.d.ts` — TypeScript declarations consumed by `lib/sea/`.
+- `index.d.ts` — TypeScript declarations consumed by `lib/kernel/`.
   Generated by napi-rs from the Rust source; checked in as the
   consumer-facing type contract.
 - `index.js` — napi-rs's per-platform router shim. Gitignored;
@@ -57,7 +57,7 @@ nodejs repo.
 
 At release time the kernel's CI publishes
 `@databricks/databricks-sql-kernel-<triple>` npm packages — one per supported
-platform — each containing a single `.node` binary. `native/sea/index.js`
+platform — each containing a single `.node` binary. `native/kernel/index.js`
 (the napi-rs router) `require()`s the package matching the consumer's
 `process.platform` / `process.arch` at load time.
 
@@ -77,7 +77,7 @@ M0 targets a **single** triple: **`linux-x64-gnu`** (package
 `@databricks/databricks-sql-kernel-linux-x64-gnu`, once published).
 
 On every other platform (macOS, Windows, linux-arm64, linux-x64-musl
-/ Alpine, …) the SEA binding is simply absent: `SeaNativeLoader`
+/ Alpine, …) the kernel binding is simply absent: `KernelNativeLoader`
 returns `undefined` from `tryGet()` / throws a structured
 `MODULE_NOT_FOUND` hint from `get()`, and the driver continues to use
 the Thrift backend exclusively. This is expected, not a regression —