v0.0.21

Single fix surfaced by the v0.0.20 post-release dogfooding smoke test (the first time the plugin exercised its own commands against a real Copilot CLI install immediately after a release).

Fixed

• probeModelAvailability default timeoutMs 15000 -> 60000ms (#85). Running /copilot:setup --probe-models against Copilot CLI 1.0.40-0 immediately after v0.0.20 reported all 7 probed models as 'unknown — probe timed out after 15000ms' with no real availability signal. Measured cold-start of copilot -p "ping" --model gpt-5.5 was ~33s end-to-end (each one-shot CLI invocation re-loads agent skills + MCP servers before resolving the model — cold-start dominates). The 15s default (set in v0.0.7) was reliably below that.

  Bumped to 60s with a measurement comment in the source so future re-tunings are data-driven. Probes still run in parallel via Promise.all, so wall-clock cost of --probe-models is bounded by the slowest probe, not the sum. Default extracted to a DEFAULT_PROBE_TIMEOUT_MS module-level constant per project convention.

Process notes

First release directly verified by the v0.0.20 CONTRIBUTING.md pre-release smoke test. Post-fix probe result on a real account: 6 / 7 models OK, 1 (claude-opus-4.6-fast) correctly identified as unavailable via isModelUnavailableStderr and surfaced in the next-steps banner.

Test suite

174 / 173 pass / 1 skipped (unchanged — the change is a default-value bump; existing setup-probe.test.mjs cases use a fake Copilot binary with no real cold-start).

See merged PRs #85, #86 for the full review history (including the /pr-review consistency finding that turned the inline 60000 into a named constant).