Bind visualization status to snapshot freshness
This commit is contained in:
parent
24bd13f9d9
commit
176b2d2784
9 changed files with 627 additions and 43 deletions
|
|
@ -254,6 +254,17 @@ docforge --project-root "$PROJECT" visualize --query persistence
|
|||
The command opens the default browser. Add `--no-open` when a script only needs the returned JSON
|
||||
URL. Use `visualization-status` and `visualization-stop` to inspect or stop the project viewer.
|
||||
|
||||
Status separates the worker lifecycle from snapshot freshness. A worker may remain `running` while
|
||||
`snapshot_state` is `stale`; it will not be reused by the next `visualize` call. `freshness.index`
|
||||
checks the exact pinned index publication with file identity only. `freshness.source` compares the
|
||||
cheap project generation when the project can prove one. Unavailable proof is `unknown`, never
|
||||
silently `current`. Status does not load project content, open SQLite, rebuild the index, or renew
|
||||
browser activity.
|
||||
|
||||
The freshness protocol requires viewer manager version 2. After upgrading an already running
|
||||
installation, rerun `docforge-viewer-manager install-user-service` or restart the foreground
|
||||
manager before requesting status.
|
||||
|
||||
## Visualization usage
|
||||
|
||||
- Left-click a node for its compact descriptor.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue