+ jHjRt^RIHt^RIt^RIt^RIt^RIHt]P!] 4t RRlt RRlt RR lt R#) aCron: import path of the restart-safe external worker. The worker is spawned as ``sys.executable -m cron.scheduler``. Its entry module is ``cron.scheduler``, not ``hermes_cli.main``, so nothing bootstraps the gateway's checkout onto its ``sys.path``; historically it imported ``cron`` only through the implicit ``-m`` cwd entry. That entry is gone under ``PYTHONSAFEPATH`` and useless when the venv's editable install maps a moved/deleted checkout -- the worker then dies with "No module named 'cron'" before its ownership ack (#112729, hypothesised cause). The shared subprocess sanitizer strips Hermes-owned PYTHONPATH entries because user children must not see our tree. This child IS Hermes, so the pin is applied *after* the env is built, on the sanitized env. On a self-managed (shell-installer / PM) install the sanitizer's drop of the runtime site-packages cannot stand this time: the worker inherits this process's interpreter, which is PM's store Python and owns no third-party dependencies, so the committed generation's site-packages is restored here too or the child dies at its first dependency import (``No module named 'ruamel'``, #122222) before it can publish its ownership acknowledgement. ) annotationsN)PathcV^8dQhRR/#)return Path | None)formats">/home/ubuntu/.hermes/hermes-agent/cron/scheduler_worker_env.py __annotate__r sKc\\P!4R,4P4# \\ 3dR#i;i)purelibN)r sysconfig get_pathsresolveKeyErrorOSErrorrr r _installed_purelibrs@I''))45==?? g s25A  A c V^8dQhRRRR/#)r project_rootrrrr)r s"r r r %s33d3{3r c^RIHpHpV!V4pTfR#T!T4pTP 4'dT#R# \d"p\P RT4Rp?R#Rp?ii;i)a The dependency ``site-packages`` PM committed for this install, or ``None``. Asked of PM's own committed selection -- the record ``activate_dependencies`` resolves at process boot -- rather than re-derived from this process's ``sys.path``: the record belongs to this install (``install_state_dir``, shared by every profile it serves). A runner that owns its dependencies (wheel / pipx / developer venv / Nix: no committed generation) has nothing to restore, so ``None`` means "pin the tree only" and nothing is invented. )committed_venv site_packageszDcron worker: could not read the committed dependency environment: %sN)pm.environmentsrr Exceptionloggerwarningis_dir)rrr environmentexcselecteds& r #_committed_dependency_site_packagesr"%sk A$\2 [)H((82d2   RTW  s: A&A!!A&c$V^8dQhRRRRRR/#)r worker_envdict repo_rootrrr)r s"r r r @s!dtr c\V4p\4\V4P48XdV#VP RR4P \ P4Uu.uFq3'gK VNK pp\\V44pV.Ve \V4.M.Op\ PP\P.VOVO44VR&V#uupi)aPrepend ``repo_root`` -- and, when this runner has one, the committed dependency generation's ``site-packages`` -- to the worker env's own PYTHONPATH (never ``os.environ``'s). Skipped when ``repo_root`` is the interpreter's ``purelib``: under a wheel / pipx / uv-tool install ``cron/`` lives in site-packages itself, which is already importable, and pinning it would move site-packages ahead of the stdlib on ``sys.path``. Order (checkout, generation, sanitizer-kept) mirrors ``activate_dependencies``' own ``sys.path``. For the cron worker, its boot (``cron/worker_bootstrap.py``) then re-selects and leases the committed generation before any third-party import, and exits the worker if it cannot. PYTHONPATH) strrrrgetsplitospathsepr"joinr%fromkeys)r$r&rooteexisting dependencypinneds&& r pin_hermes_tree_on_pythonpathr6@s y>DtDz1133%>>,;AA"**MSMaQRMHS4T$Z@J K:+As:'r KF!zzt}}=Qv=Q=Q/RSJ|  Ts % C3C)__doc__ __future__rloggingr-rpathlibr getLogger__name__rrr"r6rr r r=s:&#    8 $36r