[mvanhorn]

Motivation

Opening the remote development container did not provide a ready-to-use SpecForge environment. Python and pip could resolve to different environments, and contributors had to install project dependencies manually. The container inherited SGLang’s shell configuration without explicitly selecting a SpecForge virtual environment or installing SpecForge’s dependencies. It also lacked an editable installation connecting the mounted checkout to the Python environment.

Modifications

The container now uses a pinned SGLang base image and a dedicated Python 3.11 environment, with project and development dependencies installed in a cacheable layer. Shell configuration and VS Code select that environment, while container creation repairs its ownership after UID/GID remapping and installs SpecForge and the capture plugin editably. The new walkthrough covers remote setup, environment checks, dataset preparation, model access, and the external capture services required for training.

Related Issues

Closes #402

Accuracy Test

repo_lint was run twice; the transcript shows no output or exit status.
pre-commit run --all-files --show-diff-on-failure was invoked; the transcript contains no result confirming whether it passed.

Benchmark & Profiling

Not applicable to this change.

Checklist

• Format your code according to the Code Formatting with Pre-Commit.
• Add unit tests as outlined in the Running Unit Tests.
• Update documentation / docstrings / example tutorials as needed, according to Writing Documentation.
• Provide throughput / latency benchmark results and accuracy evaluation results as needed, according to Benchmark and Profiling and Accuracy Results.
• For reviewers: If you haven't made any contributions to this PR and are only assisting with merging the main branch, please remove yourself as a co-author when merging the PR.
• Please feel free to join our Slack channel at https://sgl-fru7574.slack.com/archives/C09784E3EN6 to discuss your PR.