Base commit: ad79bbb5ec909524f8f281e62d860c588a86f332
Revision rerun command:
pnpm exec turbo run test --filter=@bb/provider-bridge-acp -- --run -t "keeps the dynamic-tool TCP server alive"

Observed output:
acp bridge: built "bb-bridge" session MCP config for thread "thread-1" (1 tools)
acp bridge: "bb-bridge" answered initialize for thread "thread-1" (1 tools)

FAIL |@bb/provider-bridge-acp:isolated| src/bridge/bridge.test.ts > acp bridge > keeps the dynamic-tool TCP server alive after a client reset on initialize
AssertionError: expected [ Error: write ECONNRESET { …(3) } ] to deeply equal []

- Expected
+ Received

- []
+ [
+   Error {
+     "message": "write ECONNRESET",
+     "errno": -104,
+     "code": "ECONNRESET",
+     "syscall": "write",
+   },
+ ]

Test Files  1 failed | 16 skipped (17)
Tests       1 failed | 288 skipped (289)
Tasks       1 successful, 2 total

Normal Linux initialize-path check:
pnpm exec turbo run test --filter=@bb/provider-bridge-acp -- --run -t "advertises an MCP server command that answers MCP initialize"

Observed output:
[bridge] acp bridge: built "bb-bridge" session MCP config for thread "thread-1918" (1 tools)
[bridge] acp bridge: "bb-bridge" answered initialize for thread "thread-1918" (1 tools)
✓ advertises an MCP server command that answers MCP initialize when the bridge runs under the bootstrap

Test Files  1 passed | 16 skipped (17)
Tests       1 passed | 288 skipped (289)
Tasks       2 successful, 2 total

This normal Linux path did not produce a socket reset. The forced reset above reproduced the accepted-socket fault.