Show provider retries and last parent output alongside Working

[andrewfree]

Please make the thread's Working status distinguish known provider retries from active tool execution and recent parent output.

A turn can remain running while the provider retries a request. Separately, a legitimate long-running tool can produce little conversational output. The same broad status makes it difficult to decide whether to wait or intervene.

The inspected Codex integration supports this distinction:

• CodexSessionRuntime.ts keeps the session running when an error notification has willRetry: true.
• CodexAdapter.ts maps retryable errors to runtime.warning.
• All 52 existing tests in CodexAdapter.test.ts passed against the inspected source, including retryable-error mapping. This verifies adapter behavior, not every UI transition or a lost completion event.

Source reference: Codex runtime and adapter.

The existing timeline already displays an elapsed Working timer and distinguishes setup and compaction. The requested addition is the cause of the wait and recency of parent output, alongside those existing cues.

A focused improvement could show:

• A known provider retry and its available error category near Working, for example Retrying provider: HTTP 408, clearing that transient state when fresh provider progress arrives.
• Time since the parent last produced output, separately from worker activity or a newly submitted user message.
• The active tool name and elapsed time, where those signals are available. If progress is unknown, label it as unknown.

A blanket inactivity cutoff could interrupt valid long-running tools. Existing stop/retry controls can remain the user's choice. This proposal concerns making known state understandable, without inferring that every quiet turn is dead or that T3 caused a provider failure.

Related areas include #940's reconnect-warning behavior, #5742's reconnect state, and #7210/#8358's provider-specific inactivity handling. If a current discussion already covers this precise distinction, this can be consolidated there.

This proposal contains no conversation excerpts, task details, identifiers, screenshots, or raw logs.

Provenance: a human reported the confusing status and directed the investigation. Source/test verification, drafting, and submission were performed by an AI assistant with authorization.