start-work should take a config to let users set their default value for --no-worktree

Hey — would you consider adding a config option to start-work that lets a user pin --no-worktree as their default?
▎ Right now it's a per-invocation flag, but I never want to use worktrees: my git GUI (GitKraken) chokes when
▎ worktrees live under .claude/worktrees/ inside the repo (EISDIR walking the nested .git pointer file), and even
▎ after gitignoring the path, viewing uncommitted WIP from the main checkout isn't possible across worktrees. I'd
▎ rather have the branch in my main checkout where my tooling already works.
▎
▎ Proposed shape: a setting in settings.json like "start-work": { "defaultMode": "in-place" } (or whatever fits your
▎ convention), and the script reads it and passes --no-worktree through if set. Worktree stays the default for anyone
▎ who doesn't set it, so this is purely additive — no behavior change for current users.

Start at the start-work entry point and inspect how settings.json is read and how the existing --no-worktree flag is passed through. Add the proposed default configuration while preserving worktrees for users without it, then run the available start-work checks or exercise both configured and default modes.