Bump motely-wasm to 26.0.2

[OptimusPi]

motely-wasm ^26.0.0 → ^26.0.2 (latest on npm; no v27 published yet). Lockfile resolves 26.0.2. BASE_PATH=/Blueprint/ npm run build passes; dist/index.html points at /Blueprint/assets/…, favicon.svg lands at the root.

Not run in a browser.

🤖 Generated with Claude Code

https://claude.ai/code/session_01LVkdXW3VtzhXPeEtt366TS

---

Generated by Claude Code

[greptile-apps]

Confidence Score: 5/5

[High risk] Bumps a WebAssembly dependency and restructures CI/CD pipeline.

The PR appears safe to merge; no actionable issues were found.

What we checked:

• Pull requests cannot deploy: Both artifact upload and the entire deploy job exclude pull request runs.
• The installed package stays unchanged: The old and new lockfiles specify the same motely-wasm version, download URL, and integrity value.

Summary

Raises the minimum allowed motely-wasm version to 26.0.2 and separates the Pages build from deployment.

• The lockfile already resolved motely-wasm to 26.0.2; its package contents remain unchanged.
• Pull requests build without uploading a Pages artifact or deploying.
• Removes libc fields from optional native packages in the lockfile.
• No actionable issues found. No build or browser checks were run during this review.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A[Push, pull request, or manual run] --> B[Install dependencies and build]
  B --> C{Pull request?}
  C -->|Yes| D[Finish without deployment]
  C -->|No| E[Upload Pages artifact]
  E --> F[Configure Pages]
  F --> G[Deploy to GitHub Pages]

Loading

_{Reviews (1) · Last reviewed commit: "Build on PRs, deploy only on push"}