Expand description
Hot reload of the v2 configuration (RFC 0030 §6, RFC 0017 semantics):
SIGHUP or lifecycle.watch_config re-merges the files and re-validates; the
restart-only paths must be unchanged (else restart_required, the running
configuration stays); the reloadable partition applies at the loop’s
quiesce boundary — the flat tree makes most of it trivial: every turn worker
is spawned fresh from the live settings, so a new intelligence endpoint,
model, instruction, budget, tool override or workflow definition takes
effect for the next unit of work. Live runs keep the definition they
started with (pinned by hash).