The shell-level `export PROWL_WORKTREE_PATH=...` prefix was prepended to every script and setup script, so each variable became its own shell command. Beyond the scrollback noise, the leading `export` statements fired their own `command_finished` events, which would trip auto-close on the first success before the user's actual command had a chance to run. Pass the same variables through Ghostty's `env_vars` surface config so the shell process starts with them already in its environment and no shell input is needed. `Worktree.scriptEnvironmentExportPrefix` is still used by the archive script path, which shells out through an external `/usr/bin/env bash` invocation, so that API is left untouched.