+ WjjRt^RIHt^RIHt^RIHt^RIHt^RI H t ^RI H t RRR R /R R llt R #)zIPinned tool acquisition for PM's private Python engine; never worker API.) annotations)Path)native) InstallError) get_package)current_targetrealizeTexplicitFc$V^8dQhRRRRRR/#)rboolr returnztuple[Path, Path] | None)formats":C:\Users\johnn\AppData\Local\hermes\hermes-agent\pm\_uv.py __annotate__r s'&J&J4&J$&JC[&Jc^RIHpHpHpHp^RIHpV'd V!RVR7V!4p\4p/p RFp \V 4p V!WV4p V fV'gR#\V RR4hV R8Xd7VPR 4'd V!4'dV!WVR R 7p V fR#V wrV PVPV PV 4R ,4V4pVeVP4'gV'gR#\V R R4hWV &K \\!V R,44\\!V R,443#)aResolve uv and Python without host discovery or recursive worker dispatch. A read-only probe never installs. A sealed Windows payload builds on a verified writable copy of its Python: uv starts a venv's ``Scripts\python.exe`` to query it, and that redirector runs outside the package, so its target must too. A redirector naming the packaged interpreter dies with exit 101 (#135236). Hermes itself still enters those venvs on the packaged interpreter (``pm.environments.venv_command``). )_installed_location _lockfileensuresealed) writable_copyuv)r pythonNzpinned tool is unavailablezrun `hermes pm install`win32z0a writable Python is required for bundled builds)rr whyentryzinstalled binary is missing)rr) pm.installrrrrpm.user_facingrrrr startswithbinaryrgetis_filerr)rr rrrrrlockfiletargetbinariesnamepackagelocationfactsstorer!s$$ r _toolchainr, s+JI,th'{H  FH d#&w&A  t%AC\] ] 8  1 1' : :vxx$TX)[]H  EIIdOG,D EvN >!1!1t%BD]^ ^%!( x~& 'fXh5G.H)I IIrN)__doc__ __future__rpathlibr pm.filesystemr pm.packager pm.registryrpm.storerr,rrrr4s6O" ###&J$&J&J&Jr