[Website] Replace failed Blueprint runs before pruning autosaves

[adamziel]

Part of #4099.

Builds on #4129.

Retrying an unfinished Blueprint run now replaces the failed Playground before autosave pruning begins.

The retry keeps the original Playground as its return target, creates and activates the replacement, and then removes the failed run. Only after that succeeds does it prune old autosaves. If the failed run cannot be removed, pruning stops instead of deleting an unrelated Playground to make room.

Autosave pruning already handles its own deletion failures, so the Blueprint editor no longer wraps it in a second try/catch. The editor also stops claiming that the failed run will remain in Recent after retry.

Testing

From a stored Playground, run a Blueprint with preferredVersions.wp set to 999.9. Open the failed run in the Blueprint editor, change the version to latest, and run it again. Confirm the replacement opens, the original Playground remains, and the failed run is absent from Recent.

[Copilot]

Pull request overview

Note

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

Adjusts Blueprint retry behavior so failed/unfinished runs are replaced (and the failed run discarded) before autosave pruning, preventing unrelated Playgrounds from being deleted and updating UI messaging accordingly.

Changes:

• On retry, activates the replacement site and attempts to remove the failed run before pruning autosaves (and aborts pruning if removal fails).
• Updates the Blueprint editor hint text logic to avoid implying failed runs will remain in Recent after retry.
• Extends unit tests to cover removal-before-prune ordering and the “do not prune if removal fails” case.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
packages/playground/website/src/components/blueprint-editor/BlueprintBundleEditor.tsx	Reorders retry flow to remove failed runs before pruning; adjusts run-hint rendering for unfinished runs.
packages/playground/website/src/components/blueprint-editor/BlueprintBundleEditor.spec.tsx	Adds tests ensuring removal happens before pruning and pruning is skipped if removal fails.

Comments suppressed due to low confidence (1)

packages/playground/website/src/components/blueprint-editor/BlueprintBundleEditor.tsx:1

• If removeSite / pruneAutosavedSites are async thunks (e.g., created with RTK createAsyncThunk), dispatch(thunk) typically resolves to an action and does not throw on rejection unless unwrapped. In that case, the catch block won’t run and pruning may still proceed even when removal failed—contradicting the intended safety behavior. Consider unwrapping the dispatched promise (or explicitly checking for a rejected action) so failures reliably abort pruning.

import { autocompletion } from '@codemirror/autocomplete';

---

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