chore: Run pnpm format:fix.

docs/environment.md

@@ -5,17 +5,18 @@ read_when:
   - You are debugging missing API keys in the Gateway
   - You are documenting provider auth or deployment environments
 ---
+
 # Environment variables
 
 OpenClaw pulls environment variables from multiple sources. The rule is **never override existing values**.
 
 ## Precedence (highest → lowest)
 
-1) **Process environment** (what the Gateway process already has from the parent shell/daemon).
-2) **`.env` in the current working directory** (dotenv default; does not override).
-3) **Global `.env`** at `~/.openclaw/.env` (aka `$OPENCLAW_STATE_DIR/.env`; does not override).
-4) **Config `env` block** in `~/.openclaw/openclaw.json` (applied only if missing).
-5) **Optional login-shell import** (`env.shellEnv.enabled` or `OPENCLAW_LOAD_SHELL_ENV=1`), applied only for missing expected keys.
+1. **Process environment** (what the Gateway process already has from the parent shell/daemon).
+2. **`.env` in the current working directory** (dotenv default; does not override).
+3. **Global `.env`** at `~/.openclaw/.env` (aka `$OPENCLAW_STATE_DIR/.env`; does not override).
+4. **Config `env` block** in `~/.openclaw/openclaw.json` (applied only if missing).
+5. **Optional login-shell import** (`env.shellEnv.enabled` or `OPENCLAW_LOAD_SHELL_ENV=1`), applied only for missing expected keys.
 
 If the config file is missing entirely, step 4 is skipped; shell import still runs if enabled.
 
@@ -28,9 +29,9 @@ Two equivalent ways to set inline env vars (both are non-overriding):
   env: {
     OPENROUTER_API_KEY: "sk-or-...",
     vars: {
-      GROQ_API_KEY: "gsk-..."
-    }
-  }
+      GROQ_API_KEY: "gsk-...",
+    },
+  },
 }
 ```
 
@@ -43,13 +44,14 @@ Two equivalent ways to set inline env vars (both are non-overriding):
   env: {
     shellEnv: {
       enabled: true,
-      timeoutMs: 15000
-    }
-  }
+      timeoutMs: 15000,
+    },
+  },
 }
 ```
 
 Env var equivalents:
+
 - `OPENCLAW_LOAD_SHELL_ENV=1`
 - `OPENCLAW_SHELL_ENV_TIMEOUT_MS=15000`
 
@@ -62,10 +64,10 @@ You can reference env vars directly in config string values using `${VAR_NAME}`
   models: {
     providers: {
       "vercel-gateway": {
-        apiKey: "${VERCEL_GATEWAY_API_KEY}"
-      }
-    }
-  }
+        apiKey: "${VERCEL_GATEWAY_API_KEY}",
+      },
+    },
+  },
 }
 ```