PmjdZddlmZddlZddlZddlZddlZddlmZddl m Z ej e Z eejdz ZdZdd ZeZddZdddZdS)u Resolve where the Photon sidecar runs from and where its Node deps live. The sidecar source ships inside the installed plugin tree (``plugins/platforms/photon/sidecar/``). On dev/source installs that tree is writable and everything — ``npm ci``, the spectrum patch, the sidecar itself — happens in place. Hosted/managed images instead keep the whole install tree under an immutable ``/opt/hermes`` (read-only for the hermes user), which broke every install/self-heal path with EROFS (NS-606). Resolution order (mirrors ``resolve_whatsapp_bridge_dir`` for the Baileys bridge, which hit the same wall): 1. ``PHOTON_SIDECAR_DIR`` env override — operator escape hatch, used as-is. 2. Source dir writable → run in place (dev installs, unchanged behavior). 3. Source dir read-only but ``node_modules`` is baked and current → run in place. This is the managed-image happy path: the Dockerfile bakes the sidecar deps with ``npm ci`` at build time (deterministic installs, NS-559), so no runtime install is ever needed. 4. Source dir read-only and deps missing or stale → mirror the sidecar source files to ``$HERMES_HOME/photon/sidecar`` (the durable data volume, e.g. ``/opt/data`` on hosted) and return that. The caller's normal install/self-heal machinery then works there because it is writable. The mirror is refreshed on every resolve: when an image update changes a sidecar source file, the changed file is re-copied (content compare, not mtime) while ``node_modules`` is left in place — the adapter's existing lockfile-vs-install-marker staleness check then triggers the ``npm ci`` self-heal inside the mirror. This module is import-light on purpose: both ``adapter.py`` (gateway) and ``cli.py`` (``hermes photon ...``) use it. ) annotationsN)Path)Optionalsidecar)z index.mjsz package.jsonpackage-lock.jsonz$patch-spectrum-mixed-attachments.mjspathrreturnboolc|dz } ||dS#t$rYdSwxYw)zTrue when we can create files in ``path`` (probe-based, not stat). A stat-mode check lies on containers (root-squash, read-only bind mounts), so probe with a real create+unlink like the WhatsApp bridge resolver does. z.hermes-write-probeTF)touchunlinkOSError)rprobes L/home/thesage/.hermes/hermes-agent/plugins/platforms/photon/sidecar_paths.py dir_writabler;sU ( (E  t uus (1 ?? sidecar_dirc|dz }|dz dz } |j|jkS#t$rYdSwxYw)u@True when the committed lockfile postdates npm's install marker. Same signal as ``adapter._sidecar_deps_stale`` — duplicated here (three lines) rather than imported so this module stays import-light for the CLI. Returns False on any stat failure so an odd filesystem never forces the mirror path. r node_modulesz.package-lock.jsonF)statst_mtimer)rlockfilemarkers r_lock_newer_than_installrOsg00H > ),@ @F}}'&++--*@@@ uus3A AA source_dirOptional[Path]c|t|nt}tjd}|rt|St |r|S|dz rt |s|Sddlm}|dz dz } | dd tD]}||z }|s||z }|r1tj t|t|d s/tjt|t||S#t $r(}t"d |||cYd}~Sd}~wwxYw) zReturn the directory the sidecar should run from (see module doc). ``source_dir`` defaults to the installed plugin tree; tests and callers that monkeypatch the adapter's ``_SIDECAR_DIR`` pass it through so the override keeps working. NPHOTON_SIDECAR_DIRrr)get_hermes_homephotonrT)parentsexist_okF)shallowu[photon] install tree is read-only and mirroring the sidecar to %s failed (%s) — falling back to the read-only source dir; dependency installs will not be possible)rSOURCE_SIDECAR_DIRosgetenv _dir_writableexistsrhermes_constantsrmkdir _MIRROR_FILESfilecmpcmpstrshutilcopy2rloggerwarning) rsourceoverridermirrornamesrcdstexcs rresolve_sidecar_dirr9_s",!7T*   =OFy-..HH~~V ''))2J62R2R 100000 _   )I 5F TD 111! 1 1D4-C::<< 4-C::<< 1w{3s88SXXu'U'U'U 1 SXXs3xx000  7       sB5E E6E1+E61E6)rrr r )rrr r )N)rrr r)__doc__ __future__rr+loggingr$r.pathlibrtypingr getLogger__name__r0__file__parentr#r*rr&rr9rrEs  D#"""""   8 $ $T(^^*Y6      "      .......rD