Design: pipeline progress UI for PipelineStatusCard

[geoffjay]

Context

Tracked as a follow-on to #419 (pipeline abstraction schema and conductor implementation).

The existing PipelineStatusCard on the dashboard is currently a stub — usePipelineStatus returns null (see PR #648). Once #419 resolves the scope question (first-class orchestrator with DB/API vs. CLI-only), this issue covers the design and implementation of real-time pipeline progress visualization.

Two design paths (pending #419 scope decision)

Path A — First-class orchestrator support (#419 resolves to DB + API)

Design and implement a live pipeline progress indicator per issue:

◉ triage → ◉ enrich → ● implement → ○ review → ○ merge

• Wire usePipelineStatus hook to the pipeline API endpoint
• Show active stage, completed stages, and pending stages
• Real-time updates via WebSocket or polling

Path B — CLI-only (#419 stays CLI-only)

• PipelineStatusCard reads from memory service digests
• Informational display only (no real-time stage transitions)
• Consistent with current stub pattern

Dependency

Blocked by #419 — the architectural decision on first-class vs. CLI-only orchestrator support must be made before this design work begins.

Acceptance Criteria

• Design decision documented (Path A or Path B based on Plan: Create automation structure that combines agents and workflows #419 outcome)
• PipelineStatusCard renders meaningful pipeline state (not a stub)
• usePipelineStatus hook wired to appropriate data source
• Visual design matches the stage schema defined in Plan: Create automation structure that combines agents and workflows #419

[geoffjay]

✅ Triage Complete

Field	Value
Type	enhancement
Complexity	medium
Milestone	v0.9.0 - Autonomous Development Pipeline
Labels	enhancement, frontend, ui, needs-decision, complexity:medium

Blocked by #419 — the first-class orchestrator vs. CLI-only scope decision must be made before design work can begin. Two paths are fully scoped in the issue body.

Designer input confirms the stage schema (named stages with entry, after, conditions) maps directly to a visual progress indicator. No clarifying questions needed once the #419 architectural decision lands.