wt-switch-create

Arguments: `$ARGUMENTS`. Grammar: `<branch> [<repo>] [-- <task>]`. - **branch** — required first token; the branch name for the new worktree. - **repo** — optional path; create the worktree in this repo instead of the session's current one. - **task** — optional; what to do inside the new worktree. No task means enter the worktree and wait. Without a `--`: a path-shaped second token (absolute, `~`-relative, `./`- or `../`-relative, or an existing directory) is the repo, and the task starts after it. Otherwise the task starts at the second token. ``` /wt-switch-create my-feature -- fix the parser bug /wt-switch-create my-feature ~/workspace/other-repo -- fix the parser bug /wt-switch-create my-feature ``` ## What to do 1. **First action — before reading any files or running any commands:** - If a repo was given, `cd` into it first with a `Bash` call (the working directory persists for the rest of the session). `EnterWorktree` has no repo parameter — it creates the worktree wherever the session is rooted. - Then call `EnterWorktree({name: "<branch-name>"})`. This re-roots the session into the new worktree. If a repo was given, confirm the new worktree landed under it; if not, the `cd` didn't take — report it and stop. - It works because this plugin maps `WorktreeCreate` → `wt switch --create <name> --no-cd --format=json`, so the new worktree lands in worktrunk's normal sibling layout (`<repo>.<branch>/`), not under `.cl...