provider-mistral

# Provider: Mistral Vibe CLI Process guidance for keeping the gateway's Mistral (`vibe`) integration aligned with the upstream CLI. This skill does **not** define argv/env behaviour; the single mechanical source of truth is `UPSTREAM_CLI_CONTRACTS.mistral` in `src/upstream-contracts.ts`, enforced by `validateUpstreamCliArgs` / `validateUpstreamCliEnv`. Never re-encode flags, agent modes, output formats, the env-model rule, or resume rules here or in TOML. ## Identity | Field | Value | | ---------------- | ------------------------------------------------------------------------ | | CliType | `mistral` | | Executable | `vibe` | | Package | `mistral-vibe` (pypi; also uv / brew) | | Repo | https://github.com/mistralai/mistral-vibe | | Release API | https://api.github.com/repos/mistralai/mistral-vibe/releases/latest | | Watch categories | `flags`, `agent-modes`, `session-logging`, `output-formats`, `env-model` | These values mirror `UPSTREAM_CLI_CONTRACTS.mistral.upstreamMetadata` and `docs/upstream/provider-sources.dag.toml` (`[providers.mistral]`). The TypeScript metadata is authoritative; the TOML is scanner input only. ## When to use - A Mistral Vibe release...