+ Wja0t$Rt^RIHt^RIt^RIHt^RIHtH t H t H t ^RI H t^RI Ht^RIHt^RIHt/tR ]R &/tR ]R &R RltRRltRRR/RRllltR#)uThe effective USER config: config.yaml + managed overlay + ``${VAR}`` expansion, no defaults. ``load_config()`` merges ``DEFAULT_CONFIG`` first, which is wrong for readers that treat a missing key as "unset" (the gateway's presence-sensitive env bridge, ``cfg == {}`` sentinels, cron model pinning) — so nine surfaces used to hand-roll raw-read → overlay → expand in differing orders and none of them replayed the model-key canonicalization or the last-known-good recovery ``load_config()`` gained. This module is that one primitive. Order matches ``_load_config_impl``: the user layer is expanded BEFORE the managed overlay so a managed ``${VAR}`` resolves against the process environment only (``apply_managed_overlay`` expands it) and can never be re-resolved through a profile's secret scope (docs/design/managed-scope.md §4.1). ``read_user_config_raw`` stays the write-back primitive. ) annotationsN)Path)AnyDictOptionalTuple)config) managed_scope)_warn_config_parse_failure)fast_safe_loadzdict[str, dict[str, Any]]_LAST_GOOD_USER_RAWzdict[str, tuple[Any, ...]]_EFFECTIVE_CACHEc V^8dQhRRRR/#)rawdict[str, Any]return)formats"OC:\Users\johnn\AppData\Local\hermes\hermes-agent\hermes_cli\config_effective.py __annotate__r!sZZNZ~Zc\P!V4p\P!\ V\ 4'dTM/4p\P !\ V\ 4'dV4#/4#N)_config_expand_env_varsr apply_managed_overlay isinstancedict_normalize_root_model_keys)rexpandedmergeds& r _effectiver"!sX'',H  0 0ZRV=W=W]_ `F  - - 648P8Pf YYVX YYrc(V^8dQhRRRRRRRR/#) r config_pathrpath_keystrexc Exceptionrrr)rs"rrr's( 9 94 93 9Y 9> 9rc\PV4pRpVf^RIHpV!V4pRp\ YVeTMRR7Ve\ P !V4#/#)zLast-known-good raw user mapping after a parse failure: this process's last good parse, else the newest ``good`` copy in backups/config/, else ``{}`` (warned as defaults).zlast-known-good)load_newest_good_backupzlast-known-good-backupdefaults)fallback)r gethermes_cli.config_backupsr*r copydeepcopy)r$r%r'rr,r*s&&& r_recover_user_rawr1'sY  ! !( +C H {E%k2+{co([ef!$4== 8b8r fail_closedFc$V^8dQhRRRRRR/#)rr$zOptional[Path]r2boolrrr)rs"rrr4s(@@N@SW@dr@rc ^RIHpV!4pVe \V4#Vf\P!4p\ V4p\P ;_uu_4\P!V4wrV\PV4pVeVeVR,V8Xd\;QJd1RV^ ,P44F 'dK RM& RM"!RV^ ,P444'd(\P!V^,4uuRRR4#/pRp \PPV4p Ve[V eWV R,V8XdI\P!V ^,4p\P!V\P!V44MVe\#VRR 7;_uu_4p \%V 4p RRR4\'X \(4'dT M/p.VO\P!V4N5\PV&\P!V4\V&V\P!48Xd^R IHp V !VR 4\P2!V4p\4P6!4pV'd\P2!VV4\V4pVe.V 'g&.VO\P!V4NVN5\V&M\P9VR4VuuRRR4# +'giELE;i \.d!pT'dh\1YT4RrRp?LRp?ii;i +'giR#;i) u2User ``config.yaml`` → ``${VAR}`` expansion → managed overlay → model-key canonicalization. NO ``DEFAULT_CONFIG`` merge: a key absent from the file (and from the managed layer) is absent here, so ``{}`` sentinels and presence-sensitive bridges keep working. An absent file is an empty user layer (the managed layer still applies). Returns a fresh deepcopy. Broken YAML: ``fail_closed=True`` raises the parse error (for callers that keep their own last-good state); otherwise the last successfully parsed user file — in-process first, then the newest ``backups/config/*.good.*`` copy — is served through the same pipeline, so a mid-edit torn write never silently drops user overrides (same contract as ``load_config``). Cached on the user + managed file signatures and the values of every referenced env var.)worker_config_snapshotN:NNc3X"TF wr\P!V4V8HxK" R#5ir)r_env_ref_lookup).0kvs& r -load_user_config_effective..Ms$Q?Ptq7**1-2?Ps(*FT:NNz utf-8-sig)encoding) backup_configgood)agent.safe_worker_policyr6r"rget_config_pathr& _CONFIG_LOCK_load_config_cache_sigr r-allitemsr/r0_RAW_CONFIG_CACHEr setdefaultopenr rrr.rAr(r1_env_ref_snapshotr load_managed_configpop)r$r2r6snapshotr%user_sig cache_sigcachedr recoveredraw_hitfloadedrAr' env_snapshotmanaged effectives&$ rload_user_config_effectiverZ4s@&'H(##--/ ;H    %<<[I!%%h/  )"7F2J)M -M rdsb # --($D 24.3/1,1Z 9@Z_@@r