Windows PowerShell: @ symbol in drone commands needs quoting — @branch parsed as PS array

[Input-X]

Bug

PowerShell treats @ as a special character (array/splatting operator). Running:

drone @prax monitor run

PowerShell interprets @prax as a variable reference, not a literal string. Drone receives monitor as the first arg instead of @prax.

Error: drone: unknown command 'monitor'

Workaround

Quote the argument:

drone '@prax' monitor run

Fix options

1. Document in README/setup output — tell Windows users to quote @branch args in PowerShell
2. Create a drone.ps1 wrapper — auto-detect and fix @ args before passing to the real drone
3. Accept prax without @ prefix — drone could treat drone prax monitor run as equivalent to drone @prax monitor run

Option 3 is probably best UX. Option 1 is simplest.

Not affected

• Git Bash on Windows (works fine)
• Linux/macOS bash/zsh (works fine)
• Only PowerShell has this issue

Found during Windows 10 setup testing.

[Input-X]

Solution implemented (two-part fix)

Part 1: PowerShell profile wrapper

Created WindowsPowerShell/Microsoft.PowerShell_profile.ps1 with a drone function that uses $MyInvocation.Line to capture the raw command text before PS parses @ as splatting. Passes raw args through cmd /c which doesn't have the @ problem.

function drone {
    $exe = Join-Path $env:AIPASS_HOME '.venv\Scripts\drone.exe'
    $raw = $MyInvocation.Line.Trim()
    if ($raw -match '^drone\s+(.+)$') {
        $argsPart = $Matches[1]
        $argsPart = ($argsPart -split '\s*\|\s*')[0].TrimEnd()
        cmd /c "`"$exe`" $argsPart"
    } else {
        & $exe
    }
}

Part 2: Bare branch name routing in drone.py

As a fallback (and convenience for any shell), drone.py now auto-routes bare branch names. drone prax monitor run = drone @prax monitor run. The existing detection at line 553 that used to print an error now calls _handle_target() directly.

Tested and confirmed working

• drone @prax monitor run — works in PS (via profile wrapper)
• drone prax monitor run — works everywhere (via bare name routing)
• drone systems — works from any directory (via AIPASS_HOME, see drone systems fails outside AIPass directory — _cwd_has_registry missing AIPASS_HOME fallback #316)

setup.sh should auto-install the PS profile on Windows — filed as separate issue.

[AIOSAI]

Fixed by #342 — the PS profile wrapper (Option 2 from this issue) is now written by setup.sh to ~/Documents/WindowsPowerShell/Microsoft.PowerShell_profile.ps1 on Windows installs. It re-parses $MyInvocation.Line to preserve @ before invoking drone.exe. Option 3 (auto-route bare branch names) was rejected — see issue #340 + comment in drone.py main() for the tradeoff reasoning.