Zellij fit assessment for Hermes Navigator

Zellij is a good optional backend for Hermes Navigator scenes, not a replacement for Hermes Navigator itself. Official Zellij docs validate four capabilities that matter for Navigator: KDL layouts for reusable workspace profiles, CLI/JSON control for machine-driven automation, background/headless sessions for SSH hosts, and session resurrection for local runtime continuity.

The key boundary is persistence. Hermes Navigator should keep its SQLite SceneStore / NamedSession as the authoritative source for issue_ref, project identity, and context snapshots, while Zellij manages host-local terminal layout/runtime state.

Recommendation: conditionally adopt Zellij for hnavig scene activate/resume as an optional terminal backend, with one Zellij session per host (gaia, as, eury). Do not treat a single Zellij session as cross-host shared state, and do not scope this first wave as a full replacement for the broader tmux substrate.