Layer the frontend toolchain on top of the existing release builder
image so a single container covers Go, C support-layer and web
development, with the builder image remaining the single source of
truth for the cross toolchain, Go and MaixCDK.
- Mount the workspace at /home/build/NanoKVM, where the Makefile and
support/sg2002/build expect it, and resync MaixCDK components via
update_lib on create so C builds never use stale sources
- Install Node from official dist tarballs (integrity-checked, pinned
to the major used by CI), with NODE_DIST_MIRROR / NPM_REGISTRY /
BASE_IMAGE build args for restrictive or mirrored corporate networks
- Export the MaixCDK virtualenv via remoteEnv so non-interactive
processes (tasks, extensions, exec) get it too; make
updateRemoteUserUID explicit since the published builder image bakes
the CI runner's uid
- Run pnpm non-interactively during post-create (no TTY) and give the
skeleton-less home a standard ~/.profile -> ~/.bashrc chain
- Make the web toolchain convention explicit via package.json engines
(Node >= 22, pnpm >= 11, matching CI) and document it in web/README
- Document the dev container in the README, point server/README at the
container flow that works on any host OS, and ignore .pnpm-store/
