# Workflow Visualization And Replay

## Recommendation

Do not restore workflow visualization as a standalone sidebar product.

Restore it as a runtime run-detail capability under `Releases`, with a secondary entry point from `Evidence > Verify & Replay`, and a smaller design-time preview inside the workflow editor.

## Why

- The visualizer is about understanding a run, not browsing a separate product area.
- The feature already has runtime concepts like critical path, timeline, node states, and auto-refresh.
- Those belong closest to release runs, replay, and evidence.

## Primary Placement

- Menu group: `Releases`
- Section: `Runs`

Primary route family:
- `/releases/runs/:runId/*`

## Secondary Placement

- `Evidence > Verify & Replay`
  - link into the same run graph/replay context

### Design-time secondary placement
- `Administration > Workflows`
  - workflow editor gets a `Preview DAG` mode or tab
  - this is authoring-time preview, not runtime run analysis

## Product Shape

### Release run detail tabs
- `Summary`
- `Graph`
- `Timeline`
- `Critical Path`
- `Replay`
- `Evidence`

The graph/timeline/critical-path experiences should be facets of the same run detail, not separate products.

## Merge Map

### Into runtime run detail
- `WorkflowVisualizerComponent`
- `TimeTravelControlsComponent`
- `StepDetailPanelComponent`

### Into design-time authoring
- reusable graph-preview subset of `WorkflowVisualizerComponent`
  - only for `Workflow Editor`
  - without runtime replay state

## Placement For Single Actions And Stray Pages

### Step detail
- Right drawer from the `Graph` tab
- Not a full route unless deep-linking to failed step diagnostics becomes necessary

### Time-travel controls
- Toolbar in the `Timeline` or `Replay` tab
- Not its own page

### Critical path
- Toggle or subtab inside `Graph`
- Not a separate sidebar item

### Replay verify
- Primary home in `Replay`
- Secondary deep link from `Evidence > Verify & Replay`

### Workflow authoring preview
- Add a `Preview DAG` tab or toggle in the workflow editor
- Do not mix authoring preview with live runtime telemetry

## Suggested Route Sketch

- `/releases/runs/:runId`
- `/releases/runs/:runId/summary`
- `/releases/runs/:runId/graph`
- `/releases/runs/:runId/timeline`
- `/releases/runs/:runId/replay`
- `/releases/runs/:runId/evidence`
- `/evidence/verify-replay?runId=:runId`
- `/administration/workflows/:workflowId?view=preview`

## What Not To Do

- Do not create a standalone `Workflow Visualization` sidebar item.
- Do not separate graph, replay, and run evidence into unrelated shells.
- Do not put runtime graph tooling only in workflow authoring; runtime operators need it on run detail first.

## Detailed UX And Sprint

- Detailed UX dossier: `../workflow-visualization-replay/README.md`
- Implementation sprint: `../../../docs-archived/implplan/SPRINT_20260307_028_FE_workflow_visualization_replay.md`
- Shipped verification note: `../../../features/checked/web/workflow-visualization-replay-ui.md`

## Corroborating Inputs

- `docs/modules/release-orchestrator/ui/overview.md`
- `docs/modules/release-orchestrator/workflow/evidence-based-release-gates.md`
- `docs/modules/ui/architecture-rework.md`
- `src/Web/StellaOps.Web/src/app/routes/releases.routes.ts`
- `src/Web/StellaOps.Web/src/app/routes/evidence.routes.ts`
- `src/Web/StellaOps.Web/src/app/features/workflow-visualization/workflow-visualization.routes.ts`
- `src/Web/StellaOps.Web/src/app/features/workflow-visualization/components/workflow-visualizer/workflow-visualizer.component.ts`

## Final Call

This should become a `Release Runs` detail capability with graph, timeline, replay, and step-detail views, plus an evidence-side entry point and a smaller workflow-editor preview.