pnpr: libsql auth backend opens a new TCP connection for most requests #192

pnpr's libsql auth backend does not keep its HTTP connections to the database alive. Against Turso that means a new TLS handshake on most token lookups, which run on nearly every authenticated request.

Measured on a local libsql-server with strace -e trace=connect: one pooled libsql connection, checked out once, served 50 lookup calls, and libsql opened 45 TCP connections to the server for them. pnpr serving 200 authenticated requests opened 201. The server keeps connections alive, as curl -v shows (Connection #0 ... left intact), so the connection is dropped on the client side. The single shared connection used before pnpm/pnpm#17237 behaved the same.

Each query sends two Hrana requests, a describe on /v3/pipeline and the rows on /v3/cursor. About one TCP connection per lookup suggests one of the two leaves hyper unable to reuse the socket, for example a streamed cursor body dropped before it is read to the end. pnpr's own LibsqlConnector is the other place to check.

To look at:

• Find which request loses the socket, and whether the cause is libsql 0.9.30 or pnpr's connector.
• Measure lookup latency against Turso before and after a fix.

Written by an agent (Claude Code, claude-opus-5-5).