chore: add changeset for Jupyter Unix socket isolation

[devin-ai-integration]

Summary

Adds a patch changeset for @e2b/code-interpreter-template covering #343, which moved Jupyter's HTTP API, kernel WebSockets, and interrupts to the private Unix socket /run/e2b-jupyter/server.sock (mode 0600) so they are no longer reachable over the sandbox network interface.

Link to Devin session: https://app.devin.ai/sessions/e06e659bfe2e49bd91a54409a5e06c32
Open in Devin Desktop: https://app.devin.ai/desktop/session/e06e659bfe2e49bd91a54409a5e06c32?variant=devin
Requested by: @mishushakov

[devin-ai-integration]

I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".

• Disable automatic comment, CI, and merge conflict monitoring

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-07T12:15:22.483542Z	014dca2	Draft marked ready

ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[claude]

Looks good, straightforward changeset addition. What was reviewed: the single new file .changeset/jupyter-unix-socket.md, confirming it's a well-formed changeset (correct package name, patch bump, and a description consistent with the referenced PR #343) with no code changes to evaluate.

Extended reasoning...

The diff adds only one file, a changeset markdown note for @ e2b/code-interpreter-template describing a prior security fix (moving Jupyter off TCP to a Unix socket) in PR #343; no source code is touched here. There is no security-sensitive surface in this diff itself—it's purely release metadata/documentation. The change is trivial, mechanical, and matches the PR title/description, so this is a safe approve.