Problem

When a workflow completes (via CLI, Web UI, or any platform), the main chat view does not display a completion summary. Users must manually navigate to the Workflow Execution view (Dashboard → View Logs) to see what happened.

Current Behavior

• Chat shows only the raw text output from the last node — no workflow context
• No indication in chat that a workflow ran, how long it took, or whether it succeeded/failed
• For CLI-launched workflows: the chat view shows just the final text blob with a timestamp
• No "View Logs" link or workflow status card in the chat

Evidence

Screenshots of the "Fix GitHub Issue 11" conversation:

• Chat view: Shows only the final summary text (Artifacts, Next Steps) — no workflow card, no progress, no link to logs
• Workflow execution view (Dashboard → View Logs): Shows the full graph with 7 nodes, tool calls, and detailed per-node output

The user sees just the end result in chat with no way to understand what happened or navigate to the detailed view.

Expected Behavior

After a workflow completes, the chat should show a workflow completion card containing:

1. Workflow name and status (completed/failed/cancelled)
2. Duration
3. Node summary (e.g., "7 nodes completed")
4. Key artifacts (with clickable links)
5. "View Logs" link that navigates to /workflows/runs/{runId}

Technical Context

Data already available: The executor sends workflowResult metadata ({ workflowName, runId }) on the final message. The ChatInterface.tsx (packages/web/src/components/chat/ChatInterface.tsx:49-50) already parses workflowResult from message metadata.

What's missing:

1. CLI adapter (packages/cli/src/adapters/cli-adapter.ts:51-54): Persists workflowResult metadata, but the chat view doesn't render it as a card
2. No completion card component: MessageList.tsx and MessageBubble.tsx don't have a workflow result rendering path
3. No explicit "workflow completed" message: The executor doesn't send a dedicated summary message — the last node's text output is the final message

Workflow dispatch card exists: The chat already shows a WorkflowDispatchCard when a workflow starts (via workflowDispatch metadata). A similar pattern should be used for completion.

Suggested Approach

1. Create a WorkflowResultCard component (similar to existing WorkflowDispatchCard)
2. Render it when a message has workflowResult metadata
3. Fetch run summary (status, duration, node count, artifacts) from /api/workflows/runs/{runId}
4. Include a "View Logs" link to /workflows/runs/{runId}
5. For failed workflows, show error classification and suggested actions