chore: provider-state re-verify all 11 CLIs + copilot/minimax adapter drift fixes

[bbingz]

Summary

A provider-state-review Workflow (11 read-only probe agents → per-provider adversarial verify → synthesis, 23 agents) re-checked every provider CLI's live install + upstream + adapter contract on top of v0.6.27.

Headline: no version gaps, no breaking CLI drift. All 11 locals == upstream where comparable (claude 2.1.193 / gemini 0.49.0 / qwen 0.19.2 / copilot 1.0.65 / opencode 1.17.11 / pi 0.80.2 / cmd 0.40.8 / mmx 1.0.16 / kimi-code 0.19.1 / grok 0.2.64 / agy 1.0.12); every flag/auth/argv assumption verified intact against live --help.

Code fixes (with regressions)

• copilot resume contract — buildCopilotInvocation emits --session-id <id> instead of --resume <id> for resume-by-exact-id. copilot 1.0.65's -r, --resume[=value] takes an OPTIONAL =-attached value (or opens the session picker), so the prior space-separated form would not resume by id; --session-id <id> is the documented by-id flag. Reachable via ask/rescue --provider copilot --resume <id> (the companion sets resumeSessionId).
• minimax finish-reason — extractMiniMaxResponseFromMmxJson honours Anthropic-style stop_reason in the finishReason fallback (mmx speaks both the OpenAI finish_reason and Anthropic Messages stop_reason shapes; the parser already handles Anthropic content[]). Pure additive, zero regression.

All 5 companion bundles regenerated by build:plugins.

Docs / comments / memory

• kimi-code v0.6.0 → kimi-code 0.19.1 in docs/provider-paths.md + docs/polycli-v1-public-surface.md; dropped the re-drifting v0.6.0 pin from behavioural code comments (kimi.js, review.mjs, prompt-runtime.mjs).
• provider-paths.md snapshot → 2026-06-26; replaced the stale v0.6.21 clause in the roadmap.md Current-state section with the re-verification note.
• (Out-of-repo) project memory reference_cli_provider_versions.md rewritten to the 11-provider reality: pi @mariozechner→@earendil-works; kimi spawns kimi-code not the shadowed PyPI kimi-cli; minimax=mmx-cli not mini-agent.

Deferred / FLAGGED (not changed)

Per minimum-diff + the AGENTS.md "flag pre-existing dead code, don't delete" rule:

• pi.js dead agent_end.result.text / resultEvent.error branches (live agent_end carries only messages[]/willRetry, verified vs pi-agent-core .d.ts; harmless).
• opencode.js billed run "ping" auth probe could use non-billing opencode auth list, not done because auth-list proves CONFIGURED-not-WORKING and folding it in would weaken status honesty / risk the four-state.
• JSON/stream-json event schema unverified for ~7 providers (read-only/cost constraint — needs an execution-allowed run or fixture recapture; gemini/grok fixture meta versions also lag, already tracked by check:fixture-freshness).

Validation

• npm test 559/559
• npm run release:check exit 0

Respects the Path B boundary: no shared runtime base, no parser promoted into polycli-utils, timing four-state untouched, cold/retry still unimplemented.