The container runtime policies kind was restart-required because the pool
captured image, pull policy, network, max uptime and max concurrency at
construction and the dispatcher fixed its slot count at the start of a drain
pass. Both consumers now re-read the published config:
- the pool's settings come from a live source read per acquire, with the
boot-resolved registry credential and Docker construction values preserved;
a live default-image change is pulled rather than assumed present;
- the daemon owns one long-lived dispatcher that accepts a new limit: running
tasks keep their slots, a raise admits queued work immediately, and a lower
limit is applied as tasks finish;
- the control-plane descriptor is live, the kind joins runtimeResourceKinds,
and the apply/reload paths resize the dispatcher after publishing. The
ContainerConfig fields whose consumers now re-read are added to the reload
allowlist; registry_auth stays restart-required.
Regenerate the docs artifacts. contracts.json also carries the voice
media-type description a prior commit left stale.