+ jHjyxRt^RIHt^RIt^RIt^RIt^RIt^RIHt^RI H t RRlt RRlt R R lt R R /R RlltRt^tRRltRRltRR/R R!lltR"R#ltR$R%lt]!R&R'04tR(R)ltR*R+lt R,R-lt!R.R/lt"R0R1lt#R2R3lt$R4R/R5R6llt%R7R8lt&R ! ! # + +A ..r c V^8dQhRRRR/#)r project_rootrrboolr)r s"r r r sTdr c"VR, P4'dR#^RIHp^RIHpV!V4pV!V4pV'gR#VP R4\ 9d0\RVP RRP\ 4 R 24hR #) uA sealed tree ships its interpreter; only checkouts own a venv. The stamp file is the authority (shared with hermes_cli.steward). A tree with BOTH a stamp and .git is a dev tree — treat as checkout. A stamp without a valid ``updateMechanism`` is a build-lane bug and must not be silently read as "not sealed" (that is exactly the misclassification that made sealed trees look updatable) — same guard as hermes_cli.version_info._stamp_version_info. .gitFread_install_stamp)install_stamp_pathupdateMechanismzinstall-stamp.json at z. is missing a valid 'updateMechanism' (one of z, zg). The build lane that wrote this stamp must pass --update-mechanism to scripts/write_install_stamp.py.T) existshermes_cli.stewardrpm.pathsrgetr RuntimeErrorparentjoin)rrr stamp_pathdatas& r _is_sealedr%s v%%''5+#L1J l +D  xx!"*;;$Z%6%6$78))-3D)E(FG. .  r c V^8dQhRRRR/#)rrrr str | Noner)r s"r r r 3sGGGGr cF^RIp^RIHpHp\ V4R, P 4'dV!V4P R4R8wdR#VP4pV'gR#V!\ V44pV'dRV R2MRpR R PV4 R V 2#) zCOne passive startup verdict; callers only choose stderr or logging.N)rsealed_stewardrrselfzthis z1-managed install must rebuild the artifact to fixzrun `hermes pm install`zinstall out of sync (; u) — ) pmrrr)rrractivater")rr,rr)problemsstewardremedys& r check_runtimer13s E \V#++--2D\2R2V2VWh2ims2s{{}H T,/0GgYOP7 "499X#6"7vfX FFr createTc$V^8dQhRRRRRR/#)rrrr2rrNoner)r s"r r r Ds&XXDXTXTXr c^RIp^RIHpHpHpHp^RIHp\V4pVP\4p \V4'dV PRV4R#V!V4PR4R8XdV PRV4R#V!V4f#V PRWR , R , 4R#V!WR , R , 4p \V 4\V48wd^R IHp V !R R R4hV!WR7p V R,'g3^RIpVP\4PRV R,4R#R#)zHRefresh durable commands; bootstrap repairs only existing PATH exposure.N) ENTRY_POINTSensure_install_launchers expose_cliresolve_store_pythonrz*launchers: sealed tree at %s keeps its ownrexternalz/launchers: external runtime at %s keeps its ownz C@ JJL''E <%dV2dV3DUGL''*e+MO  !   s G  GGzsource_completion.pyzupdate_completion.pyc$V^8dQhRRRRRR/#)rrIrargv0rfrrr)r s"r r r *s&[[$[s[t[r c\V4pVP\9;'d%VP4PVR, 8H#)zPExact own-script identity; argv is not inherited by the processes a tail spawns. hermes_cli)rr _TAIL_SCRIPTSrr!)rIrscripts&& r _is_tail_scriptr*s9 %[F ;;- ' Z ZFNN,<,C,CtlGZ,ZZr cV^8dQhRR/#)rrrr)r s"r r r 0s  4 r cj\;QJdRR4F 'gK R# R#!RR44#)u4A launcher-marked child: booted by a manager, not a user's shell. Launcher markers only — not INVOCATION_ID, which systemd exports to every descendant: an ordinary hermes command inside a CI runner still owes its repair. Parsed as a truthy flag, so an explicit ``0``/``false`` does not suppress the tail. c3"TFDp\PPVR4P4P 4R9xKF R#5i)N)1trueyeson)renvironrrlower).0rs& r $_supervised_child..7s>MD tR &&(..04NNMsA ATF)HERMES_SUPERVISED_CHILDHERMES_S6_SUPERVISED_CHILD)anyrr r _supervised_childr0s? 3M3333M r c V^8dQhRRRR/#)rrIrrrr)r s"r r r =s4444r c^RIHp^RIHpV!V4pVP R4p\ V\ 4'd%V'dRV9gVP R4RJdR#\V4pVP4'dAVP4PVR, P4P8dR#V!VRR 7pVPV8H;'dVP'*#) aTrue when the checkout is the exact clean tree the last install/update completed. Every finished tail records its tree in install-stamp.json (write_source_stamp); when that commit is a clean HEAD, the products in the tree were built for it, so a stale venv only needs re-provisioning and a marker armed BEFORE that stamp is a leftover from a previous home/install, never a rebuild of the same SHA (fresh Windows installs and pristine HERMES_HOMEs hit exactly this: #123314). A marker armed after the stamp is newer debt (a same-commit ``hermes update`` that failed or was killed) and is still owed. Boot-time adoption also stamps HEAD but builds nothing, so its stamp (``adoptedAt``) is not evidence; neither is a dirty tree. r)_git_version_infocommit adoptedAtdirtyFzinstall-stamp.jsonT)include_untracked) rrhermes_cli.version_inforr isinstancerfrr`rrrr)rIrrstamprrrEs& r _tree_matches_completed_stampr=s69 t $E YYx F fc " "&K54HEIIV]L^fkLk%d+GW\\^44@T9T8Z8Z8\8e8ee TT :D ;;& 3 3^3r c$V^8dQhRRRRRR/#)rrrargvrxrrPr)r s"r r r Ws&tttYt;tr c^RIp^RIp\V4P4p\ WCP ^,4'dR#^RIHp^RIH pV!V4pVR,R.8Xg\\V4,'g{\V4'gjVPPRR4P4R9g;VR, P!4'dVR , P#4'gR#V!V4pV'g^R IHp V !V4V!V4pVPR 4R 8wdR#^RIp ^R IHp ^RIHp Hp V P5VR7p^RIHpV!V4pVe\;VVVR7#\=V4pT;'d#VP#4;'d \?4p\AV4wpppV'g*V\B8d\ERV R2VPFRR7EMV'gMV'gV'dVP#4'dV !VRR7pVPI4'g \KR4hVPL'gXV !VR7eMV'dVPO4R#\QVRR7V P5VR7'g \KR4hM/VPSV4'g \KR4h\UWNVR7VPO4V !V4pVf \KR4hVPVPYVPVP[V44VPVPYVPVP[VP\448HpV'd V'g\_V4V#V'd\ERVPFRR7R# TPO4i;i) aFinish a self-managed source update before importing app dependencies. PM's successful input stamp signals a finished dependency sync; the ``source-completion-pending`` marker signals the tail still owed after it, so a tail that failed is retried on the next launch WITHOUT rebuilding dependencies that are already current. Old updaters need not write a marker (and cannot accidentally clear this obligation). A supervised child leaves that tail to ``hermes update`` when its dependencies are current: its manager restarts it on every start, so a sticky marker would re-run the tail (and its environment builds) on each boot until the disk fills. Return the store interpreter when this process must restart cleanly. N) command_argvr:NrNr,HERMES_DISABLE_LAZY_INSTALLSrrrV)step_adopt_blessed_checkoutrr*r9) UpdateLockread_live_updaterY)owning_home_root)rZz=hermes: a source update could not be finished automatically (z9 attempts); run `hermes update` from a shell to finish itTfileflushF install_rootcheckout_firstEan update is still running; wait for it to exit, then relaunch Hermes)rarm-dependency sync left this install out of date)rZr->tEB||~~fg g ===%54%H%T LLN*$E:))t)<<&'VWW=,,T22&'noo%dWM LLN !$ 'F ~YZZ 77  BGGOOF3 48H8HY\YgYgIh8i iD $$  d::T + % LLNsO'O AOOOc(V^8dQhRRRRRRRR/#)rrIrrrZrrrPr)r s"r r r s( 7 74 7 7$ 7; 7r c^RIp^RIp^RIp^RIHp^RIHpV'gnV!VRR7pVP4'g \R4h\VRVR7VP4VPVR7'g \R 4hV!V4p V f \R 4hVPPVPPV 44VPPVPPVP448Hp V'd V 'gV #R# TP4i;i) aLaunch a checkout that another data root owns (#123238). Dependency state is per data root, so a borrowing root -- a test's temporary ``HERMES_HOME``, a per-task home -- still gets an environment of its own, synced exactly as a process spawned under a live update syncs. The rest is the checkout's, and so the owner's: launchers, product builds, post-update maintenance, the install stamp and the owner's own update markers. None of it is armed, run or published from here, so a borrowing launch cannot rebind the shared launchers, rebuild products another root is serving, or race the owner's tail under a lock that lives in a different home. Nr)rFrr)r borrowed_fromrYrr)rrr,rBr9r rr r rrrarrrr) rIrrZrrr,r9rrrrs &&$ r r r s :1 tEB||~~fg g  %dU K LLN!!t!44NO O !$ 'F ~YZZ 77  BGGOOF3 48H8HY\YgYgIh8i iD 66$6 LLNs D,,D>c(V^8dQhRRRRRRRR/#)rrIrrZrrrr4r)r s"r r r s(>>>$>>$>r c a ^RIp^RIHo ^RIHpV'gVR, VR, 3p\ ;QJdV 3RlV4F 'gK RM RM!V 3RlV44'd \ R 4h\R VPRR 7\V4p\W'*R 7V'd\V4R#M6\V4'd\V4R#\R VPRR 7VR, pVR, P4;'g"\ VR, PR44p^RIHp Hp T !VP"RRR\%VR, 4R\%V4R.V'dRMRORW!V4VP&R7P(p V ^8wd\-VRR7\ R4h\V4R# T d2p \RT P* 2TPRR 7^p Rp ? L_Rp ? ii;i)zOSync dependencies when they are stale, then run the tail the marker still owes.N)_marker_owner_is_live)activation_environment.update-incomplete.lazy-refresh-incompletec34<"TF pS!V4xK R#5iNr)rmarkerr#s& r r(_finish_source_update..sJ>$V,,>sTFrz0hermes: completing source-update dependencies...rrz1hermes: finishing an interrupted source update...z apps/desktopzdist/index.htmlr*)CustodyRefusedrun-Iz-Bz-uzhermes_cli/source_completion.pyz--sourcez--finish-update) inherit_lockcwdenvstdoutzhermes: )rWzAsource update completion failed; run `hermes update` to finish it)z --desktopr)rhermes_cli._early_recoveryr#rqr$rr r r rrrr`rhermes_cli.update_custodyr,r-rrf __stderr__ returncodereasonr)rIrZrrr$legacy_markers completed desktop_appdesktopr,r-codergr#s&$$ @r rrs@6 !55t>X7XY 3J>J333J>J J Jfg g @szzY]^1$7  "$M:  T "   't , ,  A Z^_'K//88:;;{Y.44S9: >  ^^T4 99 : T$5 3")~b 34-CD-IRUR`R`  *  qy"45 O  T   %CJJdCs AGH 'HH r c(V^8dQhRRRRRRRR/#) rrIrrrr rPrr4r)r s"r r r 2s)#.#.D#.$#.{#.^b#.r c^RIp^RIp^RIHp^RIHp^RIHpVe\RV R2VPRR7M V'g\R VPRR7\V4V'd \V4V!V4P4'g V!V4MRpV!4VPVRVRR 7\V4VeR#R Fp W , PRR 7K R#) zCommit the tree's dependency generation; *arm* also owes the tail afterwards. *borrowed_from* names the data root that owns the checkout when this one only borrows it: the sync is this root's own, but the checkout's update markers stay the owner's. N)ensure_tools_for_sync)runtime_facts_path)legacy_selectionzThermes: preparing dependencies for this data root (the checkout's updates belong to z)...Trz1hermes: preparing dependencies for this update...r[r)r%r&)rr, pm.clientr?rqr@ pm.extrasrAr r rbrr`rcrdr) rIrr rr,r?r@rAextrasrs &$$ r rr2s  /2*  dt%+.::T C  A Z^_d#  t,>d+C+K+K+M+M d #SWFLL$TVZL["4( C -Cr c 0V^8dQhRRRRRRRRRRR R/#) rrrrIrrxoriginalmoduler'rr)r s"r r r Xs<>> >>$->9B>LV>>r cR.p^pV\V48dW6,pVR9gVPR4'gMWVPV4V^, pVR9gKZV\V48gKlVPW6,4V^, pKR\V4: RV: R2pV^,R8XdRW6^,,: R2p MEV'dVR8wd R V: R 2p M.R \\ V^,4P 44: R 2p \V4.VOR NRNW,N#)zRe-enter the same script/module/launcher with the managed interpreter. An old venv may use a different Python ABI. Do not add the new generation to that interpreter, and do not depend on its obsolete editable finder. -c-z&import sys, runpy; sys.path.insert(0, z); sys.argv = r+zexec()__main__zrunpy.run_module(z&, run_name='__main__', alter_sys=True)zrunpy.run_path(z, run_name='__main__')r.)rIz-mz--rJ)z-Wz-X)rG startswithrrfrabsolute) rrIrrFrGoptionsindexoptionprefixbodys &&&&& r relaunch_commandrTXsG E #h-  , ,F4E4Ec4J4J v   \ !ec(m&; NN8? + QJE5c$i].QUPXXZ [F Aw$x *-Q/ Fj("6*,RS!T$q']%;%;%=!> AAWX K =' =4 = =v} ==r c V^8dQhRRRR/#)rrz list | Nonerrr)r s"r r r xs$${$c$r cF\P!RR7pVPRRR7VPRRRR7VPR RR 7VPV4p\ VP 'd\ VP 4MRVPR 7pVP'd!\\P!V44M=VPR 4'dR VR , R2MRp\RVR, V 24VR,'d^#^#)zhermes_cli.venv_sync)progz--project-rootN)defaultz--check store_truezreport; change nothing)actionhelpz--json)rZ)rNrXz (rKrz venv sync: rTr?) argparseArgumentParser add_argument parse_argsrhrrrNjsonr dumpsr)rparserargsrLrXs& r mainrdxs  $ $*@ AF ($7 ,-E 6   T "D #'#4#4#4T  $djjF yyy djj !-3ZZ-A-A2fX&'q)r F7O,VH56t 1#!#r rLr(>-V-h--help --versioni)*__doc__ __future__rr\r`r subprocesspathlibrrrrr%r1rMrhrd frozensetrr|rrrrrrrrrrbrrrrrr rrrTrdrD SystemExitrr r ros # 0/:G"XDXDDEDD8e4?@0 I%&!#* !Y ,HdHD< D13IJK [ 44tn 7F>B#.UY#.L>@$* z TV r