+ „WÝjƒãó6€Rt^RIHt^RIHt!RR4tR#)a¶The ``api_content`` sidecar backfill writers for SessionDB (#124102 FILE_LINES split). Split out of :mod:`hermes_state_messages`: the two row-addressed sidecar UPDATEs the turn prologue uses when the current turn's user row was materialized before the sidecar could be composed. Bound into ``SessionDB`` via this mixin, so every existing ``session_db.set_message_api_content(...)`` call site and test patch seam keeps working unchanged. )Ú annotations)ÚAnycó2€]tRt^tRtRRltRRltRtR#)ÚSessionApiContentMixinz;``SessionDB`` mixin: the ``api_content`` sidecar backfills.có(€V^8„dQhRRRRRRRR/#)éÚ session_idÚstrÚcontentrÚ api_contentÚreturnÚint©)Úformats"ÚLC:\Users\johnn\AppData\Local\hermes\hermes-agent\hermes_state_api_content.pyÚ __annotate__Ú#SessionApiContentMixin.__annotate__s0€÷YñY°cðYÀCðYÐVYðYÐ^añYóc ó`€^RIHpVPRV!V4WPV434#)uòBackfill the ``api_content`` sidecar onto the newest ACTIVE user row (0/1 rows). Preflight compaction inserts that row BEFORE the sidecar exists and the later persist identity-skips compacted dicts; without this a reload reopens the prompt-cache divergence. ``content`` match guards a racing rewrite. POSITIONAL, and only safe when the caller already knows the newest active user row IS the message it stamped. The content match is NOT sufficient on its own: repeated identical user turns ("ok", "y", "continue") make an OLDER row compare equal, so calling this before the current turn's row exists overwrites the previous turn's sidecar with this turn's bytes — durable wrong-bytes replay, a worse cache break than the missing sidecar. When the caller holds the durable row id (``_row_id``, synced onto the live dict by ``sync_flushed_message_markers`` and stamped by :meth:`_insert_message_rows`), use :meth:`set_message_api_content` instead — it addresses the exact row and cannot land on a neighbour. ©Ú_scrub_surrogatesz¨UPDATE messages SET api_content = ? WHERE id = (SELECT id FROM messages WHERE session_id = ? AND role = 'user' AND active = 1 ORDER BY id DESC LIMIT 1) AND content IS ?)Úhermes_state_messagesrÚ_write_rowcountÚ_encode_content)Úselfrr r rs&&&& rÚset_latest_user_api_contentÚ2SessionApiContentMixin.set_latest_user_api_contents;€õ" <Ø×#Ñ#ð !ñ˜{Ó +¨Z×9MÑ9MÈgÓ9VÐ Wó Yð Yrc ó,€V^8„dQhRRRRRRRRRR/#) rrr Úrow_idr r rr r r)rs"rrr)s;€÷añaØðaØ'*ðaØ58ðaØGJðaà ñarc  óÜ€^RIHpV'd4\V\4'g\V\4'dV^8:d^#VP RV!V4W!VP V434#)aýBackfill the ``api_content`` sidecar onto ONE known durable row. Row-addressed counterpart to :meth:`set_latest_user_api_content`: the caller passes the ``_row_id`` the write path stamped on the live message dict, so the update cannot drift onto a neighbouring row that merely carries the same text. Used by the turn prologue whenever the current turn's user row was already materialized before the sidecar could be composed (in-place preflight compaction, a close/early flush that raced the prologue). The crash persist then marker-skips that message, so this is the only way the stamped bytes reach the store. ``active = 1`` and the ``content`` match stay as defensive guards: a row the compaction archived, or one a racing rewrite changed, is left untouched. rzuUPDATE messages SET api_content = ? WHERE id = ? AND session_id = ? AND role = 'user' AND active = 1 AND content IS ?)rrÚ isinstanceÚboolr rr)rrrr r rs&&&&& rÚset_message_api_contentÚ.SessionApiContentMixin.set_message_api_content)se€õ( <ßœZ¨´×5Ò5¼ZÈÔPS×=TÒ=TÐX^ÐbcÔXcÙØ×#Ñ#ð @á ˜{Ó +¨VÀ×AUÑAUÐV]ÓA^Ð _óað arrN)Ú__name__Ú __module__Ú __qualname__Ú__firstlineno__Ú__doc__rr"Ú__static_attributes__rrrrrs†ÙEõY÷0añarrN)r(Ú __future__rÚtypingrrrrrÚr,sðñõ#å÷5aó5ar