You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat: live visibility into in-progress rollouts #2859
Wave 3 — operational visibility under #2831. This does not block #2750 correctness or completion.
Problem
Aggregate progress and completed JSONL rows do not show what an active rollout is doing or whether a live collector has stopped progressing. Concurrent server logs are interleaved and vary by component.
Essential scope
User-facing inspection by stable rollout and attempt identity.
Current stage, elapsed time, latest progress heartbeat, and bounded recent activity.
Presentation of active, slow, retrying, stalled, cancelled, and terminal states.
Bounded redaction that excludes secrets, full prompts, and unbounded response bodies.
This issue owns presentation and operator workflow.
Dependencies
Integration follows stable identity from #2135 and a progress/status API coordinated with #3160. UI/API design and redaction tests may proceed earlier. It is a child of #2831, not #3160.
Acceptance criteria
Users can select an active rollout and see identity, stage, elapsed time, and last progress.
Slow expected work is distinguishable from bounded retry and stalled execution.
Recent activity and failures are bounded and redacted.
The view works without tracing enabled.
Concurrent completion, retry, cancellation, and stale-progress races are handled.
Activity