loop uses obsolete gh copilot --message flag #874

Bug

loop and related watch/execute paths invoke gh copilot --message ..., but the currently installed GitHub CLI Copilot integration on this machine accepts -p rather than --message.

This causes the loop to fail immediately even when the squad setup itself is healthy.

Environment

• @bradygaster/squad-cli: 0.9.4-insider.1
• OS: WSL2 Ubuntu / Linux
• Node: v22.22.1
• npm: 10.9.4
• GitHub CLI: authenticated and working
• gh copilot --help shows prompt usage as gh copilot -p "..."

Repro

1. Create a valid loop.md with configured: true
2. Run:

npm exec squad -- loop

Actual

The first round starts and then fails with:

error: unknown option '--message'
Try 'copilot --help' for more information.

The failing constructed command is effectively:

gh copilot --message "...loop prompt..."

Expected

loop should invoke the installed gh copilot in a way that is accepted by the current CLI.

Evidence

On this machine:

gh copilot --help

shows examples like:

gh copilot -p "Summarize this week's commits"

and does not document --message.

Root Cause

The installed Squad CLI still hardcodes --message in multiple places, including:

• dist/cli/commands/loop.js
• dist/cli/commands/watch/index.js
• dist/cli/commands/watch/capabilities/*.js

Example from the installed code:

const args = ['copilot', '--message', prompt];

Local workaround

Replacing --message with -p in the installed CLI allowed the loop to get past the previous immediate failure and begin Round 1 successfully.

Suggested fix

Update the CLI integration points to use the currently supported gh copilot prompt flag shape, or centralize the Copilot command construction behind a compatibility layer so this does not break again when GitHub CLI changes.