fix(sea): align napi package name to @databricks/databricks-sql-kernel-*

Same alignment as the logging PR: kernel #131/#135 renamed the published napi
package @databricks/sql-kernel -> @databricks/databricks-sql-kernel. Update the
packaging test, version-test hint, SeaNativeLoader install hint, and README to
match the regenerated router, fixing the native-packaging unit tests under the
KERNEL_REV bump to kernel main 80b68e1.

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

Author: msrathore-db

lib/sea/SeaNativeLoader.ts

@@ -17,7 +17,7 @@
  *
  * Mirrors the load-failure-tolerant pattern of `lib/utils/lz4.ts`: the
  * `.node` artifact ships via per-platform optional dependencies
- * (`@databricks/sql-kernel-<triple>`), so its absence must not crash
+ * (`@databricks/databricks-sql-kernel-<triple>`), so its absence must not crash
  * a Thrift-only consumer of the driver. Callers that actually need
  * SEA construct a {@link SeaNativeLoader} (or use the process-global
  * {@link getSeaNative}) which throws a structured error if the binding
@@ -104,7 +104,7 @@ function loadFailureHint(err: NodeJS.ErrnoException): string {
   // not the bare `${platform}` shown here, so a literal example would
   // 404. Point at the README's supported-triple list instead.
   const installHint =
-    'Install the matching @databricks/sql-kernel-* optional dependency for your platform ' +
+    'Install the matching @databricks/databricks-sql-kernel-* optional dependency for your platform ' +
     '(see native/sea/README.md for the supported triples; M0 ships linux-x64-gnu only).';
   if (err.code === 'MODULE_NOT_FOUND') {
     return `SEA native binding not installed for platform ${platform} on Node ${process.version}. ${installHint}`;

native/sea/README.md

@@ -3,7 +3,7 @@
 **The Rust binding source lives in the kernel repo** at
 `databricks-sql-kernel/napi/`. Building it requires a local checkout
 of that repo — see "Build for local dev" below. The published npm
-package is `@databricks/sql-kernel-<triple>`.
+package is `@databricks/databricks-sql-kernel-<triple>`.
 
 ## Workspace topology
 
@@ -33,10 +33,10 @@ and reintroduce the same clash. Standalone-workspace is the fix.
 - `index.js` — napi-rs's per-platform router shim. Gitignored;
   populated by `npm run build:native` for local dev. In published
   tarballs it ships alongside the `.d.ts` and `require()`s the
-  right `@databricks/sql-kernel-<triple>` optional dependency.
+  right `@databricks/databricks-sql-kernel-<triple>` optional dependency.
 - `index.*.node` — the actual native binary, one per platform.
   Gitignored. In production these live in the per-triple optional
-  dependencies (`@databricks/sql-kernel-linux-x64-gnu`, etc.); for
+  dependencies (`@databricks/databricks-sql-kernel-linux-x64-gnu`, etc.); for
   local dev `npm run build:native` copies one into this directory.
 
 ## Build for local dev
@@ -56,7 +56,7 @@ nodejs repo.
 ## Production load path
 
 At release time the kernel's CI publishes
-`@databricks/sql-kernel-<triple>` npm packages — one per supported
+`@databricks/databricks-sql-kernel-<triple>` npm packages — one per supported
 platform — each containing a single `.node` binary. `native/sea/index.js`
 (the napi-rs router) `require()`s the package matching the consumer's
 `process.platform` / `process.arch` at load time.
@@ -68,13 +68,13 @@ platform — each containing a single `.node` binary. `native/sea/index.js`
 > unpublished package would break every install.) Until they ship, the
 > binding is produced locally via `npm run build:native` (which copies
 > `index.<triple>.node` into this directory). Once the packages are
-> published, add `@databricks/sql-kernel-<triple>` back to
+> published, add `@databricks/databricks-sql-kernel-<triple>` back to
 > `optionalDependencies` — npm then installs only the matching one.
 
 ## Supported platforms (M0)
 
 M0 targets a **single** triple: **`linux-x64-gnu`** (package
-`@databricks/sql-kernel-linux-x64-gnu`, once published).
+`@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`
@@ -86,9 +86,9 @@ CI starts publishing them in later milestones.
 
 ## Supply-chain note
 
-The unpublished triple names (`@databricks/sql-kernel-darwin-arm64`,
+The unpublished triple names (`@databricks/databricks-sql-kernel-darwin-arm64`,
 `…-win32-x64-msvc`, etc.) referenced by the router are **not**
 squat-able: `@databricks` is a Databricks-owned npm scope, and npm
 only allows org members to publish under a scope it owns. A third
-party therefore cannot register `@databricks/sql-kernel-*` and have
+party therefore cannot register `@databricks/databricks-sql-kernel-*` and have
 the router autoload it. No placeholder packages are required.

tests/unit/sea/native-packaging.test.ts

@@ -21,7 +21,7 @@ import { join } from 'path';
 // (e.g. `@databricks/sea-native-linux-x64-gnu-darwin-arm64`, and the doubled
 // `@databricks/sea-native-linux-x64-gnu-linux-x64-gnu`), so a published
 // install would never resolve a `.node`. The canonical name is
-// `@databricks/sql-kernel-<triple>` (see native/sea/README.md and the
+// `@databricks/databricks-sql-kernel-<triple>` (see native/sea/README.md and the
 // SeaNativeLoader load-failure hint).
 describe('SEA native binding — packaging (native/sea/index.js)', () => {
   // Resolved from the repo root (the cwd for `npm test`) so the test does not
@@ -35,8 +35,8 @@ describe('SEA native binding — packaging (native/sea/index.js)', () => {
     expect(required.length, 'no @databricks/* require() found in the router').to.be.greaterThan(0);
   });
 
-  it('every npm fallback uses the canonical @databricks/sql-kernel-<triple> name', () => {
-    const triple = /^@databricks\/sql-kernel-[a-z0-9]+(-[a-z0-9]+)*$/;
+  it('every npm fallback uses the canonical @databricks/databricks-sql-kernel-<triple> name', () => {
+    const triple = /^@databricks\/databricks-sql-kernel-[a-z0-9]+(-[a-z0-9]+)*$/;
     for (const name of required) {
       expect(name, `unexpected SEA native package name: ${name}`).to.match(triple);
     }
@@ -47,9 +47,9 @@ describe('SEA native binding — packaging (native/sea/index.js)', () => {
     expect(indexJs, 'router still doubles the linux-x64-gnu triple').to.not.contain('linux-x64-gnu-linux-x64-gnu');
   });
 
-  it('resolves the M0 linux-x64-gnu triple to @databricks/sql-kernel-linux-x64-gnu', () => {
+  it('resolves the M0 linux-x64-gnu triple to @databricks/databricks-sql-kernel-linux-x64-gnu', () => {
     expect(required, 'M0 supported triple package missing from the router').to.include(
-      '@databricks/sql-kernel-linux-x64-gnu',
+      '@databricks/databricks-sql-kernel-linux-x64-gnu',
     );
   });
 });

tests/unit/sea/version.test.ts

@@ -16,7 +16,7 @@ import { expect } from 'chai';
 import { tryGetSeaNative } from '../../../lib/sea/SeaNativeLoader';
 
 // Fail loudly only when the binding is actually expected to be present —
-// i.e. a CI step has provisioned it (a published `@databricks/sql-kernel-*`
+// i.e. a CI step has provisioned it (a published `@databricks/databricks-sql-kernel-*`
 // optional dep installed, or `npm run build:native` was run) and opts in via
 // `SEA_NATIVE_EXPECTED=1`. A missing binding there is a real packaging / build
 // regression that a silent skip would mask.
@@ -37,7 +37,7 @@ describe('SEA native binding — smoke test', function smoke() {
       it('fails loudly: the binding must load on the linux-x64 CI runner', () => {
         expect.fail(
           'SEA native binding failed to load on a linux-x64 CI runner where ' +
-            '@databricks/sql-kernel-linux-x64-gnu is expected. Run `npm run build:native` or check packaging.',
+            '@databricks/databricks-sql-kernel-linux-x64-gnu is expected. Run `npm run build:native` or check packaging.',
         );
       });
       return;