fix(stream): add logging to empty catch blocks in stream error handling

[chirag127]

Summary

Replaces silent empty catch blocks with contextual logging across the stream subsystem, and externalizes sql.js in next.config.mjs to suppress build warnings.

Scope note (maintainer edit): this PR is scoped to logging hygiene only. Two unrelated hunks that had ended up on this branch (a targetExhaustion.ts 401 auth-exhaustion change and a modelFamilyFallback.ts candidate-skip change, tracked separately as #8133 and #8134) have been reverted back to the release baseline here so this PR stays focused and doesn't carry a regression the other two changes introduced against tests/unit/kiro-claude-sonnet-5-2267.test.ts. Those two changes should be proposed in their own PR(s).

Changes

open-sse/utils/stream.ts

• Log errors in onComplete callbacks (lines 929, 1112, 2451, 2567, 2723)
• Log errors in onFailure callbacks (lines 929, 1112, 2542)
• All logging uses console.debug with [STREAM] prefix and model context

open-sse/utils/streamHandler.ts

• Log trackPendingRequest decrement failures (line 249)
• Log onError callback failures (line 336)
• Log stall watchdog triple-catch failures (lines 667, 673, 677)
• Add comments to intentional controller.close() catches (lines 537, 546, 558)

open-sse/executors/cursor.ts

• Log KV blob write failures (lines 431, 438)
• Log exec server event write failures (line 461, 517)
• Add comments to intentional H2 lifecycle catches (lines 837, 861, 869, 917, 1007)

next.config.mjs

• Add sql.js to serverExternalPackages to suppress 20+ build warnings

src/lib/db/adapters/sqljsAdapter.ts

• Use a dynamic "sql.js" + "/package.json" expression instead of a static resolve string, so Next's static analysis stops flagging an unresolvable sql.js/package.json build warning (fix(dependencies): sqljsAdapter build warning "Can't resolve sql.js/package.json" #8135)

Issues Fixed

• Closes fix(stream): silent error swallowing in onComplete/onFailure callbacks in stream.ts #8138 (stream.ts onComplete/onFailure silent swallowing)
• Closes test(stream): missing integration test for stall watchdog in pipeWithDisconnect #8139 (streamHandler.ts empty catches)
• Closes test(stream): missing test for earlyStreamKeepalive cleanup on client disconnect #8140 (cursor.ts stream path catches)
• Closes fix(streamHandler): pending request counter drift on trackPendingRequest failure #8141 (pending request counter drift)
• Refs refactor(stream): document intentional empty catches vs ones needing logging #8142 — this PR only documents/logs the catches in the 3 files above (5 of the ~38+ empty catches tracked by refactor(stream): document intentional empty catches vs ones needing logging #8142); the rest of that issue remains open

Testing

• npm run typecheck:core passes
• ESLint passes on all modified files
• Prettier formatting applied
• No behavioral changes in the logging-hygiene hunks -- only logging/comments added to existing catch blocks
• Added tests/unit/stream-handler-catch-logging-8143.test.ts: regression guard proving the stall-watchdog's handleError catch now logs via console.debug instead of silently swallowing
• tests/unit/kiro-claude-sonnet-5-2267.test.ts passes (was regressed by the now-reverted modelFamilyFallback.ts hunk; confirmed green after the revert)

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a8be93402f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Scope 401 exhaustion to the failed connection

When a combo has multiple active accounts for the same non-per-model provider, a single expired or invalid account can return 401 here and exhaustedProviders.add(provider) will cause every later target for that provider to be skipped for the rest of the request, including targets with different connectionIds that still have valid credentials. The comment says this is for “all accounts” being unavailable, but the predicate only checks the status/provider; scope the 401 to exhaustedConnections when a connection is known, or only provider-exhaust after proving all accounts are unavailable.

AGENTS.md reference: open-sse/services/AGENTS.md:L11-L13

Useful? React with 👍 / 👎.

[diegosouzapw]

Thanks, @chirag127! 🙏 Merged the logging-hygiene scope (console.debug on the stream-subsystem empty catch blocks + sql.js externalize). Dropped the two undisclosed behavioral hunks that were out of scope — the #8133 401 auth-exhaustion branch and the #8134 family-fallback filter (which regressed kiro-claude-sonnet-5-2267). Rebaselined stream.ts file-size for the legitimate logging own-growth. If you'd like the #8133/#8134 changes, please resubmit them as separately-tested PRs.