Keep visualization worker alive until explicit stop
This commit is contained in:
parent
440ca7510f
commit
eb48ba1a51
12 changed files with 410 additions and 150 deletions
|
|
@ -1,5 +1,23 @@
|
|||
# Completed slices
|
||||
|
||||
## DFG-18 persistent visualization lifecycle
|
||||
|
||||
### Changed
|
||||
|
||||
- Released DocForge 0.11.0 with a persistent project-bound visualization worker.
|
||||
- Replaced browser leases and MCP-owner-process shutdown with an explicit
|
||||
`docforge_stop_visualization` read tool.
|
||||
- Added a private, atomically written project-cache registry. It reuses a live worker only when
|
||||
its authenticated loopback endpoint and exact index snapshot identity match the current request.
|
||||
- Removed the parent-process `Popen` lifecycle dependency by spawning the session-isolated worker
|
||||
directly, so no process cleanup warning or parent lifetime remains coupled to the browser.
|
||||
|
||||
### Verification
|
||||
|
||||
- A process-boundary test terminates the launcher, confirms the viewer remains live, confirms a
|
||||
separate runner reuses its URL, and confirms the explicit stop tool terminates it.
|
||||
- Focused warning-strict lifecycle and MCP contract tests pass.
|
||||
|
||||
## DFG-17 relationship-aware graph and upstream flow
|
||||
|
||||
### Changed
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue