@deepseek-ai/dsh-llm-pi-ai

Change configuration at runtime

Profiles are re-read once per operation through the optional settings seam: the base and the user's llm-pi-ai: settings section merge per provider, so a user can add a route, override one field of a composition route, or point a route at another proxy, all effective on the next request with no restart. A section the adapter could not serve is refused where it is written — settings.mutate answers settings-rejected — and a stored section that later fails keeps the namespace's last good value. When the route set or a route's retry policy changes, the plugin re-registers atomically: a conflicting route leaves the previous routes serving.