chore(deps): bump @tschk/moonshine packages to 0.4.0

[undivisible]

moonshine 0.4.0 release

---

Note

Medium Risk
Upgrading the moonshine stack can affect build, SSR, and routing behavior even without local code edits; verify dev/build/deploy after install.

Overview
Bumps all nine @tschk/moonshine* dependencies in website/package.json from ^0.3.1 to ^0.4.0 for the moonshine 0.4.0 release. No application source changes are included—only the declared version ranges for core, compiler, framework, React, router, server, shaders, deploy-bun, and adapter-conformance packages.

^{Reviewed by Cursor Bugbot for commit 87a4501. Configure here.}

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 87a450133a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Regenerate the Bun lockfile with the dependency bump

The website workflow at .github/workflows/ci.yml:40 runs bun install --frozen-lockfile; Bun's bun install --help describes this flag as “Disallow changes to lockfile.” Because website/bun.lock:8-16 still records all nine Moonshine ranges as ^0.3.1 and resolves the 0.3.x packages, installing this manifest requires changing the lockfile, so the website gate stops during dependency installation before typechecking or tests. Regenerate and commit website/bun.lock alongside this bump.

Useful? React with 👍 / 👎.