Motivation

PR #694 disables image generation when provider is Ollama (`lifecycle-service.ts` skips creating ImageGeneration; `main.ts` gates the command palette entry). The skip is purely defensive — Ollama itself does support some image-generation backends (e.g. via certain multimodal models, or via Ollama's planned support).

Two paths:

1. Add Ollama image-gen support when an installed model exposes image output. Probably small scope until Ollama formalizes the API.
2. Formally lock image-gen as Gemini-only and remove the runtime gating gymnastics — the always-register/runtime-gate command pattern in `8cf7cea` exists specifically to handle this case.

Recommendation

Wait until Ollama's image API stabilizes (still moving target as of Apr 2026), then revisit. In the meantime, capability matrix from #703 makes the gating cleaner without committing to either direction.

Code refs

• `src/services/lifecycle-service.ts` (image-gen service nulling on provider switch)
• `src/main.ts` (`gemini-scribe-generate-image` command always registered, runtime-gated)

Catalyst: PR #694 review discussion.