feat: reload narrow runtime settings overlay at future calls #179
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/runtime-config-overlay-request"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Small runtime-overlay slice using the existing writable
settings.local.yamlabove read-onlyharness.yaml. Adds live dispatcher rules and reasoning-effort-none model opt-ins with complete validation and last-valid fallback at future worker/prompt boundaries. Does not rewrite inflight requests or explicit conversation selections. Unknown overlay keys are strict at startup too; legacy environment opt-ins remain additive. Provider opt-in is not an endpoint-support claim.Installing this new host version requires the normal rollout/restart; subsequent supported overlay edits need no restart. No activation or live-agent access is claimed.
Evidence: 41 focused tests and typecheck passed (existing recorded runs); independent exact-tree review found no P0/P1. Normal owner ReviewService passed with no findings; staged and committed fingerprint and local/commit/push/publish gates verified. Seven files only; no new implementation during delivery. No merge, manual CI/build, configuration or deployment changes. PRs #177 and #178 are separate and untouched.