cleanup(markdown): Prettier format all markdown @ 80 char width (#10714)

docs/cli/sandbox.md

@@ -1,6 +1,7 @@
 # Sandboxing in the Gemini CLI
 
-This document provides a guide to sandboxing in the Gemini CLI, including prerequisites, quickstart, and configuration.
+This document provides a guide to sandboxing in the Gemini CLI, including
+prerequisites, quickstart, and configuration.
 
 ## Prerequisites
 
@@ -18,30 +19,36 @@ gemini --version
 
 ## Overview of sandboxing
 
-Sandboxing isolates potentially dangerous operations (such as shell commands or file modifications) from your host system, providing a security barrier between AI operations and your environment.
+Sandboxing isolates potentially dangerous operations (such as shell commands or
+file modifications) from your host system, providing a security barrier between
+AI operations and your environment.
 
 The benefits of sandboxing include:
 
 - **Security**: Prevent accidental system damage or data loss.
 - **Isolation**: Limit file system access to project directory.
 - **Consistency**: Ensure reproducible environments across different systems.
-- **Safety**: Reduce risk when working with untrusted code or experimental commands.
+- **Safety**: Reduce risk when working with untrusted code or experimental
+  commands.
 
 ## Sandboxing methods
 
-Your ideal method of sandboxing may differ depending on your platform and your preferred container solution.
+Your ideal method of sandboxing may differ depending on your platform and your
+preferred container solution.
 
 ### 1. macOS Seatbelt (macOS only)
 
 Lightweight, built-in sandboxing using `sandbox-exec`.
 
-**Default profile**: `permissive-open` - restricts writes outside project directory but allows most other operations.
+**Default profile**: `permissive-open` - restricts writes outside project
+directory but allows most other operations.
 
 ### 2. Container-based (Docker/Podman)
 
 Cross-platform sandboxing with complete process isolation.
 
-**Note**: Requires building the sandbox image locally or using a published image from your organization's registry.
+**Note**: Requires building the sandbox image locally or using a published image
+from your organization's registry.
 
 ## Quickstart
 
@@ -67,7 +74,8 @@ gemini -p "run the test suite"
 
 1. **Command flag**: `-s` or `--sandbox`
 2. **Environment variable**: `GEMINI_SANDBOX=true|docker|podman|sandbox-exec`
-3. **Settings file**: `"sandbox": true` in the `tools` object of your `settings.json` file (e.g., `{"tools": {"sandbox": true}}`).
+3. **Settings file**: `"sandbox": true` in the `tools` object of your
+   `settings.json` file (e.g., `{"tools": {"sandbox": true}}`).
 
 ### macOS Seatbelt profiles
 
@@ -81,7 +89,10 @@ Built-in profiles (set via `SEATBELT_PROFILE` env var):
 
 ### Custom Sandbox Flags
 
-For container-based sandboxing, you can inject custom flags into the `docker` or `podman` command using the `SANDBOX_FLAGS` environment variable. This is useful for advanced configurations, such as disabling security features for specific use cases.
+For container-based sandboxing, you can inject custom flags into the `docker` or
+`podman` command using the `SANDBOX_FLAGS` environment variable. This is useful
+for advanced configurations, such as disabling security features for specific
+use cases.
 
 **Example (Podman)**:
 
@@ -99,7 +110,8 @@ export SANDBOX_FLAGS="--flag1 --flag2=value"
 
 ## Linux UID/GID handling
 
-The sandbox automatically handles user permissions on Linux. Override these permissions with:
+The sandbox automatically handles user permissions on Linux. Override these
+permissions with:
 
 ```bash
 export SANDBOX_SET_UID_GID=true   # Force host UID/GID
@@ -131,7 +143,9 @@ export SANDBOX_SET_UID_GID=false  # Disable UID/GID mapping
 DEBUG=1 gemini -s -p "debug command"
 ```
 
-**Note:** If you have `DEBUG=true` in a project's `.env` file, it won't affect gemini-cli due to automatic exclusion. Use `.gemini/.env` files for gemini-cli specific debug settings.
+**Note:** If you have `DEBUG=true` in a project's `.env` file, it won't affect
+gemini-cli due to automatic exclusion. Use `.gemini/.env` files for gemini-cli
+specific debug settings.
 
 ### Inspect sandbox