fix: co-locate troubleshooting images to fix broken CDN rendering (#444)

Images in docs/images/ are served as broken 130-byte placeholders by
Mintlify CDN. Co-locating images with the MDX file (matching the
working pattern in features/workflow/ and features/cowork/) bypasses
this issue. Also fixes the Slack link placeholder.

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

docs/troubleshooting/connection-issues.mdx

@@ -6,7 +6,7 @@ description: "How to fix connection issues when the BrowserOS agent is not respo
 If you see **"Failed to Fetch"** or **"Unable to connect to BrowserOS agent"**, your agent has been killed.
 
 <Frame>
-  <img src="/images/troubleshooting/failed-to-fetch-error.png" alt="Failed to fetch error" />
+  <img src="/troubleshooting/failed-to-fetch-error.png" alt="Failed to fetch error" />
 </Frame>
 
 ## Windows: Did you allow the BrowserOS Agent?
@@ -14,7 +14,7 @@ If you see **"Failed to Fetch"** or **"Unable to connect to BrowserOS agent"**,
 When BrowserOS starts for the first time on Windows, a popup will ask if you want to allow **BrowserOS Agent** to access the network. Click **Allow** — the agent runs as a separate process alongside the browser and needs this permission to work. If you clicked **Cancel** or missed this prompt, the agent won't be able to connect.
 
 <Frame>
-  <img src="/images/windows-installation/windows-installation-allow-browseros-agent.png" alt="Allow BrowserOS Agent network access prompt" />
+  <img src="/troubleshooting/windows-installation-allow-browseros-agent.png" alt="Allow BrowserOS Agent network access prompt" />
 </Frame>
 
 To fix this, go to **Windows Security → Allow an app through your network settings**, and make sure **BrowserOS Agent** is enabled.
@@ -26,7 +26,7 @@ To fix this, go to **Windows Security → Allow an app through your network sett
     Open **Settings** from the sidebar, scroll to the MCP Server section, and click **Restart**. Wait a couple of minutes.
 
     <Frame>
-      <img src="/images/troubleshooting/mcp-server-restart.png" alt="Click Restart in MCP Server Settings" />
+      <img src="/troubleshooting/mcp-server-restart.png" alt="Click Restart in MCP Server Settings" />
     </Frame>
   </Step>
 
@@ -39,7 +39,7 @@ To fix this, go to **Windows Security → Allow an app through your network sett
         4. Reopen **BrowserOS** — the agent will restart automatically.
 
         <Frame>
-          <img src="/images/windows-installation/troubleshoot-search-restart-agent-task-manager.png" alt="Search for BrowserOS Agent in Task Manager and restart it" />
+          <img src="/troubleshooting/troubleshoot-search-restart-agent-task-manager.png" alt="Search for BrowserOS Agent in Task Manager and restart it" />
         </Frame>
 
         <Note>If the agent still doesn't reconnect, end both **BrowserOS** and **BrowserOS Agent** in Task Manager, then reopen the app.</Note>
@@ -100,7 +100,7 @@ If you're still experiencing issues, reach out:
   <Card title="Discord" icon="discord" href="https://discord.gg/YKwjt5vuKr">
     Get help from the community
   </Card>
-  <Card title="Slack" icon="slack" href="SLACK_LINK_HERE">
+  <Card title="Slack" icon="slack" href="https://dub.sh/browserOS-slack">
     Join our Slack
   </Card>
 </CardGroup>