What problem does it solve? Environment variable changes often silently break panel UIs, docker-compose fallback chains, or CORS allowlists because a commented .env.example entry, a wrong shell fallback syntax, or a hardcoded port goes unnoticed until runtime. ## Core Features & Use Cases - Env editing rules: Enforces uncommented .env.example entries, ${VAR:-fallback} colon syntax in docker-compose.yml, and per-worktree port variables instead of hardcoded ports. - Three-mode validation: Ensures every variable resolves correctly across worktree dev, panel preview, and production modes. - Debugging playbook: Diagnoses common failures such as panel UI hiding fields, containers missing variables, NEXT_PUBLIC_* changes not applying, and CORS rejections. - Use Case: When adding a new WEB_ORIGIN variable for CORS, follow the checklist to update root and app .env.example files, the compose fallback chain, and the three-mode comment block so the panel Envs page and all deployment modes keep working. ## Quick Start Review my changes to .env.example and docker-compose.yml and verify the new environment variable resolves correctly in worktree dev, panel preview, and production modes.