Name the frames of the Bun 1.3.14 main-thread segfault from #3708, then move or keep the pinned Bun #3804

Later: It needs a person to open bun.report, which no crew run can reach; until someone does, the pin keeps the runtime still.

Split from #3726. The crash report link in #3708 (bun.report, Bun 1.3.14, panic(main thread): Segmentation fault at address 0x0, RSS 3.53 GB after ~21 min) can only be opened outside a crew run: the run's network proxy refuses bun.report and api.github.com. Two crew runs declined for that reason.

Done:

• [ ] A person opens the link and comments the main-thread frames here: Bun.spawn, a socket, sqlite or the HTTP server.
• [ ] Then a builder either moves the pinned oven/bun line, from the pin issue, to the release that fixes it, or files it upstream with the report link and the load that preceded it (255 socat, 148 bwrap, 81 bun, 10 claude in the pod), and links it here.