Pool type incompatible with kysely 0.29 PostgresDialect (Client.connect signature mismatch)

Summary

Passing Pool from @neondatabase/serverless to kysely's PostgresDialect no longer type-checks after kysely 0.29.

Reproduction

import { Pool } from '@neondatabase/serverless';
import { Kysely, PostgresDialect } from 'kysely';

new Kysely({
  dialect: new PostgresDialect({
    pool: new Pool({ connectionString }),
  }),
});

Error

Type 'Pool' is not assignable to type 'PostgresPool | ((options?: AbortableOperationOptions) => Promise<PostgresPool>)'.
  Type 'Pool' is not assignable to type 'PostgresPool'.
    The types returned by '(new Client(...)).connect()' are incompatible between these types.
      Type 'Promise<void>' is not assignable to type 'Promise<PostgresClient>'.
        Type 'void' is not assignable to type 'PostgresClient'.

Cause

kysely 0.29 (PR #1796) tightened the structural PostgresClient.connect() return type from Promise<void> to Promise<PostgresClient> as groundwork for query cancellation. The Pool.Client exposed by @neondatabase/serverless still has connect(): Promise<void> — which matches the underlying pg API.

Context

• @neondatabase/serverless: 1.1.0
• kysely: 0.29.2
• Neon's own docs still recommend exactly this pattern, so this breaks the recommended setup.
• Kysely maintainers have stated in the past they consider Neon-Pool ↔ PostgresDialect integration out of scope (kysely#1441).

Begin with the TypeScript reproduction using @neondatabase/serverless Pool and Kysely's PostgresDialect. Compare Pool.Client.connect(), Kysely 0.29's PostgresClient expectation, and the referenced Kysely PR, then check Neon's Kysely guide. Done means the recommended setup type-checks with the reported versions without weakening the stated integration contract.