+ lHj) JRt^RIt^RIHtR RRlltR RRlltRRltR#) uzCheckpoint-enablement resolution for TUI-created agents (issue #79625). Desktop sessions (``hermes serve`` → TUI gateway) never set ``HERMES_TUI_CHECKPOINTS`` (that env var is only set by the ``hermes --tui --checkpoints`` CLI path), so agent creation previously gated filesystem checkpointing on the env var alone and silently ignored ``checkpoints.enabled`` in config.yaml. These helpers resolve enablement the way the messaging gateway does (``gateway/run.py`` ``_checkpoint_agent_kwargs``): the env var (explicit CLI opt-in) wins when set, otherwise the ``checkpoints`` config section applies with ``DEFAULT_CONFIG`` defaults. N)is_truthy_valuec>V^8dQhR\R,R\/#cfgNreturndictbool)formats"V^8dQhR\R,R\/#rr)r s"r r r s * *TD[ *D *rct\PPR4pVe \V4#\ V4#)uPResolve checkpoint enablement with the env-var override first. ``HERMES_TUI_CHECKPOINTS`` (set by ``hermes --tui --checkpoints``) is the explicit opt-in and wins when present; otherwise fall back to the ``checkpoints`` config section (issue #79625 — the desktop backend never sets the env var, so config was being silently ignored). HERMES_TUI_CHECKPOINTS)osenvironrrr)renv_vals& r resolve_checkpoints_enabledr s3jjnn56Gw'' $S ))rc<V^8dQhR\R\R\/#)rcwdrefr)str)r s"r r r .s& N Ns N N NrcVPV4p\V4^, p^Tu;8:d\T48dMMY4,P RT4#\R\T4 R24h \dTu#i;i)uS``/rollback N`` style number → the checkpoint's hash; a real hash passes through.hashz!Invalid checkpoint number. Use 1-.)list_checkpointsint ValueErrorlenr)mgrr r!ridxs&&& r _resolve_checkpoint_hashr,.s**3/ #hl C"#k""##FC00 8[9I8J!L MM  s#A00 B?B)N)__doc__rutilsrrrr,rr r0s#  ! Q * Nr