fix(server): release SSE streams when a Bun client disconnects - #44341

AI code review — automated review for reference, author can ignore or act on any point.

Well-scoped workaround for a nasty class of leak — hooking "aborted" and destroying the response to force Bun's missing "close" is the least invasive fix available, the comment citing the upstream issue (packages/core/src/util/http-server.ts:30-37) is much appreciated, and the process.versions.bun gate keeps Node/Electron behavior byte-identical. Both production listeners are wired (packages/cli/src/commands/handlers/serve.ts:43, packages/opencode/src/server/server.ts:201), and the tests use real sockets including the negative case (packages/core/test/util/http-server.test.ts:68-110). Two notes:

1. Residual leak for silent disconnects. "aborted" fires on an explicit client teardown of the request, but a peer that vanishes without FIN/RST (laptop sleep, NAT drop) emits nothing, so those SSE streams still accumulate until the next response.write() fails. Periodic SSE heartbeats would self-heal this; otherwise worth adding one line to the doc comment acknowledging the bridge only covers the explicit-abort case, so future readers don't assume it's total.

2. Coverage check on other servers. packages/stats/server/src/server.ts also builds a node:http server that runs under whatever runtime hosts it — if any of its routes are long-lived/streaming, it needs bridgeClientDisconnect too; if everything is short-request/response, fine as-is. (The WSL sidecar uses node:net, so it's unaffected.)

Minor: the writableEnded/destroyed check at http-server.ts:42 has an inherent TOCTOU window against concurrent end(), but destroying an ended response is harmless — no action needed.

Automated PR Cleanup

Thank you for contributing to opencode.

Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions.

This PR was closed because it matched the following cleanup criteria:

• The PR was created more than 1 month ago
• The PR had fewer than 2 positive reactions
• Positive reactions are counted as thumbs-up, heart, celebration, or rocket reactions on the PR

PRs created within the last month are not affected by this cleanup.

If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate.

Thanks again for taking the time to contribute.