+ jHj"a0t$Rt^RIHt^RIt^RIt^RIt^RIHt^RI H t H t ^RI H t HtHt]P !]4tRtRt]P*!4t/tR]R &R R ltR R ltRRltRRltRRltRRltRRRllt.ROt R#)a9Profile-level session-storage health: one process-wide latch per state.db path. A structurally corrupt state.db used to show up as an empty or partial Desktop sidebar, green readiness and a 500 from ``/api/sessions``: every surface guessed on its own and none said "the store is damaged" (#72046). This module is the single place that fact is recorded. Writers (``SessionDB._halt_db_corrupt``), readers (``SessionDB`` read helpers) and the readiness probe publish into it; ``gateway.readiness`` (``state_db`` / ``session_store`` checks, hence ``/api/status`` ``components.storage``) and the session list endpoints read from it, so Desktop and readiness cannot disagree. Only structural corruption latches: bare ``SQLITE_CORRUPT`` / ``SQLITE_NOTADB`` with no FTS provenance. FTS-scoped damage has its own fail-open path with canonical rows intact, and a malformed-schema row is healed by the web open path, so neither is reported here. The latch never clears on its own. A corrupt image does not heal, and a store that flickers between "ok" and "corrupt" is the silent failure this replaces. It resets when the process restarts, which is the recovery boundary ``StateDbCorruptError`` already documents (stop Hermes, recover or restore, start again). No marker is written to disk: the file it would describe is the one that is damaged. ) annotationsN)Path)DictOptional)classify_persistence_erroris_fts_scoped_corruption_erroris_malformed_schema_errorokcorruptzdict[str, str]_corruptcV^8dQhRR/#returnstr)formats"8/home/ubuntu/.hermes/hermes-agent/hermes_state_health.py __annotate__r-sAASAcf\\V4P4PRR74#)F)strict)rr expanduserresolvedb_paths&r_keyr-s( tG}'')111? @@rc V^8dQhRRRR/#rexc BaseExceptionrboolr)rs"rrr1s $rc\V\P4;'d?\V4'*;'d'\ V4'*;'d\ V4R8H#)zCanonical B-tree/schema/freelist damage: a corrupt/NOTADB error SQLite does not scope to the FTS index, and not the malformed-schema case the web open path repairs.r ) isinstancesqlite3 DatabaseErrorrrr)rs&ris_structural_corruption_errorr&1s\ 3--. 9 9.s3 3 9 9)#. . 9 9 's +y 8 rc V^8dQhRRRR/#)rreasonobjectrNoner)rs"rrr<s  & T rc\V4p\;_uu_4V\9d RRR4R#\V4\V&RRR4\P RWV4R# +'giL);i)zELatch *db_path* as corrupt for the life of this process (idempotent).Nzstate.db at %s is structurally corrupt (%s); session storage is reported as corrupt until Hermes restarts on a recovered or restored file. Stop Hermes, then run `hermes sessions recover --source %s --inspect-only` or restore a snapshot.)r_lockr rloggererror)rr(keys&& rmark_storage_corruptr0<sX w-C  (?  F    LL V   s A$A$$ A4 c V^8dQhRRRR/#rr)rs"rrrKs]trcB\V4'gR#\W4R#)zFLatch *db_path* when *exc* is structural corruption; True when it was.FT)r&r0)rrs&&rnote_storage_errorr3Ks )# . .& rcV^8dQhRR/#r r)rs"rrrSsLLcLrc\;_uu_4\V4\9d\M\uuRRR4# +'giR#;i)z[``"corrupt"`` once this process has seen structural corruption on *db_path*, else ``"ok"``.N)r,rr STORAGE_CORRUPT STORAGE_OKrs&r storage_stater8Ss# "&w-8"; s : A cV^8dQhRR/#)rrz Optional[str]r)rs"rrrYs++}+rc\;_uu_4\P\V44uuRRR4# +'giR#;i)zLThe first error text latched for *db_path* (logs/diagnostics only), or None.N)r,r getrrs&rstorage_corrupt_reasonr<Ys# ||DM* s 8 A cV^8dQhRR/#)rrr*r)rs"rrr_s...rc\;_uu_4Vf\P4M\P\ V4R4RRR4R# +'giR#;i)zForget the latch for *db_path* (all paths when None). For tests and a verified in-process recovery; nothing in the runtime clears it on its own.N)r,r clearpoprrs&rreset_storage_staterA_s6  ? NN  LLg - s 9A A# )N)r6r7r&r0r3rAr<r8)!__conditional_annotations____doc__ __future__rloggingr$ threadingpathlibrtypingrrhermes_state_errorsrrr getLogger__name__r-r7r6Lockr,r __annotations__rr&r0r3r8r<rA__all__)rBs@rrOs*#!   8 $  .A L + . r