Render research nodes in the graph workbench #111

Merged

lost-rob0t merged 9 commits from agent/issue-104-research-node-graph-ui into main

2026-07-28 04:53:33 +00:00

lost-rob0t commented

2026-07-28 04:51:42 +00:00

(Migrated from github.com)

Refs #104

Summary

render research-node documents as distinct status-labelled graph nodes
map running, paused, blocked, completed, failed, and killed states to theme-aware borders
show research state plus input, output, and actor counts in the graph inspector
add right-click Inspect outputs and Clone research node actions
clone plans as fresh drafts without copying runtime results
add focused projection, helper, and inspector tests

Scope

This completes the graph rendering portion of #104 and adds the safe, non-executing context actions. The issue remains open for its compact/full editor, real actor queue lifecycle, provenance relations, and complete desktop/mobile coverage.

The PR intentionally does not implement a fake Run action that only changes status without dispatching actors.

Verification

Merge only after the repository CI workflow passes all static, unit/integration, build, artifact, and browser gates.

Refs #104 ## Summary - render `research-node` documents as distinct status-labelled graph nodes - map running, paused, blocked, completed, failed, and killed states to theme-aware borders - show research state plus input, output, and actor counts in the graph inspector - add right-click **Inspect outputs** and **Clone research node** actions - clone plans as fresh drafts without copying runtime results - add focused projection, helper, and inspector tests ## Scope This completes the graph rendering portion of #104 and adds the safe, non-executing context actions. The issue remains open for its compact/full editor, real actor queue lifecycle, provenance relations, and complete desktop/mobile coverage. The PR intentionally does not implement a fake **Run** action that only changes status without dispatching actors. ## Verification Merge only after the repository CI workflow passes all static, unit/integration, build, artifact, and browser gates.