+ WjRt^RIHt^RIt^RIt^RIHt]P!]4t Rt RRlt RRRR R R /R R llt RRlt RRltRRltRRltRRltRRltRRltR#)aThe terminal's PATH: the user's own tools first, Hermes's after them. Hermes's process puts its store's tool dirs first (``pm.install.activate``), so Hermes's own code resolves the pinned binaries. Terminal commands belong to the user and the agent, so they run the tools the user installed, and Hermes's tools are the fallback for a machine without them. Hermes's own operations must not depend on this PATH: they resolve pinned tools through PM (``pm.env_for``, ``pm.installed_package``). A sealed Windows payload's store sits under ``WindowsApps``. In the process tree that the app's execution alias starts, a program whose own executable is outside the package cannot start one inside it: cmd.exe running npm's ``npx.cmd`` gets "Access is denied" from the packaged ``node.exe``, and a venv's ``Scripts\python.exe`` redirector exits 101 when it starts the packaged Python. A copy of the same files outside the package starts without error, so there :func:`copies` swaps those dirs for PM's verified copies. ) annotationsN)PathcV^8dQhRR/#)returnbool)formats"BC:\Users\johnn\AppData\Local\hermes\hermes-agent\pm\user_facing.py __annotate__r s===cd^RIHp^RIHpV!4P R4;'dV!4#)zQTrue for a sealed payload on Windows, the only layout with the restriction above.)sealed)current_targetwin32) pm.installrpm.storer startswith)rrs r appliesrs&!'   & &w / < J s ' AA AAc V^8dQhRRRR/#)rrCr:rr)r s"r r r bs \ \ \y \r c4aa\4'g \V4#/o\FHp\V4pV'd \ V4M.oS'gK-SP V3RlV44KJ \\ PV3RlV444#)z*dirs* with each packaged npm, node and python dir swapped for its writable copy on a sealed Windows payload. A packaged dir stays when PM may not copy it (lazy installs off).c3f<"TF&p\PPV4S3xK( R#5iN)ospathnormcase).0rDr4s& r copies..ls%Fv!))!,f5vs.1c3<"TF=pSP\PPV4V.4Fq"xK K? R#5irY)r?rZr[r\)r]rDcswaps& r r^r_ms9ZAtxx@P@PQR@SVWUX7Y!a7YasAA)rlistCOPIEDrLrUupdatedictfromkeys)rCrrr4rbs& @@r copiesrhbsp 99Dz!#Dd#%+D! 6 KKFvF F   ZZZ [[r c V^8dQhRRRR/#)r directoryrrrr)r s"r r r ps    r c\V4PRRUu.uF"p\PP V4NK$ ppV\PP R4\PP R4.8wdR#\ \V4P R44'*#uupi \dR#i;i)aTrue for the Windows app-alias dir when its ``python.exe`` is only the Store stub. The stub opens the Microsoft Store instead of running Python. A real Store Python puts its aliases in the same dir, and it also ships a ``python3.N.exe``, which the stub does not. N Microsoft WindowsAppsFz python3.*.exeT)rpartsrZr[r\anyglobrQ)rjpartros& r _python_stub_dirrsps 15Y0E0Ebc0J K0JRWW  d #0JE K !!+.0@0@0OPPtI++O<=== L s(B3 'B88 CCcV^8dQhRR/#)rrr:r)r s"r r r shhihr c^RIHpV!RRR/R7PRR4P\P 4Uu.uFq'gK VNK up#uupi)rH)r>pythonr=)base_env)rr>r?splitrZpathsep)r>rDs r _python_dirsr{sN"x62,?CCFBOUUVXV`V`a ga!efAAa gg gs  AAc V^8dQhRRRR/#)rr[rrr)r s"r r r sUU3U3Ur c^RIHpV!4pV'gV#\V4p.VOVOUu0uF"p\PP V4kK$ ppVP \P4Uu.uF4qf'gK \PP V4V9gK2VNK6 pp\\44Uu0uF"p\PP V4kK$ pp\R\V44\V44p VUu.uF+p\PP V4V9gK)VNK- p pVUu.uF+p\PP V4V9gK)VNK- p p\PP\P.VRV OV OWyROV O44#uupiuupiuupiuupiuupi)z*path* with Hermes's store tool dirs (their writable copies, see :func:`copies`) moved behind the user's own entries. Hermes's Python stops just before the app-alias dir that holds the Store stub, so a machine without Python still runs a real one. )_store_path_dirsc3P"TFwr\V4'gKVxK R#5irY)rs)r]ips& r r^#user_facing_path..sEoda1A!1Dos& &N)rr~rhrZr[r\ryrzr{next enumeratelenjoinrfrg) r[r~rBoursrDkeysrkeptrvcutearlylates & r user_facing_pathrsu,  E  %=D)854 9ABGG  Q D 9zz"**- W-!Arww7G7G7JRV7VAA-D W+1,.+A B+Aabggq!+AF B EioEs4y QC >1 0 0 3v =QQE > At!rww//2&@AAtD A ::??4==)R4:)R)RT )RT)RS TT : W B > As5(G6 G!G*G(G &GG&G<G)npmnoderv)__doc__ __future__rloggingrZpathlibr getLogger__name__rRrdrr7rErLrUrhrsr{rrr r rsy#  ! #= " "u "E "FQX B \ h Ur