What

Repair the qqbot bundled plugin dependency closure so packaged desktop builds include silk-wasm, and fail packaging early if the qqbot plugin is incomplete.

Why

Upgraded packaged installs could keep an incomplete openclaw-qqbot runtime plugin, leaving QQ stuck in a restarting/starting state with Cannot find module 'silk-wasm' during plugin preload.

How

• Start qqbot bundled dependency collection from the plugin's own node_modules before falling back to the pnpm virtual-store parent.
• Add a regression test covering qqbot bundled runtime dependencies during extension materialization.
• Add controller sidecar packaging checks for openclaw-qqbot/node_modules/silk-wasm/package.json.
• Add mac packaged-app validation to ensure the final .app includes the qqbot silk-wasm dependency.

Affected areas

• Desktop app (Electron shell)
• Controller (backend / API)
• Web dashboard (React UI)
• OpenClaw runtime
• Skills
• Shared schemas / packages
• Build / CI / Tooling

Checklist

• pnpm typecheck passes
• pnpm lint passes
• pnpm test passes
• pnpm generate-types run (if API routes/schemas changed)
• No credentials or tokens in code or logs
• No any types introduced (use unknown with narrowing)

Notes for reviewers

• I ran the targeted regression test: pnpm --filter @nexu/controller exec vitest run tests/openclaw-runtime-plugin-writer.test.ts.
• I also built an Apple Silicon unsigned zip and verified the packaged app contains runtime/controller/plugins/openclaw-qqbot/node_modules/silk-wasm/package.json.
• I did not mark full pnpm test as passing because the current main branch already has unrelated failing tests.