OrcaRouter provider support for PagibleAI CMS

PagibleAI CMS delivers on its README promise of "simple as WordPress, the power of Contentful": an API-first Laravel CMS where content generation and refinement, translation, image inpainting/repainting and audio transcription are native, and where 30+ MCP tools let an LLM drive content management directly. That mix of editorial ease and machine-readable structure is what makes it useful for Laravel teams shipping anything from a blog to a multi-tenant, multi-domain site.

What stands out from the docs is how provider-neutral the AI layer is: every capability in `config/cms/ai.php` (`CMS_AI_WRITE`, `CMS_AI_IMAGINE`, `CMS_AI_TRANSCRIBE`, ...) selects its own provider, model and API key, and an optional `url` key already accepts an OpenAI-compatible endpoint. Because of that design, offering OrcaRouter as another selectable provider would give site operators a single key that serves multiple model families with routing and failover, without touching their existing Gemini, OpenAI or DeepL setup.

I'd like to propose adding **OrcaRouter as an optional AI provider** for PagibleAI CMS. It would sit alongside the existing providers and would not replace or change any of them.

OrcaRouter exposes an OpenAI-compatible API and uses standard API-key authentication, giving access to multiple chat, reasoning, image and video models through one endpoint. For Pagible's users, three capabilities seem most relevant:

- **Multiple model families behind one endpoint and one key** - features like `write`/`refine` (text) and `imagine`/`inpaint`/`repaint` (image) could route to suitable models without per-vendor setup.
- **Automatic model routing with provider failover** - an editorial task is less likely to fail because one model provider is down or rate-limited.
- **Usage tracking and budgets** - useful for multi-tenant or agency deployments where AI spend needs to stay attributable and predictable.

The natural integration point is the existing provider abstraction: Prism/Prisma PHP already supports configurable providers, and Pagible's per-feature entries plus the optional `url` override for OpenAI-compatible endpoints would let OrcaRouter be selected like any other provider. This is a proposal only - no code exists or has been tested in this repository.

OrcaRouter is already in use across the open-source ecosystem, including RAGFlow, Dify, promptfoo and goose, so supporting it here would follow an established pattern rather than introduce a new one.

For full transparency: OrcaRouter runs an optional open-source partner program in which approved OSS projects can receive a 5% revenue share from OrcaRouter usage attributed to their integration. Participation is not a prerequisite for an integration, and I'm happy to follow Pagible's own disclosure and governance expectations.

I'm an engineer on the OrcaRouter team. If adding OrcaRouter as an optional provider sounds useful for PagibleAI CMS, I'd welcome your thoughts - and, with your go-ahead, I'd be glad to prepare an implementation PR. A few existing integrations are listed at https://www.orcarouter.ai/built-with.

Start with config/cms/ai.php and the existing provider abstraction in Prism/Prisma PHP. Trace how each feature selects its provider, model, API key, and optional url, then clarify which OrcaRouter capabilities and failover behavior are required. Done means an optional provider can be selected without changing existing Gemini, OpenAI, or DeepL configuration.

Rédigé par le modèle d'indexation à partir du texte de l'issue.