[SEA-NodeJS] (4/8) PAT auth via useSEA: true

[msrathore-db]

Stack

Linear stack of 8 PRs landing the M0 + M1 Phase 1 SEA NodeJS work. Merge in order from base ↑ to tip. The tip branch (msrathore/sea-auth-u2m, PR #383) is the single snapshot containing everything in flight — point your test or benchmark harness at it for an end-to-end check.

Pos	PR	Branch	Scope
1/8	#378	sea-abstraction	IBackend / ISessionBackend / IOperationBackend interfaces
2/8	#380	sea-napi-binding	TS loader + build script for the kernel-provided .node artifact
3/8	#377	sea-errors-logging	Kernel ErrorCode → JS error-class mapping (M0 minimum)
4/8	#379	sea-auth	PAT auth via useSEA: true
5/8	#382	sea-execution	executeStatement + openSession (sessionConfig, initialCatalog/Schema)
6/8	#381	sea-results	CloudFetch + Inline Arrow result fetching
7/8	#384	sea-operation	cancel / close / finished lifecycle + INTERVAL parity + napi-relocation acceptance (absorbed sea-integration content)
8/8	#383	sea-auth-u2m ← TIP	M1 Phase 1 OAuth M2M + U2M (5 review rounds, ZERO HIGH at close)

Companion kernel stack (databricks/databricks-sql-kernel): 8 PRs — root #26 (async-public-api) → #27 → #25 → #29 → #28 → #30 → #24 → #23 (tip).

Policy: new PRs always stack on the current tip. No sibling/parallel topology. No force-pushes on existing PRs unless absolutely necessary; if a PR's content is wrong, add a fix-up commit on top of the stack tip rather than rewriting history.

---

This PR is position 4/8.

Summary

Wires the PAT auth path through the napi binding. useSEA: true on DBSQLClient.connect() routes openSession via the kernel; M0 e2e at 327ms vs pecotesting.

Extended in #383 (M1 Phase 1 OAuth) with OAuth M2M + U2M via a discriminated AuthMode union.

Draft until you give the go for review.

Tracking

• PECOBLR-2666 — NodeJS SEA integration (parent epic — M0 PAT auth baseline)

Co-authored-by: Isaac

[github-actions]

Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase (git rebase -i main).

[github-actions]

Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase (git rebase -i main).

[github-actions]

Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase (git rebase -i main).