Add modal graph node inspection

docs/CONTRACT.md

@@ -23,7 +23,7 @@ approved contract and measured cross-project evidence; it is not an unimplemente
 - Result envelope: `schemas/result.schema.json`, version 1.
 - Changeset schema: `schemas/changeset.schema.json`, version 1.
 - Index schema: version 1, disposable and reproducible.
-- Core, CLI, and MCP server: version 0.7.1.
+- Core, CLI, and MCP server: version 0.7.2.
 
 Schema files describe the generic interchange contract. Runtime validation remains responsible for
 path confinement, source hashing, relationship resolution, dependency cycles, project limits, stale
@@ -105,11 +105,16 @@ overview, bounded search, exact node content, and bounded incoming-and-outgoing
 There is no write endpoint, arbitrary query endpoint, static filesystem handler, external asset,
 or project-selection control.
 
-The `graph-browser@2` template provides mouse-wheel zoom centered on the pointer, left-button drag
+The `graph-browser@3` template provides mouse-wheel zoom centered on the pointer, left-button drag
 pan, explicit zoom-in and zoom-out buttons, a reset-view button, and a live zoom percentage. A
 four-pixel drag threshold preserves node activation for ordinary clicks. Loading another root node
 resets the viewport so the new neighborhood begins centered and fully framed.
 
+Activating a graph node opens a modal inspector containing that node's complete validated metadata
+and content. Inspection does not replace the current neighborhood or reset the viewport. The modal
+supports keyboard activation, Escape, explicit close controls, and backdrop dismissal. Loading the
+inspected node as the new root requires the separate Explore neighborhood action.
+
 One MCP process owns at most one listener. Repeated invocations reuse it and may replace its
 validated snapshot only after a fresh index check. The listener stops with the MCP process.
 Project-specific integrations receive the same tool because it operates on the supplied

docs/MCP_CONTRACT.md

@@ -61,7 +61,7 @@ only through the explicit local CLI integration command.
 
 ## Visualization boundary
 
-`docforge_visualize` starts the fixed built-in `graph-browser@2` template against the currently
+`docforge_visualize` starts the fixed built-in `graph-browser@3` template against the currently
 validated derived index. It may focus one stable node, run one bounded lexical query, or open the
 project overview. The tool returns a loopback URL and exact snapshot identity.
 
@@ -70,7 +70,9 @@ expression. Its HTTP surface is token-bound, read-only, same-origin, and limited
 search/filter, and node-neighborhood JSON. The browser exposes an exact validated index snapshot.
 It rejects index replacement or alteration and requires another MCP invocation to refresh.
 Viewport interaction is entirely client-side: wheel zoom, left-button drag pan, explicit zoom
-buttons, and reset never request or mutate project data.
+buttons, and reset never request or mutate project data. Graph-node activation fetches exact node
+data from the same bounded read endpoint and opens a client-side modal inspector. Replacing the
+current root requires the modal's explicit Explore neighborhood action.
 
 ## Excluded tools
 

docs/NEW_PROJECT_QUICKSTART.md

@@ -16,8 +16,9 @@ The DocForge repository contains the complete generic CLI and stdio MCP server.
 
 - Project identity, validation, exact-node retrieval, lexical search, and filtering.
 - Backlinks, dependency traversal, impact traversal, and bounded context profiles.
-- `docforge_visualize`, which starts the token-protected, loopback-only `graph-browser@2` viewer.
+- `docforge_visualize`, which starts the token-protected, loopback-only `graph-browser@3` viewer.
   The viewer supports search, family filtering, exact-node inspection, bounded neighborhoods,
+  modal inspection without losing the current neighborhood, explicit neighborhood exploration,
   mouse-wheel zoom, left-button drag panning, zoom controls, and viewport reset.
 - Isolated documentation changesets, proposal validation, diffs, and escaped HTML previews when a
   proposal writer and render view are configured.