fix: ensure status indicator present earlier in exec path

[sayan-oai]

ensure status indicator present in all classifications of exec tool. fixes indicator disappearing after preambles, will look into using phase to avoid this class of error in a few hours.

commands parsed as unknown faced this issue

tested locally, added test for specific failure flow

[sayan-oai]

@codex review rhis

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Chef's kiss.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[joshka-oai]

Compared with #10701: there is semantic overlap, but they cover different timing windows, so both are useful.

• fix: ensure status indicator present earlier in exec path #10700 restores the status indicator when "exec_command_begin" fires (especially unified-exec / unknown-classification paths).
• fix(tui): restore working shimmer after preamble output #10701 keeps/restores the working shimmer during the preamble idle gap while the task is still running.

Together they address the "looks finished too early" UX across both phases.

I also suggest adding a visual snapshot test for the exec-begin path (in addition to the state/visibility assertion), so we verify the user-visible working affordance and guard against future rendering regressions.