administrator/DocForge2
1
0
Fork 0
Code Issues Pull requests Projects Releases 2 Packages Wiki Activity Actions Pages

Manage graph viewers with a supervised local service

Browse source
This commit is contained in:
Andraxion 2026-07-25 00:17:21 -04:00
parent eb48ba1a51
commit 7c87536167
14 changed files with 1027 additions and 103 deletions
Download patch file Download diff file Expand all files Collapse all files

11
README.md
View file

@ -46,9 +46,9 @@ relation-specific colors, line patterns, directional symbols, and an exact visib
constructs a bounded upstream lineage with semantic direction for execution, data, and dependency
relations while excluding structural and evidence context.
DFG-18 makes the viewer a truly persistent project-bound local service. It survives MCP process
turnover and browser inactivity, reuses the current snapshot URL, and stops only when
`docforge_stop_visualization` explicitly requests it.
DFG-18 makes the viewer a managed project-bound local service. A native per-user supervisor owns
the viewer manager, which survives MCP process turnover, reuses the current snapshot URL, exposes
status and explicit stop tools, and reclaims only genuinely idle workers.
## Development
@ -100,8 +100,9 @@ surface.
Both generic and explicit adapter MCP servers expose the same visualization tools because they read
the validated `ProjectIndex` supplied by the project binding. `docforge_visualize` reuses its
unguessable loopback URL when the current snapshot remains valid, or replaces the worker after a
complete index check when it does not. The project-bound worker remains available until
`docforge_stop_visualization` explicitly stops it.
complete index check when it does not. The per-user viewer manager retains active workers across
MCP process turnover, reports state through `docforge_visualization_status`, and reclaims idle
workers after one hour. See [`docs/VIEWER_MANAGER.md`](docs/VIEWER_MANAGER.md) for installation.
See [`docs/NEW_PROJECT_QUICKSTART.md`](docs/NEW_PROJECT_QUICKSTART.md) for a complete generic MCP
setup, continuous-agent policy, visualization instructions, and a project-adapter checklist.