✨ feat(devcontainer): add multi-environment configs for VS Code, Codespaces, and JetBrains

[codekiln]

Summary

Adds three separate devcontainer configurations optimized for different development environments:

Config	Location	Workspace	Secrets	File Watching
VS Code Local	Default .devcontainer/	Bind mount	.env file	gRPC FUSE
Codespaces	.devcontainer/codespaces/	Cloud-managed	GitHub secrets	Cloud-managed
JetBrains	.devcontainer/jetbrains/	Named volume + .devcontainer bind	.env via bind	Native inotify

Why Three Configurations?

• VS Code Local: Bind mounts project from host, uses local .env file
• Codespaces: Cloud-based, no local files - .env is gitignored and doesn't exist in cloud, must use GitHub Codespaces secrets
• JetBrains: Needs named volume for native inotify support (avoids gRPC FUSE warnings), but also needs access to local .env file via hybrid mount

Changes

• Add codespaces/ config that works without .env file (uses GitHub secrets directly)
• Add jetbrains/ config with hybrid mount (named volume for workspace, bind mount for .devcontainer)
• Add X11 libraries to Dockerfile for JetBrains Gateway compatibility (libxext6, libxrender1, libxtst6, libxi6, libfreetype6)
• Update README with three-config architecture documentation
• Mark override file approach as deprecated for JetBrains users

Test Plan

• VS Code local: Default config still works with "Reopen in Container"
• Codespaces: Create Codespace and select codespaces/devcontainer.json
• JetBrains Gateway: Clone Repository workflow with jetbrains/devcontainer.json
• Verify JetBrains shows named volume (not grpcfuse): mount | grep /workspace

Fixes #718

🤖 Generated with Claude Code

[github-actions]

Unit Test Results

186 tests  ±0   186 ✅ ±0   1s ⏱️ ±0s
  1 suites ±0     0 💤 ±0 
  1 files   ±0     0 ❌ ±0 

Results for commit 5545f1f. ± Comparison against base commit 47eb92a.

♻️ This comment has been updated with latest results.

[github-actions]

SDK Integration Test Results

294 tests  ±0   294 ✅ ±0   34s ⏱️ -13s
 13 suites ±0     0 💤 ±0 
  1 files   ±0     0 ❌ ±0 

Results for commit 5545f1f. ± Comparison against base commit 47eb92a.

♻️ This comment has been updated with latest results.

[github-actions]

Integration Test Results

315 tests  ±0   311 ✅  - 4   4m 36s ⏱️ -31s
 13 suites ±0     0 💤 ±0 
  1 files   ±0     4 ❌ +4 

For more details on these failures, see this check.

Results for commit 5545f1f. ± Comparison against base commit 47eb92a.

♻️ This comment has been updated with latest results.

[Copilot]

Pull request overview

This PR introduces a multi-environment devcontainer architecture with three separate, optimized configurations tailored to different development tools and workflows: VS Code (local), GitHub Codespaces, and JetBrains Gateway.

Key Changes:

• Added dedicated Codespaces configuration that works exclusively with GitHub secrets (no .env file dependency)
• Added dedicated JetBrains configuration with hybrid mount approach (named volume for workspace + bind mount for .devcontainer folder) to resolve gRPC FUSE file watching issues
• Enhanced Dockerfile with X11 libraries required for JetBrains Gateway compatibility
• Updated documentation to explain the three-config architecture and deprecate the manual override file approach for JetBrains users

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
.devcontainer/jetbrains/docker-compose.yml	New JetBrains-specific compose config with hybrid mount strategy (named volume for workspace, bind mount for .devcontainer to access .env file)
.devcontainer/jetbrains/devcontainer.json	New JetBrains devcontainer configuration referencing the JetBrains-specific docker-compose file
.devcontainer/codespaces/docker-compose.yml	New Codespaces-specific compose config that uses GitHub secrets directly without .env file dependency
.devcontainer/codespaces/devcontainer.json	New Codespaces devcontainer configuration with VS Code extensions and settings
.devcontainer/README.md	Comprehensive documentation update explaining the three-config architecture, setup steps for each environment, and trade-offs
.devcontainer/docker-compose.override.yml.template	Updated with deprecation notices directing JetBrains and Codespaces users to dedicated configurations
.devcontainer/Dockerfile	Added X11 libraries (libxext6, libxrender1, libxtst6, libxi6, libfreetype6) required for JetBrains Gateway support

The changes are well-structured, properly documented, and follow consistent patterns across all configurations. Each environment's unique requirements (bind mounts vs named volumes, .env files vs GitHub secrets) are appropriately addressed. No issues were identified during the review.

[Copilot]

Pull request overview

Copilot reviewed 8 out of 8 changed files in this pull request and generated 2 comments.

[codekiln]

@copilot open a new pull request to apply changes based on the comments in this thread

[Copilot]

@codekiln I've opened a new pull request, #722, to work on those changes. Once the pull request is ready, I'll request review from you.

[codekiln]

In jetbrains:

[post-create] Skipping gh CLI extensions (will be installed after authentication)
[post-create] Setting up tmux configuration...
/workspace/.devcontainer/post-create.sh: line 132: cd: /workspace/.devcontainer: No such file or directory
Lifecycle script command: `bash /workspace/.devcontainer/post-create.sh` is failed with exit code: 1
bash: /workspace/.devcontainer/setup-github-auth.sh: No such file or directory
Lifecycle script command: `bash /workspace/.devcontainer/setup-github-auth.sh` is failed with exit code: 127

This was using the VCS clone method.

I think there's a conceptual difference between how we need to configure vcs clone method in jetbrains and how it works in VS Code because the .env file will just not be there before it's cloned. It's more like codepsaces, but without the ability to define the environment variables ahead of time.