Complete graph explorer projection

docs/discovery-queries.md

@@ -78,8 +78,19 @@ Export the graph as Mermaid:
 railiance-fabric export --format mermaid
 ```
 
+Export the graph as the manifest-compatible graph explorer payload:
+
+```bash
+railiance-fabric export --format graph-explorer
+```
+
 The JSON export has two top-level arrays:
 
 - `nodes`: service, capability, interface, dependency, and binding nodes
 - `edges`: graph relationships such as `provides`, `exposes`,
   `available_via`, `consumes`, `binds:<status>`, and `uses_interface`
+
+The graph explorer payload wraps those nodes and edges as Cytoscape-compatible
+elements with stable keys, layers, display state, visual facets, source
+references, and deep links. The registry service exposes the same projection at
+`GET /exports/graph-explorer`.

docs/graph-explorer-contract.md

@@ -23,6 +23,12 @@ GET /exports/graph-explorer/manifest
 GET /exports/graph-explorer
 ```
 
+The local CLI can emit the same payload for repo-local inspection:
+
+```bash
+railiance-fabric export --format graph-explorer
+```
+
 The manifest tells a graph shell where to load data, which fields are stable,
 which layers exist, which filter fields are available, and which modes the host
 supports.