wt-switch-create

Arguments: `$ARGUMENTS`. Grammar: `[<branch>] [<repo>] [-- <task>]`. - **branch** — optional; the branch name for the new worktree. When omitted, pick one (step 1 below). - **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. Tokens before the `--` are the branch and/or repo: a path-shaped token (starting with `/`, `~`, `./`, or `../`) is the repo; any other token is the branch (`docs` is a branch name, never the `docs/` directory). More than one branch-shaped token before a `--` doesn't fit the grammar — ask. Without a `--`, judge where the task starts: leading tokens that read as a branch name (`fix-auth`) or a repo path are consumed as such, and the rest is the task; otherwise the whole input is the task (`fix the parser bug` has no branch-shaped lead — all task). ``` /wt-switch-create my-feature -- fix the parser bug /wt-switch-create -- fix the parser bug /wt-switch-create my-feature ~/workspace/other-repo -- fix the parser bug /wt-switch-create my-feature ``` ## What to do Creating the worktree comes first on every invocation, before any other work. The invocation is itself the explicit request to create it; a research or read-only task gets one all the same. <!-- Maintainers: rationale.md (same directory) covers the harness rules and design choices behind this — read it before re-adding guards or routes. --> 1. *...