Docs: add sticky navbar CSS for Mintlify

docs/assets/mintlify-navbar.css

@@ -0,0 +1,35 @@
+/* Make Mintlify navbar sticky - override all positioning */
+#navbar {
+  position: sticky !important;
+  top: 0 !important;
+  z-index: 9999 !important;
+  width: 100% !important;
+}
+
+/* Override fixed positioning from Tailwind */
+#navbar.fixed,
+#navbar[class*="fixed"],
+div#navbar {
+  position: sticky !important;
+}
+
+/* Remove any overflow restrictions on parents that break sticky */
+* {
+  overflow-x: visible !important;
+}
+
+body,
+html,
+body > div,
+body > div > div {
+  overflow-y: visible !important;
+  overflow-x: visible !important;
+}
+
+/* Ensure layout containers don't break sticky */
+[class*="layout"],
+[class*="Layout"],
+main,
+[role="main"] {
+  overflow: visible !important;
+}

docs/docs.json

@@ -7,6 +7,7 @@
     "dark": "/assets/pixel-lobster.svg"
   },
   "favicon": "/assets/pixel-lobster.svg",
+  "css": "/assets/mintlify-navbar.css",
   "colors": {
     "primary": "#FF5A36"
   },

docs/install/node.md

@@ -1,16 +1,16 @@
 ---
 summary: "Node.js + npm install sanity: versions, PATH, and global installs"
 read_when:
-  - You installed Clawdbot but `clawdbot` is “command not found”
+  - You installed Clawdbot but clawdbot is command not found
-  - You’re setting up Node.js/npm on a new machine
+  - You're setting up Node.js/npm on a new machine
-  - `npm install -g ...` fails with permissions or PATH issues
+  - npm install -g fails with permissions or PATH issues
 ---
 
 # Node.js + npm (PATH sanity)
 
-Clawdbot’s runtime baseline is **Node 22+**.
+Clawdbot's runtime baseline is **Node 22+**.
 
-If you can run `npm install -g clawdbot@latest` but later see `clawdbot: command not found`, it’s almost always a **PATH** issue: the directory where npm puts global binaries isn’t on your shell’s PATH.
+If you can run `npm install -g clawdbot@latest` but later see `clawdbot: command not found`, it's almost always a **PATH** issue: the directory where npm puts global binaries isn't on your shell's PATH.
 
 ## Quick diagnosis
 
@@ -23,9 +23,9 @@ npm prefix -g
 echo "$PATH"
 ```
 
-If `$(npm prefix -g)/bin` (macOS/Linux) or `$(npm prefix -g)` (Windows) is **not** present inside `echo "$PATH"`, your shell can’t find global npm binaries (including `clawdbot`).
+If `$(npm prefix -g)/bin` (macOS/Linux) or `$(npm prefix -g)` (Windows) is **not** present inside `echo "$PATH"`, your shell can't find global npm binaries (including `clawdbot`).
 
-## Fix: put npm’s global bin dir on PATH
+## Fix: put npm's global bin dir on PATH
 
 1) Find your global npm prefix:
 
@@ -51,7 +51,7 @@ On Windows, add the output of `npm prefix -g` to your PATH.
 
 ## Fix: avoid `sudo npm install -g` / permission errors (Linux)
 
-If `npm install -g ...` fails with `EACCES`, switch npm’s global prefix to a user-writable directory:
+If `npm install -g ...` fails with `EACCES`, switch npm's global prefix to a user-writable directory:
 
 ```bash
 mkdir -p "$HOME/.npm-global"
@@ -63,7 +63,7 @@ Persist the `export PATH=...` line in your shell startup file.
 
 ## Recommended Node install options
 
-You’ll have the fewest surprises if Node/npm are installed in a way that:
+You'll have the fewest surprises if Node/npm are installed in a way that:
 
 - keeps Node updated (22+)
 - makes the global npm bin dir stable and on PATH in new shells
@@ -74,4 +74,4 @@ Common choices:
 - Linux: your preferred version manager, or a distro-supported install that provides Node 22+
 - Windows: official Node installer, `winget`, or a Windows Node version manager
 
-If you use a version manager (nvm/fnm/asdf/etc), ensure it’s initialized in the shell you use day-to-day (zsh vs bash) so the PATH it sets is present when you run installers.
+If you use a version manager (nvm/fnm/asdf/etc), ensure it's initialized in the shell you use day-to-day (zsh vs bash) so the PATH it sets is present when you run installers.