sjzdZddlmZddlZddlZddlmZmZmZej e Z dZ dZ dZddd ZdddZdS)uShared config→env bridge for media-delivery policy. ``validate_media_delivery_path`` (gateway/platforms/base.py) reads its policy from environment variables: - ``HERMES_MEDIA_DELIVERY_STRICT`` <- gateway.strict - ``HERMES_MEDIA_ALLOW_DIRS`` <- gateway.media_delivery_allow_dirs - ``HERMES_MEDIA_TRUST_RECENT_FILES`` <- gateway.trust_recent_files Historically the config.yaml -> env translation ran ONLY in gateway startup (gateway/run.py), so any process that delivers media without booting the gateway — a manual ``hermes cron run`` in the CLI, ``hermes send``, a standalone cron tick — filtered MEDIA paths under DIFFERENT policy than the gateway's scheduled deliveries. In strict/allowlisted enterprise deployments that divergence silently dropped attachments from manual cron runs while scheduled runs delivered them (text is unaffected — only media goes through path validation). ``apply_media_policy_env()`` is that same translation as a shared, idempotent helper. Gateway startup calls it, and every standalone delivery entrypoint calls it immediately before filtering media paths. Precedence: an explicitly-set environment variable WINS over config.yaml. This preserves both the operator contract (env overrides are how deployments pin behavior) and gateway/run.py's historical shape (it only wrote the env var when the config key was present; we additionally refuse to overwrite a pre-existing env value so a shell-exported override survives). ) annotationsN)AnyDictOptionalHERMES_MEDIA_DELIVERY_STRICTHERMES_MEDIA_ALLOW_DIRSHERMES_MEDIA_TRUST_RECENT_FILESconfigOptional[Dict[str, Any]]returnDict[str, Any]c|& ddlm}|pi}n#t$ricYSwxYw|di}t |t r|niS)Nr) load_configgateway)hermes_cli.configr Exceptionget isinstancedict)r r gateway_cfgs 8/home/agent/.hermes/hermes-agent/gateway/media_policy.py_load_gateway_cfgr+s ~  5 5 5 5 5 5 []](bFF   III **Y++K$[$77 ?;;R?s  &&Nonec> t|}|sdS|d}|tjts|rdndtjt<dSdSdS#t$r td d YdSwxYw) uBridge gateway media-policy settings from config.yaml into the env. Idempotent and env-wins: a variable already present in the environment is never overwritten, so gateway startup (which runs this same helper) and operator shell exports keep precedence. Never raises — a policy-bridge failure must not break delivery; the validator falls back to its defaults exactly as before. Nstrict10media_delivery_allow_dirsc38K|]}|t|VdSN)str).0ps r z)apply_media_policy_env..Ns-0Q0QAq0QQ0Q0Q0Q0Q0Q0Qtrust_recent_fileszapply_media_policy_env failedT)exc_info)rrosenviron _STRICT_ENV_ALLOW_DIRS_ENVrr!listtuplepathsepjoin_TRUST_RECENT_ENVrloggerdebug)r rr allow_dirsallow_dirs_str trust_recents rapply_media_policy_envr77sE'//   F**  bjnn[&A&A -3&r?s:#""""" &&&&&&&&&&  8 $ $, +5 @ @ @ @ @!E!E!E!E!E!E!Er%