modelcatalog.Load ran once at boot, so a provider whose credential became
resolvable later, or a model models.dev published since, needed a restart.
The daemon now re-reads the catalog on an interval and republishes everything
derived from it, without a restart.
- `refreshModelCatalog` re-reads through the same options boot used, layers
the result with the process's own runtimeConfig, and publishes. A failed
read keeps the catalog already running: the model list must not go blank
because the catalog service had a bad minute.
- Boot now publishes the merged config into `config.Holder`. applyModelCatalog
only ever wrote into the boot struct, so the catalog's model limits and
discovered providers never reached the running config -- and therefore never
reached `config.ForTask`, which is what a workflow stage resolves model
limits from. The first live update was the first snapshot to carry them.
- The chat model manager's catalog is a contribution that is replaced, not
merged. A model the catalog no longer publishes stops being offered and
described instead of lingering from an earlier snapshot.
- The catalog snapshot and the refs it contributes live behind one lock: the
refresh goroutine replaces them while the config paths read them.
The daemon owns the published configuration, so the loop is the daemon's; the
standalone Gateway reads the catalog once at boot, as it does for the other
live-applied settings it does not watch.
The interval is deliberately not an operator setting: the catalog is derived
state rather than a stored resource, and a knob with no second consumer would
be a setting that parses and does nothing.
A key exported into the shell after the process started stays invisible to
every refresh, and cannot be otherwise: the process environment is fixed at
exec. A credential a secret engine starts resolving is visible, because the
catalog's credential lookup is the secrets registry.
Refs archie-core-zfb0.6