feat(sea): type async-execute napi surface + pecotesting e2e

[msrathore-db]

Summary

JS-side typing + live e2e test for the new napi async-execute surface delivered by kernel branch msrathore/krn-async-execute (commit 1957878, PR https://github.com/databricks/databricks-sql-kernel/pull/76).

Plumbing

• SeaNativeLoader.ts — new typed interfaces:

  • SeaNativeStatementStatus — string union mirroring the kernel StatementStatus variant names ('Pending' | 'Running' | 'Succeeded' | 'Failed' | 'Cancelled' | 'Closed' | 'Unknown')
  • SeaNativeAsyncStatement — statementId, status(), awaitResult(), cancel(), close()
  • SeaNativeAsyncResultHandle — statementId, fetchNextBatch(), schema() (no cancel/close — parent owns lifecycle)
  • SeaNativeConnection.submitStatement(sql, options?) method

• native/sea/index.d.ts — mirrors the napi-rs codegen: new AsyncStatement / AsyncResultHandle class declarations + Connection.submitStatement(...) method.

• tests/e2e/sea/async-execute-e2e.test.ts — three live-warehouse cases:

  1. submit → awaitResult → drain 100 rows from range(0, 100); byte-decode the Arrow IPC and assert row count
  2. status() returns a string variant from the kernel enum
  3. cancel() against a still-pending statement (range(0, 100_000_000)) completes within 2s wire-latency budget

Deferred (follow-on PR)

A full SeaAsyncOperationBackend implementing IOperationBackend so DBSQLOperation async-mode flows through the same facade callers use for Thrift. The kernel + napi surface is ready; the facade-level integration is the next increment. This PR ships the kernel→napi→JS shape and locks the behaviour with a live e2e.

ULTRATHINK on async-cancel safety

Kernel's AwaitResultCancelGuard (src/statement/executed_async.rs:305-356) installs an RAII drop hook in await_result() that fires a fire-and-forget cancel_statement if the future is dropped mid-poll. This covers:

• JS Promise.race losers
• AbortController.abort()-driven cancellation
• timeout wrappers (Promise.race([awaitResult(), timer]))
• V8 GC of an orphaned Promise

The napi util::guardedcatch_unwind covers V8 panic-across-boundary on top. The Arc<Mutex<Option<…>>> lock shape in the napi AsyncStatement wrapper matches the existing Connection and Statement so cancel/close queue behind any in-flight awaitResult() until it returns naturally — the kernel handles the drop-the-future case independently.

Cross-repo dependency

Requires kernel branch msrathore/krn-async-execute (PR https://github.com/databricks/databricks-sql-kernel/pull/76). Stacks on msrathore/sea-statement-options (F3 + F4, PR #393).

Test plan

• tsc shows zero new TS errors (14 baseline preserved)
• Tests written against pecotesting env-var gate (skipped when absent)
• Live warehouse run — pending merge of kernel PR so the native binary can be built locally

[msrathore-db]

Re-review requested — F1-F4 stack underneath this PR is now DA-approved at round-3; this PR (F3b NodeJS async-execute) is the next adversarial-review target.

Round-3 final tip:de55b96f268410269c90666921ece6deef7bdff5

This PR was parked behind the F1-F4 quality bar per team-lead's hard-stop directive. With F1-F4 + matrix now in APPROVED FOR MERGE state, F3b adversarial review starts on this PR + the kernel companion (#76).

Findings will be addressed per the same protocol that closed F1-F4 round-1 → round-2 → round-3:

• ground-truth origin state before re-implementing,
• gate exit codes pasted on every fixup notification (eslint, tsc --noEmit, live e2e),
• DA verifies each finding independently in their check-worktree.

DA preview notes on F3b (Q1 IPC encoder lift to bindings_common, Q2 typed-status fallback handling, Q3 progress-UI error-envelope path, Q4 keep AsyncResultHandle without close, Q5 soften throughput claim, Q6 facade-integration deferral) are stashed for the formal review.

Co-authored-by: Isaac

[msrathore-db]

Superseded by #406, which implements the async submit+poll lifecycle (Thrift runAsync parity) on top of the params/intervals/getInfo base (#403). This PR only typed the napi async surface on the earlier M0 backend and did not wire SeaSessionBackend.executeStatement / SeaOperationBackend to actually submit-and-poll. The typed surface and the live-cancel behaviour are both covered in #406. Closing in favour of #406.