bug: /restart fails in sessions created with -w

Describe the bug

A Copilot CLI session started with copilot -w cannot recover after running /restart inside the session. The restart attempts to use both the worktree option and the existing session ID, which results in an option conflict.

Affected version

1.0.80

Steps to reproduce the behavior

1. From any Git repository, start Copilot CLI with an automatically created worktree:

   $ copilot -w
   Created worktree at /path/to/repo.worktrees/<generated-name> (branch <generated-name>)
   

2. Inside the session, run /restart.

3. Observe the error:

   error: option '-w, --worktree[=name]' cannot be used with option '--session-id <id>'
   

Expected behavior

/restart should restart or resume the current session successfully while retaining the existing worktree, without passing -w in conflict with --session-id.

Additional context

• Operating system: macOS
• Shell: zsh
• The session was started with the bare -w option, allowing Copilot CLI to generate the worktree name.

/restart の処理と、copilot -w で起動されたセッションのコマンド構築から始めてください。Issue の 3 つの手順で競合を再現し、-w と --session-id がどのように組み合わされているかを調べてください。/restart がオプションの競合なしに現在のセッションを再開し、生成された worktree を保持できれば完了です。