Dashboard build fails inside install-smoke Docker container (rollup handleInvalidResolvedId)

[webdevtodayjason]

Discovered during 2026-05-26 install-smoke run.

The hosted installer's pnpm build step for the dashboard fails inside the smoke's Docker container with a rollup handleInvalidResolvedId error. The installer warns and continues — dashboard just isn't available on port 8080 in the container — so the smoke proceeds, but it surfaces something that may affect real new-operator installs too.

```
[0;36m →[0m Building dashboard...
at Object.logger [as onLog] (file:///root/argentos/dashboard/node_modules/.pnpm/rollup@4.60.4/node_modules/rollup/dist/es/shared/node-entry.js:23385:9)
at ModuleLoader.handleInvalidResolvedId (file:///root/argentos/dashboard/node_modules/.pnpm/rollup@4.60.4/node_modules/rollup/dist/es/shared/node-entry.js:22129:26)
at file:///root/argentos/dashboard/node_modules/.pnpm/rollup@4.60.4/node_modules/rollup/dist/es/shared/node-entry.js:22087:26
[1;33m ⚠[0m Dashboard build failed — run later: cd ~/argentos/dashboard && npx vite build
[1;33m ⚠[0m Dashboard build output missing — dashboard will not be available on port 8080
```

The full stack trace isn't captured in the visible output. To repro, run the smoke and grep the log for handleInvalidResolvedId.

Open questions:

• Is this Docker-container-specific (something about the bookworm-slim node:22 base image) or would it bite real Mac operators too?
• Is it a missing dep that's only installed on macOS through Homebrew or some other side channel?
• Does the dashboard build succeed locally for the operator? If yes, the difference between local and container env is the root cause to chase.

Discovered during v2026.5.6.6 install-smoke validation.

[alucard210319]

Hi, I can help narrow this down.

Since the visible smoke log only shows Rollup handleInvalidResolvedId, I would first reproduce the dashboard build inside the same Docker/container path and capture the full unresolved import. Then I would keep any PR limited to the missing dependency, import, or config issue.

If paid outside help is appropriate, I can do a root-cause pass for $15, then quote a focused PR only if the fix is actually small.