v1.24.0 — browser viewer

Browser viewer

The 3D preview now runs in any browser, not just a VS Code webview. New open_viewer / close_viewer MCP tools start a local HTTP + WebSocket host and return a URL — point a browser (or the Claude Code browser pane) at it and you get the full viewer: parts panel, parameter sliders, section plane, measure, STEP/STL export, and live reload on save.

set_render_mode, toggle_dimensions and open_shape drive it too. The SubscriberBus gained in-process subscribers, so those existing tools reach browser viewers without any change at their call sites.

Works from a plain npx -y @shapeitup/mcp-server install: the package ships the two browser bundles (~1.3 MB gzipped) and resolves the OCCT/Manifold/MuJoCo wasm from node_modules, where they already are as ordinary dependencies.

Fixes

• Plugin skills never loaded. The marketplace entry pointed at ./skills while the repo had skill/, and the layout was wrong — a skill is a directory containing SKILL.md. Now skills/shapeitup/SKILL.md.
• The skill was not scoped. Frontmatter said globs:, which is not a Claude Code field and was silently ignored. The field is paths:.
• Plugin version drift. The marketplace entry was pinned at 1.3.0 against packages at 1.23.0.
• MCP config was never read. mcpServers lived in .claude/settings.json, which is not a location Claude Code loads MCP servers from. Moved to .mcp.json.
• Build was broken on pnpm 11. The build-script allowlist moved to pnpm-workspace.yaml; CI now pins pnpm 11 to match.

release-check gained guards for the plugin version, the skills path layout, and the presence of the browser bundles in the npm package — each of these failed silently before.