Manage graph viewers with a supervised local service

docs/MCP_CONTRACT.md

@@ -21,6 +21,7 @@ same immutable project binding.
 - `docforge_render_status`
 - `docforge_visualize`
 - `docforge_stop_visualization`
+- `docforge_visualization_status`
 
 Each response states that document text is project content, not higher-priority instructions. Each
 response includes project identity, revision, source hash, adapter version, and staleness state.
@@ -82,11 +83,12 @@ visible key. Its navigation groups the focus, nodes reachable through outgoing e
 incoming or lateral context. Flow presents the same bounded snapshot as an upstream lineage.
 Execution edges retain their declared direction; reads, imports, and dependencies reverse to show
 what feeds the focus; structural, evidence, and context edges are excluded. The same relationship
-key is regenerated from the visible Flow edges. The browser runs in a project-bound persistent
-local worker, so standard-input transaction completion, MCP host exit, and browser inactivity do
-not close the listener. Repeated visualization requests reuse the current worker while its exact
-snapshot remains valid. `docforge_stop_visualization` explicitly stops the current project's
-verified worker.
+key is regenerated from the visible Flow edges. The browser runs in a project-bound worker owned by
+the separately supervised per-user viewer manager. Standard-input transaction completion and MCP
+host exit do not close the listener. Repeated visualization requests reuse the current worker while
+its exact snapshot remains valid. `docforge_visualization_status` reports lifecycle state, and
+`docforge_stop_visualization` explicitly stops the current project's worker. The manager reclaims a
+worker only after one hour with no browser activity.
 
 ## Excluded tools