Enhance context isolation documentation

- Add isolation mention to introduction
- Expand default context behavior note with specific benefits
- Document automatic scaling without artificial limits

Complements existing isolation documentation from PR #249.

Author: github-actions[bot]

src/content/docs/sandbox/api/interpreter.mdx

@@ -7,7 +7,7 @@ sidebar:
 
 import { TypeScriptExample } from "~/components";
 
-Execute Python, JavaScript, and TypeScript code with support for data visualizations, tables, and rich output formats. Contexts maintain state (variables, imports, functions) across executions.
+Execute Python, JavaScript, and TypeScript code with support for data visualizations, tables, and rich output formats. Contexts maintain state (variables, imports, functions) across executions with complete isolation between contexts.
 
 ## Methods
 
@@ -40,7 +40,7 @@ const ctx = await sandbox.createCodeContext({
 </TypeScriptExample>
 
 :::note[Context isolation]
-Each code context is completely isolated from other contexts. Variables, imports, functions, and state defined in one context are never accessible to another context. Each context has a dedicated executor process from creation to deletion, ensuring complete isolation even under heavy concurrent usage.
+Each code context is completely isolated from other contexts. Variables, imports, functions, and state defined in one context are never accessible to another context. Each context has a dedicated executor process from creation to deletion, ensuring complete isolation even under heavy concurrent usage. The system automatically scales to support as many concurrent contexts as needed without artificial limits.
 :::
 
 ### `runCode()`
@@ -87,7 +87,10 @@ await Promise.all([
 </TypeScriptExample>
 
 :::note[Default context behavior]
-If no `context` is provided, a default context is automatically created/reused for the specified `language`. While convenient for quick tests, **explicitly creating contexts is recommended** for production use to maintain predictable state.
+If no `context` is provided, a default context is automatically created/reused for the specified `language`. While convenient for quick tests, **explicitly creating contexts is recommended** for production use to:
+- Maintain predictable state across executions
+- Enable concurrent execution by creating multiple contexts
+- Ensure proper resource cleanup when contexts are deleted
 
 <TypeScriptExample>
 ```