[Website] Skip incomplete OPFS site directories during startup listing

[adamziel]

An interrupted first save can leave an OPFS site-* directory behind before wp-runtime.json is written. Startup treated every directory as a stored Playground and logged a NotFoundError while listing it.

Skip missing or mismatched OPFS entries during startup listing. Other read failures still reach the existing error log.

Before	After

The after capture reloads with site-funny-sunny-country still present without wp-runtime.json; the console filter has no matching startup error.

Testing

Reload with a metadata-less directory under OPFS /sites and confirm startup skips it without a site-read console error.

[Copilot]

Pull request overview

Note

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

Prevent noisy startup errors by skipping OPFS site-* directories that are missing required metadata (e.g., from an interrupted first save), while preserving existing logging for other read failures.

Changes:

• Skip OPFS entries when listing sites if the read fails with NotFoundError or TypeMismatchError.
• Add a unit test ensuring incomplete directories are ignored without logging.
• Mock @php-wasm/logger in tests to assert no error logs for the skipped case.

Reviewed changes

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

File	Description
packages/playground/website/src/lib/state/opfs/opfs-site-storage.ts	Skips missing/mismatched OPFS entries during startup listing to avoid spurious errors.
packages/playground/website/src/lib/state/opfs/opfs-site-storage.spec.ts	Adds coverage for interrupted-save directories and asserts logger is not called.

---

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