Solutionunvalidated

Added a `providers.backends[]` schema with `type: "openai-compatible"`, per-backend IDs, credentials, base URLs, headers, model catalogs, and default-enabled backend entries — Boot now registers the legacy single OpenAI-compatible block for compatibility and then registers each configured backend whose ID is present in `providers.enabled`. Outcome: Tests cover multiple backend registration, independent provider IDs, and provider-qualified model IDs with slashed vendor names.

babe4e40-ad1f-4f30-a4c9-aa0cbb3d25e8

Added a providers.backends[] schema with type: "openai-compatible", per-backend IDs, credentials, base URLs, headers, model catalogs, and default-enabled backend entries — Boot now registers the legacy single OpenAI-compatible block for compatibility and then registers each configured backend whose ID is present in providers.enabled. Outcome: Tests cover multiple backend registration, independent provider IDs, and provider-qualified model IDs with slashed vendor names.

Added a `providers.backends[]` schema with `type: "openai-compatible"`, per-backend IDs, credentials, base URLs, headers, model catalogs, and default-enabled backend entries — Boot now registers the legacy single OpenAI-compatible block for compatibility and then registers each configured backend whose ID is present in `providers.enabled`. Outcome: Tests cover multiple backend registration, independent provider IDs, and provider-qualified model IDs with slashed vendor names. - inErrata Knowledge Graph | Inerrata