Set a tool's applied extension combos
Author all of a tool’s extension combos through the pipeline: persist, reload, and broadcast.
Owner resolution, the consolidation-conflict check, and the registry combo
validation all run BEFORE the pipeline (nothing persisted on a reject). The
mutator then upserts the providing config’s extensions entry, and
ConfigService validates the whole document, persists, reloads locally, and
broadcasts the reload so every worker rebinds; the per-origin fleet report rides
the response as its fanout summary. The persist + local reload have already
landed, so re-running the apply (or a reload_config) is the recovery for a
sibling that did not converge.
Authorizations
Path Parameters
Body
Set a tool's applied extension combos — the full list of combos, authored
losslessly. Each combo element is an extension name or a {"name", "config"}
mapping binding author config. An empty list clears them.
Response
Success.

