+ Wj3 Rt^RIHt^RIt^RIHtRRltRRltRR ltR R lt R R lt RRlt RRlt RRlt RRltR#)z9Where the store, lockfile, and installed-state file live.) annotationsN)PathcV^8dQhRR/#returnr)formats" ! ! # * * 1 11r cV^8dQhRR/#rr)r s"r r r s--d-r cz\PPR4pV'd \V4#\ 4#)zThe tree this process runs from. ``HERMES_INSTALL_ROOT`` when a steward wrapper sets it (Nix points it at the sealed tree whose install stamp lives outside the package dir), else the executing checkout.HERMES_INSTALL_ROOT)osenvirongetrr)envs r install_rootr s* **... /C49,,r c V^8dQhRRRR/#)r project_rootrrr)r s"r r r s ' 'T 'd 'r cx\V4pVP4\48Xd \4pVR, #)uTHE stamp location for ``project_root``, shared by every stamp reader. Beside the code in checkouts, Docker and desktop payloads. A Nix package bakes the stamp outside the store's package dir and its wrapper carries ``HERMES_INSTALL_ROOT`` for the executing tree only — so the executing tree resolves through install_root, any other tree is taken literally. PM reads it in sealed stages (the Docker runtime base) before hermes_cli ships, so it lives here rather than beside the stewards. zinstall-stamp.json)rrrr)rroots& r install_stamp_pathrs1  D ||~$~ & &&r cV^8dQhRR/#rr)r s"r r r %s99t9r c^\\4P4PR, #)z lock.jsonrrr r lockfile_pathr"%s > ! ! # * *[ 88r cV^8dQhRR/#rr)r s"r r r )s  D r c.^RIHpV!\44#) store_root)pm.environmentsr'rrs r r'r')s5 9; r cV^8dQhRR/#rr)r s"r r r /s < s''D'r c$\4R, #)z facts.jsonr&rr r facts_pathr4>s <, &&r cV^8dQhRR/#rr)r s"r r r Bs//T/r c\4PR, P4'g \4#^RIHpV!4R, #)z manifest.jsonr,tools)r'ris_filer0r-r,s r writable_store_rootr9Bs7 L  / 1 : : < <|8 " $w ..r cV^8dQhRR/#rr)r s"r r r Js  D r c.^RIHpV!\44#)r%)runtime_facts_path)r(r<rr)s r r<r<Js= 9; r )__doc__ __future__rrpathlibrrrrr"r'r1r4r9r<rr r r@s>?" 2- ' 9 <'/ r