<essential_principles> Five rules that always apply to operating Workshop. These come first; every workflow assumes them.

The workshop is an isolation boundary. Processes running inside a workshop cannot reach host resources except through declared interface connections. State this when relevant; do not assume any specific workload runs inside.
State changes are async. Every mutating command produces a numbered change composed of tasks. To diagnose what happened, use workshop changes then workshop tasks <ID> — never guess.
Refresh is non-destructive; prefer it to remove+launch. If workshop refresh errors, rerun with --wait-on-error to pause in Waiting, investigate via workshop shell, then --continue (after fixing) or --abort (to revert). Constraint: --wait-on-error is single-workshop only.
Auto-connect vs manual-connect differs by interface. Mount and GPU auto-connect. Camera, desktop, ssh-agent, custom-device, and most tunnel cases require an explicit workshop connect <plug-ref> [<slot-ref>] after launch. If the user wants those, schedule the connect step — once, not per refresh: manual connections persist across workshop refresh (0.9.5+) and are re-wired only after workshop restore or remove+launch.
The project directory is mounted at /project/. Any path that needs to be visible to the workshop must be reachable under /project/. Working directories passed via workshop exec --cwd or workshop run --cwd use workshop paths. </essential_principles>

use-workshop