apps/vscode: VSIX packaging fails on main — bare "immer" import remains in extension.js

[matthiasgoergens]

Problem

pnpm -C apps/vscode run build && pnpm -C apps/vscode run package:platform fails on current main (checked at d1a46db):

VSIX packaging failed: Bare runtime dependency "immer" remains in extension/dist/extension.js.

The built dist/extension.js keeps a top-level import { ... } from "immer", which scripts/vsix-verify.mjs rejects.

Cause

• refactor(agent-core-v2): replace defineOp/Model with Event2 dispatch and replayable states #2909 added immer imports to packages/agent-core-v2 (e.g. src/state/state.ts, src/agent/contextMemory/loopEventFold.ts); agent-core-v2 declares immer as a dependency.
• feat(vscode): switch the extension to the v2 engine with a rollback switch #2916 switched the extension to the v2 engine, so agent-core-v2 is now bundled into extension.js.
• apps/vscode/tsdown.config.ts externalizes package.json dependencies by default and only force-bundles @moonshot-ai/* and zod, so immer stays a bare import in the extension bundle.

Suggested fix

Add immer to alwaysBundle in apps/vscode/tsdown.config.ts:

alwaysBundle: [/^@moonshot-ai\//, "zod", "immer"],

With that one-line change, build + package:platform succeed locally (all platform targets verified).

Worth checking whether CI exercises package:platform on main — the 0.7.2 release presumably packaged from a state before this combination, so a release cut from current main may hit this.