Bug: native Copilot memory provider is unconditionally rejected despite conditional help (v1.0.1) #2193

Environment

Homebrew standalone Squad CLI/SDK 1.0.1, macOS arm64, bundled Node.js v22.20.0.

Reproduction

Run in a project with an existing .squad/ directory:

squad memory provider --provider copilot
echo $?

The command exits 1 and prints an error with a stack trace, beginning:

Error: Real Copilot Memory API unavailable: no concrete callable API was found in installed @github/copilot SDK/tooling.

The provider handler unconditionally throws for --provider copilot and --default-copilot; it does not probe for a callable API. Meanwhile, the memory usage text says the command fails unless a real Copilot Memory API module is present.

Expected / suggested fix

Align provider behavior and help: either detect and use a supported concrete API, or explicitly document that native Copilot Memory is unsupported in this release and report that limitation without a stack trace. Keep the host-injected adapter clearly distinguished from native Copilot persistence.

Source

memory.ts at v1.0.1: REAL_COPILOT_UNAVAILABLE_REASON, the provider branch in runMemoryCommand, and its usage text.