+
    ƒWÝj•  ã                  óN   € R t ^ RIHt ^ RIt^ RIHtHtHt ^ RIH	t	 RR R llt
R# )a�  Profile-scoped reads of the ``HERMES_*`` tuning settings cron honours from ``.env``.

A standalone ``hermes -p X gateway run`` loads X's ``.env`` into ``os.environ``, so a bare
``os.getenv("HERMES_CRON_TIMEOUT")`` is X's value. Under ``gateway.multiplex_profiles`` the same
tick runs inside the default profile's process, where ``os.environ`` holds the DEFAULT profile's
``.env``. With a secret scope installed (job run + delivery) the scope is authoritative; the tick
loop itself (due-job scan, pool sizing) runs under the profile's home override only, so the
setting is read from that home's ``.env``. Outside multiplex the read is the plain environ.
)ÚannotationsN)Úcurrent_secret_scopeÚis_multiplex_activeÚload_env_file)Úget_hermes_homec               ó$   € V ^8„  d   QhRRRRRR/# )é   ÚnameÚstrÚdefaultÚreturn© )Úformats   "ÚEC:\Users\johnn\AppData\Local\hermes\hermes-agent\cron\env_settings.pyÚ__annotate__r      s!   € ÷ 4ñ 4˜3ð 4¨ð 4°cñ 4ó    c                óö   € \        4       '       g!   \        P                  ! V 4      ;'       g    T# \        4       pVf   \	        \        4       R,          4      pVP                  V 4      pVf   V# \        V4      # )Nz.env)r   ÚosÚgetenvr   r   r   Úgetr
   )r	   r   ÚscopeÚvalues   &&  r   Úcron_env_settingr      s`   € Ü× Ò Ü�yŠy˜‹×)Ð) 'Ð)Ü Ó"€EØ‚}ÜœoÓ/°&Õ8Ó9ˆØ�I‰I�d‹O€EØ’mˆ7Ð3¬¨U«Ð3r   )Ú )Ú__doc__Ú
__future__r   r   Úagent.secret_scoper   r   r   Úhermes_constantsr   r   r   r   r   Ú<module>r      s%   ðñõ #ã 	ç WÑ WÝ ,÷4ñ 4r   