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

Keep visualization worker alive until explicit stop

This commit is contained in:
Andraxion 2026-07-24 23:55:55 -04:00
parent 440ca7510f
commit eb48ba1a51
12 changed files with 410 additions and 150 deletions

View file

@ -23,6 +23,7 @@ The DocForge repository contains the complete generic CLI and stdio MCP server.
multi-node framing, visible node selection, Space-to-center, mouse-wheel zoom, left-button drag
panning, zoom controls, viewport reset, relationship color and symbol keys, and an upstream
lineage Flow view.
- `docforge_stop_visualization`, which explicitly stops the current project's persistent viewer.
- Isolated documentation changesets, proposal validation, diffs, and escaped HTML previews when a
proposal writer and render view are configured.
@ -184,7 +185,7 @@ Add a project-specific stdio MCP server to the agent host:
Restart or reload the agent host. Confirm that it exposes tools beginning with
`docforge_project_info`, `docforge_get_node`, `docforge_search`, `docforge_dependencies`,
`docforge_impact`, `docforge_get_context`, `docforge_visualize`, and
`docforge_create_changeset`.
`docforge_stop_visualization`, and `docforge_create_changeset`.
Omit `--proposal-writer` for a read-only integration.
@ -290,7 +291,8 @@ Require these adapter acceptance checks:
- Missing targets, duplicate IDs, unsafe paths, unsorted metadata, and invalid hashes fail closed.
- Building the graph does not import the application or cause runtime, network, database, or
filesystem side effects.
- Read-only MCP exposes only the fixed DocForge read surface, including `docforge_visualize`.
- Read-only MCP exposes only the fixed DocForge read surface, including visualization start and
explicit viewer shutdown.
- Proposal-enabled MCP cannot modify derived source facts or write outside confined changeset and
preview roots.
- Build, check, MCP protocol tests, adapter tests, and the owning project's full test gate pass.
@ -337,8 +339,7 @@ Place this policy in the project's `AGENTS.md` and adjust the manual path and pr
- If DocForge reports stale state, missing nodes, invalid edges, or an index mismatch, stop and
repair or rebuild the graph before claiming the work complete.
- When asked to “visualize” the project or a node, call `docforge_visualize`. The viewer is
loopback-only and read-only. An open page renews its bounded lease across short MCP transactions;
explicit process termination closes it, and an abandoned page expires automatically.
loopback-only, read-only, and persists until `docforge_stop_visualization` explicitly stops it.
```
The policy is what makes DocForge part of normal development rather than an optional lookup tool.