Feature request: lifecycle hook events for the provider-wait retry menu

Feature request: a lifecycle hook event fired when the retry-capable provider-wait menu (the screen shown while Codex is waiting on its model provider, with options like "Retry now" / "Dismiss and keep waiting") becomes actionable, and a matching event when it closes. Each event should carry the Codex session (or pane/process) identity so an external supervisor can tell which session it applies to.

Why: the current hook surface covers prompt, tool-call, permission, compaction, Stop, and session-lifecycle boundaries, but nothing fires when this provider-wait menu appears or disappears. An external supervisor that wants to act on this menu — for example, to select "Dismiss and keep waiting" automatically so a long-running unattended session doesn't stall on a transient provider hiccup — currently has no event to act on and no reliable signal that the menu is even present.

Alternatives considered and rejected:

• Polling terminal/pane output for the menu's text on a timer works but is fragile (text and layout can change between versions) and either wastes cycles polling constantly or introduces latency waiting for the next poll.
• Watching for terminal "activity" or "silence" changes as a proxy for the menu appearing doesn't reliably distinguish "provider-wait menu is up" from ordinary idle output, and terminal-level silence/activity signals can each fire only once before needing to be manually reset.
• A standing background watcher process that continuously inspects session state avoids polling latency but adds a persistent component whose own lifecycle has to be managed separately from the session it's watching.

None of these give a supervisor a precise, low-latency signal scoped to this specific menu without either fragility or an extra long-lived process. A first-class lifecycle event would let a supervisor react immediately and only when the menu is genuinely present.

Start by locating the provider-wait retry menu and the existing hook surface for prompt, tool-call, permission, compaction, Stop, and session-lifecycle events. Define matching events for the menu becoming actionable and closing, each carrying session or pane/process identity, and verify that an external supervisor can distinguish the target session and react only while the menu is present.