docs(sandbox): per-environment settings are not bundle changes
A full turbo typecheck on a 16 GB box with no swap is OOM-killed at turbo's default fan-out (measured 2026-09-28: 16.6 GB peak, marketing tsc SIGKILL; concurrency 4 peaks at 10.5 GB and passes). The fix for our own environment is TURBO_CONCURRENCY=4 set as an environment variable, which is now on "Satya's Superset" and verified through a box terminal: the shell sees it and typecheck finishes 42/42.
This PR only records the rule that came out of it in the sandbox README: something one environment needs is set on that environment and reaches its boxes through the managed environment; the bundle is what every customer's box runs.
https://claude.ai/code/session_01RL946q6aRucLVJs659sW24
Summary by cubic
Adds a rule to the sandbox README clarifying that environment-specific settings are not bundle changes. Something one environment needs, like TURBO_CONCURRENCY, is set on that environment and reaches its boxes through the managed environment; the bundle runs on every customer's box.
Summary by CodeRabbit
- Documentation
- Clarified how to configure environment-specific variables and repository limits, and when bundle changes take effect in customer boxes.