+ WjRt^RIHt^RIt^RIHt^RIHtRt!RR] 4t RRR llt RR R llt R R lt RRltRRltRRltR#)uYThe enabled-features file: the exact extras the install carries. The bundle is built with `uv sync --all-extras` minus the declared opt-in extras (`opt_in_extras`), but WHICH extras actually resolve differs per platform (markers gate some off). The shipped default is the EXACT list that installed — written at bundle time beside the payload, read at sync time: - lazy installs OFF (security.allow_lazy_installs: false): the feature list is FROZEN to this file; pm sync never deviates from it and never installs a plugin dep. - lazy installs ON: the file is the baseline; extras union on top. ) annotationsN)Path)Optionalzenabled-features.jsonc]tRt^tRtRtR#)FeatureProbeErrorz9A failed inventory must not become an empty feature list.N)__name__ __module__ __qualname____firstlineno____doc____static_attributes__r?C:\Users\johnn\AppData\Local\hermes\hermes-agent\pm\features.pyrrsCrrc V^8dQhRRRR/#)base_dirOptional[Path]returnrr)formats"r __annotate__rs 3 3N 3d 3rchVeV\, #^RIHpV!4P\, #)uuWhere the enabled-features file lives. In a bundle, the payload root (beside manifest.json — bundle-written, sealed-shipped). At runtime, the runtime dir (beside the byte store — per-install, writable on every install kind). Same relative location on both: a sealed install's store_root() is /tools, and the file sits at the payload root = store_root().parent.) store_root)FEATURES_FILENAMEpm.pathsrparent)rrs& r features_pathrs-+++# <  !2 22rc$V^8dQhRRRRRR/#)rextras list[str]rrrrr)rs"rrr*s!9$rc \V4pVPPRRR7VP\P !R^R\ \V44/^R7R,RR7V#) z?JTQ KrcV^8dQhRR/#)rrzOptional[list[str]]r)rs"rrr5s , ,* ,rc4\P!\4PRR74pTP R4p\T\4'gR#\TUu0uFp\T4kK up4# \\ 3dR#i;iuupi)uThe frozen/baseline feature list; None when no file exists (source installs without a bundle — the baseline is the recorded venv state).z utf-8-sigr'Nr) r+loadsr read_textOSError ValueErrorget isinstancelistr-str)datares r read_featuresr=5szz-/33[3IJXXh F fd # # 6*6a3q66* ++ Z  +s.A="B=BBc V^8dQhRRRR/#rrepo_dirrrrr)rs"rrrCsLLdLyLrc^RIpVR, PR4;_uu_4pVPV4pRRR4\XP R/4P R/44# +'giL;;i)z*Every extra the repo's pyproject declares.Npyproject.tomlrbprojectoptional-dependencies)tomllibopenloadr-r7)r@rFfr;s& rdeclared_extrasrJCs] % % + +D 1 1Q||A 2 $((9b)--.ErJ KK 2 1s A** A: c V^8dQhRRRR/#r?r)rs"rrrLsDYrc^RIpVR, PR4;_uu_4pVPV4pRRR4XPR/4PR/4PR.4p\ VPR/4PR/44p\ \ V4V, 4pV'd\ R V 24h\ \ V44# +'giL;i) aMExtras that only an explicit selection installs, never an all-extras build. ``[tool.hermes] opt-in-extras`` in the repo's pyproject. They stay installable through ``sync_venv([extra])``; bundles and other ``--all-extras`` builds leave them out, so their closures are absent from shipped payloads and from the recorded feature list. NrBrCtoolhermesz opt-in-extrasrDrEz5[tool.hermes] opt-in-extras names undeclared extras: )rFrGrHr7r.r-r6)r@rFrIr;namesdeclaredunknowns& r opt_in_extrasrRLs % % + +D 1 1Q||A 2 HHVR $ $Xr 2 6 6 KE488Ir*../FKLHSZ(*+GPQXPYZ[[ #e*  2 1s C!! C1 c(V^8dQhRRRRRRRR/#)rr@rvenv_dir python_exerrr)rs"rrr`s./k/kt/kt/kD/kY/krc &a^RIp^RIHp\V4Uu/uF qUV!V4bK pp\ VP 4UUu0uF qwFqkK K upp4p Rp VP \V4RRRRV \VP44\P!V 4.VRRR R ^#installed_extras..sJ8Iu4;d*8Is Fz4feature inventory returned incomplete anchor resultsc3<"TFKwr\;QJdV3RlV4F 'dK RM RM!V3RlV44'gKGVxKM R#5i)c36<"TFpSV,xK R#5irar)rdanchorresolveds& rrf-installed_extras...sCichY_HVDTDTchsFTN)all)rdextragrouprks& rrfrgs6j,zl"VH UV\__` T IJPSSTs=F F !AF7 G4G1,AG,,G14 H? H  Hra)r __future__rr+pathlibrtypingrr RuntimeErrorrrr0r=rJrRrrrrrsL # +D D 3 ,L(/kr