Snapshots Support

Let's define the relationship between Snapshots and Blueprints.

• When writing Blueprints, it's useful to include some files, e.g. private plugins. If Blueprints required shipping them in wp-content/plugins, that starts resembling a Snapshot.
• A Snapshot exported from WordPress could include a Blueprint like {"theme": "twentytwentythree"} instead of shipping the actual files. That's a smaller archive and an up-to-date theme import.

Blueprints and Snapshots are a spectrum, not distinct ideas

The smallest WordPress setup description is an empty Blueprint {}.

The most extensive description is a full Snapshot + Playground binary bundled as a double click executable – click, and that exact site runs on your computer.

There's so much in between, though:

• A Blueprint file with some plugins, themes, and site options
• A Blueprint file + a wp-config.php
• A Blueprint file with a few plugins + wp-content with more plugins and themes
• A full snapshot with a Blueprint to update the WordPress version

No file, test, or entry point is named. Start by reading the Blueprint and Snapshot examples in the issue and the repository context, then clarify how their contents should relate across the described spectrum. Done means an agreed relationship and an actionable implementation scope.