Archived
Federico Jaramillo Martinez
36d67262ec
The Pi extension provider baseline section stated that every later provider registration is a no-op, naming session_start as an example. That is now the exact case that is allowed, so the shipped configuration reference contradicted the behavior. docs/config.md is in the package files allowlist, so this text reaches users. Describe what stays frozen, the two conditions under which a known provider's model list refresh is applied, and why function-valued fields are always rejected. Record the accepted trade-offs: catalogs are shared daemon-wide state with last-registration-wins, and a model entry's own baseUrl/headers take precedence over the provider-level values. Split the log behavior out and note that ignored mutations are de-duplicated per provider while applied refreshes are always logged. Also correct the reload-behavior bullet: a restart is needed to add or remove a provider or change its connection settings, but not for a known provider refreshing only its model list.