runner: regenerate pnpm artifacts

[demtario]

Task: https://app.clickup.com/t/9015210959/DEV-2025

Summary

The generated-artifacts half of the pnpm migration, stacked on #41. Reviewing #41 covers the logic; this PR is the regenerated output plus the one source-adjacent fix the regeneration required.

examples: refresh pnpm lockfiles for latest Handsontable specifiers (15 files)

fc4e169 switched every example's Handsontable deps to "latest" in package.json but left the lockfile specifiers pinned at 18.0.0. That made pnpm install --frozen-lockfile fail for every starter pair: the container image bake would break on the next regeneration, and every Tier-2 session was silently booting through the custom-metadata --no-frozen-lockfile fallback, bypassing the generated-starter lockfile guard. Lockfile-only refresh in all 15 examples; latest currently resolves to the same 18.0.0, so resolved dependency content is unchanged.

runner: regenerate pnpm artifacts (1360 files)

All four generated artifact sets, regenerated from current sources and verified idempotent (rerunning every generator yields zero diff):

• containers/live/ (23 files) — the corepack+pnpm Dockerfile and per-framework baked package.json + pnpm-lock.yaml pairs. This is the piece Bugbot flagged on runner: migrate example installs to pnpm #41: the boot script there runs pnpm against an npm-based image until this merges. All 11 baked pairs pass the same --frozen-lockfile check the Docker build runs.
• catalog.json — starters re-imported with the new cache exclusions (drops the 12 leaked .angular/cache/** files from the angular starter), the remix optimizeDeps fix, and consistent package/lockfile pairs.
• workers/api/src/frameworks.generated.ts — corrected nuxt dev command (--host, not -H) and dependency fingerprints that now genuinely match the catalog starters, restoring the strict frozen-install path at session boot.
• apps/authoring/public/docs-examples/ (1335 files) — docs-guide examples re-imported with the pnpm install commands.

Verified locally (end-to-end via wrangler dev)

• Fresh container sessions for react-js, mui, angular, nuxt, and remix (×2) all boot via the strict frozen-install path (no fallback lines in boot logs) and render the Handsontable grid; remix first loads are clean, nuxt serves the actual demo.
• HMR WebSocket + live file edits verified against the running containers.

Merge order

Merge this PR into feature/runner-pnpm-installs before #41 merges to its base — #41 is not deployable without these artifacts (see the Bugbot thread there).

🤖 Generated with Claude Code

---

Note

Medium Risk
Large generated surface area affects container image bakes and session boot (--frozen-lockfile); wrong merge order with the parent pnpm PR could leave deploys broken until both land.

Overview
Regenerates the runner’s pnpm migration outputs and fixes example lockfiles so frozen installs work again.

15 example pnpm-lock.yaml files now use latest specifiers for Handsontable packages, matching package.json after an earlier change left locks pinned at 18.0.0 (which broke pnpm install --frozen-lockfile and forced a non-frozen fallback at container boot).

Bulk regeneration (~1360 files) refreshes runner/containers/live/ (corepack + pnpm images and per-framework baked locks), catalog.json, frameworks.generated.ts (e.g. Nuxt dev host flags, fingerprints aligned with starters), and ~1335 docs-examples JSON bundles (installCommand → pnpm install, packageManager, Angular dev via pnpm exec ng serve). Docs accessibility demos also fix arrow-key checkbox copy/links (autoWrapRow vs autoWrapCol).

Resolved Handsontable versions stay 18.0.0 where latest currently points there; many lockfile diffs are specifier/metadata-only (e.g. Linux libc annotations).

^{Reviewed by Cursor Bugbot for commit 1233bc7. Bugbot is set up for automated code reviews on this repo. Configure here.}