Use inline Playground links for PRs

[akirk]

Keep the dist/main build for compatibility with existing public Playground links, but stop building per-PR dist branches. Pull requests now get Playground links generated from the PR's blueprint.json and demo.json via base64 data-url blueprints, with only this repository's install step rewritten to the PR head commit.

Because this PR changes the pull_request_target workflow itself, GitHub will still run the old workflow from main for this PR until the change is merged.

The launchable blueprints are self-contained by installing WpApp directly from akirk/wp-app and writing the lightweight autoloader before activating memex.

Testing:

• actionlint .github/workflows/build-dist.yml .github/workflows/plugin-check.yml
• php -r 'foreach (array_merge(glob("blueprint*.json") ?: [], ["demo.json"]) as $file) { if (is_file($file)) { json_decode(file_get_contents($file), true, 512, JSON_THROW_ON_ERROR); } } echo "blueprints ok\n";'

WordPress Playground

Test this PR in WordPress Playground: Try this PR · Try with demo data

The linked blueprint loads the generated dist/pr-45 branch, including Composer dependencies.

[github-actions]

✅ WordPress Plugin Check Report

✅ Status: Passed

📊 Report

All checks passed! No errors or warnings found.

---

🤖 Generated by WordPress Plugin Check Action • Learn more about Plugin Check