Stored reload behavior
Saved Playgrounds keep limited settings and use Save & Reload. Temporary Playgrounds show Apply Settings & Reset because files and database are replaced.
Pending change: WP latest -> 6.9, PHP 8.3 -> 8.2, en_US -> pl_PL, network on -> off.
Unsaved reset warning
If the active site were Unsaved Playground, applying this change would reset WordPress, database, files, logs, and the current path.
Reload saved runtime?
The browser-saved Playground will reload with the selected WordPress, PHP, language, and network settings. Unsaved runtime changes are discarded, but the saved identity remains.
Preparing stored reload...
Last completed runtime
WP latest, PHP 8.3, English, network access allowed.
Replacement guard
Starting or importing over an unsaved Playground asks whether to cancel, save first, or replace the current runtime.
Representative visible subset from the current 43 Blueprint gallery.
Art Gallery
Validate JSON, warn about replacing current content, then run into the active Playground.
Schema valid. Ready to run.
Transfer result
No portability action is running.