docs: describe God's Eye View in conversations in the changelog and current state

CHANGELOG.md

@@ -1,5 +1,14 @@
 # Changelog
 
+- Show God's Eye View inside AI conversations. Answers that can be shown
+  include a view (camera, layers, style, map, marks, something to follow),
+  and `show_in_gods_eye_view` displays it as the live globe in clients that
+  support MCP Apps, such as Claude Desktop and the Codex and ChatGPT desktop
+  apps, and as a link everywhere else. The panel loads the app's panel build
+  (`npm run build:panel`) and its data through the MCP server, so a local
+  server needs no HTTPS or tunnel. `?embed=1` shows the globe alone for pages
+  that frame the app.
+
 - Add tools for language-model clients and a local MCP server, served over
   stdio by `npm run mcp` and over HTTP at `/mcp` on the development and preview
   servers for local requests only. `npm run mcp`

build/panel.js

@@ -62,7 +62,7 @@ const CONTENT_TYPES = {
 
 /**
  * Vite plugin serving the panel build at PANEL_BASE on the dev server, as
- * the preview server and hosted deployments serve it from the build output.
+ * the preview server and production builds serve it from the build output.
  */
 export function panelBuildPlugin({ outDir = PANEL_OUT_DIR } = {}) {
   return {

docs/CURRENT-STATE.md

@@ -6,9 +6,12 @@ Tool answers that can be shown in God's Eye View include a view: camera, layers,
 style, map, marks and an aircraft or satellite to follow, written in the
 share-link format (`gods-eye-view/view`). `show_in_gods_eye_view` shows a view as live
 God's Eye View inside clients that display MCP Apps, and as a link everywhere.
-`?embed=1` shows the app as the globe alone and takes new views from the page
-that frames it. MCP leads with the tools that find what to show. See
-[tools and the MCP server](TOOLS.md).
+The panel runs the app's panel build (`npm run build:panel`, served at
+`/panel/`) and loads it, with its data, through the MCP server, so it works
+in Claude Desktop and in the Codex and ChatGPT desktop apps with a local
+server and no HTTPS. `?embed=1` shows the app as the globe alone and takes
+new views from the page that frames it. MCP leads with the tools that find
+what to show. See [tools and the MCP server](TOOLS.md).
 
 ## Tools and local MCP server — October 1, 2026
 

docs/TOOLS.md

@@ -125,7 +125,7 @@ never requests the app's server itself. It loads everything from the app's
 own paths through `panel_request`, a tool only the panel may call
 (`_meta.ui.visibility: ["app"]`): the MCP server requests the path from the
 app's server and returns the response, compressed and in parts when large.
-The same path works for a local server, a hosted one, and every host. Only
+The same path works in every host. Only
 map imagery, tiles and fonts load directly, from the providers the
 resource's `csp` lists. `panel_request` refuses `/api/setup`, which writes
 provider keys.