Refine agent runtime controls

[klopez4212]

Summary

• replace ambiguous avatar play controls with centered Start and Restart pills
• preserve avatar clipping while smoothly morphing actions into the running status dot
• use accessible warning contrast and real restart behavior without a duplicate status badge

Validation

• just ci
• focused Playwright coverage for morphing, shared geometry, and light/dark contrast

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 377d3c114a

ℹ️ 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".

[wesbillman]

Reviewed commit 377d3c114aa15967a44478849ff3497450929fd1 on Wes's behalf.

No blocking findings. I traced the new gallery restart path through respawnManagedAgentWithRules, checked the pending/error state transitions and active-turn clearing boundary, reviewed the capsule-to-status-dot mask geometry and WebKit handling, and inspected a conflict-free merge tree against current origin/main (9213090f6076bf3b7667b9b984752b3e47ef8f2f). The focused interaction/geometry/contrast coverage matches the behavior, and CI is green at the reviewed head.

One deliberate tradeoff is that the single-flight restart lock silently ignores clicks on another agent while a restart is underway; the author has explicitly confirmed that presentation/behavior as intentional in the existing review thread, so I am not treating it as a blocker.

[wesbillman]

Reviewed commit 377d3c114aa15967a44478849ff3497450929fd1 adversarially. No blocking findings.

I traced the new gallery Restart action through respawnManagedAgentWithRules and the Rust start command, checked active/inactive/error state selection, and reviewed the animated capsule mask geometry plus its E2E coverage. The apparent provider-backed restart concern does not materialize: needs_restart is derived only from a tracked local runtime pair (runtime.rs), so provider-backed records cannot expose this new Restart pill; repeated provider starts are separately documented as idempotent update-in-place deploys.

The existing single-flight behavior can silently discard a click on another Restart pill while one restart is pending. That tradeoff is already documented in the existing review thread and explicitly confirmed by the author as intentional, so I am not duplicating it as a new finding. CI is green at the reviewed head.