Hide the Home run button after navigating into project details

[AmyShang-alt]

Summary

After sending a prompt from the Home page and navigating into the project details page, the Home page run button follows into the project details view instead of automatically hiding.

Current behavior

When the user starts a generation from Home, the run control from the Home composer remains visible after the app transitions into the project details page. The control appears to be carried across the navigation boundary rather than being dismissed or re-rendered for the new page context.

Expected behavior

The Home page run button should not remain visible after entering the project details page. When navigation happens, the Home composer controls should either:

• Automatically hide, or
• Reset to the correct controls for the project details view.

The project details page should not show stale Home page controls.

Steps to reproduce

1. Open the Home page.
2. Enter a prompt and click Send to start a generation.
3. Let the app navigate into the generated project details page.
4. Observe the run button from the Home page still visible in the project details view.

Notes

A screen recording was provided showing the Home run button following the send action into the project details page instead of hiding.

Why this matters

This makes the page transition feel broken and can confuse users about which page or generation state the run control belongs to.

20260629-112020.mp4

[lefarcen]

Hey @AmyShang-alt — this repro is clear. After Home creates the project and routes into /projects/:id, the Home composer submit control should be torn down and the project-detail composer should be the only visible run surface, so this looks like a route-transition cleanup bug rather than intended carry-over.

The current labels make sense here, and the likely fix area is the Home → project handoff so the Home submit state gets cleared as soon as ProjectView takes over.

[lefarcen]

If anyone from the community wants to take this on, comment /claim and we’ll route it to you.
It looks reasonably scoped around the Home → project composer handoff.

[roian6]

/claim

[lefarcen]

Thanks for picking this up, @roian6 🙌 Roughly how long do you think it’ll take — a few hours, 1–3 days, about a week, or longer?

[lefarcen]

@AmyShang-alt — PR #4886 is up from @roian6 for this.

The proposed fix returns EntryShell's onCreateProject(...) promise so the Home composer keeps its in-flight Sending…/disabled state until project creation and navigation finish, which matches the handoff bug described here. Keeping this issue open until the PR lands.