[Website] Give failed Blueprint runs an explicit recovery path

[adamziel]

Builds on #4134.

A stored Blueprint can fail before its first WordPress file copy completes. The old error dialog could be dismissed, leaving a loading screen that could never finish.

This PR makes the error dialog the recovery screen. It keeps the specific failure reason and offers two explicit actions:

• Edit Blueprint opens the Blueprint editor so the input can be corrected.
• Return to your last Playground discards the failed run and restores the Playground that launched it.

If that Playground no longer exists, the second action starts a new one instead. Seamless mode omits the editor and makes the return action primary.

The dialog cannot be closed with an X, Escape, or an outside click. Close does not secretly navigate. Private repository authentication may cover it temporarily; the recovery dialog returns when authentication closes.

Reloading an interrupted run also stops before booting WordPress again. It keeps the return target and does not delete the partial files behind the user's back.

Desktop before	Desktop after

Mobile before	Mobile after

Testing

1. From a stored Playground, run a Blueprint with preferredVersions.wp set to 999.9.
2. Confirm the failure dialog shows the unavailable version, keeps Troubleshoot with AI, and cannot be dismissed.
3. Open Edit Blueprint, close the editor, and confirm the failure dialog returns.
4. Choose Return to your last Playground and confirm the original Playground opens and the failed run is absent from Recent.
5. Repeat at a mobile viewport.

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Adds an explicit recovery path for failed/interrupted stored Blueprint runs so reloads don’t silently retry or strand the user behind a dead loader.

Changes:

• Adds a unit test asserting interrupted Blueprint candidates require an explicit retry.
• Enhances the site error modal to present “Edit Blueprint” and “Return to your last Playground / Start a new Playground” actions for unfinished Blueprint runs.
• Makes the error modal non-dismissible for unfinished Blueprint runs to prevent revealing a dead loader via close/outside/Esc.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File	Description
packages/playground/website/src/lib/state/redux/boot-site-client.spec.ts	Adds coverage for “interrupted Blueprint run requires explicit retry” behavior.
packages/playground/website/src/components/site-error-modal/site-error-modal.tsx	Implements recovery UX/actions and prevents dismissing the modal for unfinished Blueprint runs.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.