[ENHANCEMENT] Add devcontainer config #8978
Description
Problem (one or two sentences)
Users who clone the repo have to manually install matching Node.js and pnpm versions because there is no .devcontainer configuration, slowing down onboarding.
Context (who is affected and when)
New contributors and teammates hit this when opening the project in VS Code or trying to run setup commands for the first time.
Desired behavior (conceptual, not technical)
Opening the repo in VS Code should offer a ready-to-use Dev Container so contributors can develop immediately with the correct toolchain.
Constraints / preferences (optional)
Keep setup lightweight and compatible with existing pnpm workflows; include recommended extensions for linting/formatting.
Request checklist
- I've searched existing Issues and Discussions for duplicates
- This describes a specific problem with clear context and impact
Roo Code Task Links (optional)
No response
Acceptance criteria (optional)
Given a fresh clone of the repository
When I open it in VS Code and choose “Reopen in Container”
Then the workspace builds a Dev Container with the required Node.js and pnpm versions
And I can run pnpm install, pnpm lint, and pnpm test without additional setup
But it should not add extra manual steps for developers who prefer working outside containers
Proposed approach (optional)
Provide a .devcontainer/devcontainer.json that pins the toolchain, configures pnpm cache mounts, runs installs automatically, and recommends relevant extensions.
Trade-offs / risks (optional)
Maintaining the Dev Container requires keeping base images and tool versions in sync with the project; some contributors may still prefer native setups.