From d9e64e916500fca93920b2fae31b362628f042e6 Mon Sep 17 00:00:00 2001
From: Teknium <127238744+teknium1@users.noreply.github.com>
Date: Wed, 9 Sep 2026 12:44:59 -0700
Subject: [PATCH] fix(state): record display_identity/display_order in the
 messages schema history

#106582 (1c6683e8e0b) added display_identity and display_order to the messages
table in SCHEMA_SQL without appending the matching events to
SCHEMA_HISTORY["messages"], so test_replayed_history_ends_at_current_schema
has been red on main since 17:06Z. Append the two '+' events; no runtime change.
---
 hermes_cli/session_schema_history.py | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/hermes_cli/session_schema_history.py b/hermes_cli/session_schema_history.py
index 477b645abf..a54c16e536 100644
--- a/hermes_cli/session_schema_history.py
+++ b/hermes_cli/session_schema_history.py
@@ -232,6 +232,10 @@ SCHEMA_HISTORY: dict[str, _TableHistory] = {
             ('+', 'display_metadata', 'display_kind'),
         )),
         ('14 2026-08-25T10:55Z 1104ffe0b9', (('+', '_compressed_summary', 'observed'),)),
+        ('15 2026-09-09T17:05Z 1c6683e8e0', (
+            ('+', 'display_identity', 'display_metadata'),
+            ('+', 'display_order', 'display_identity'),
+        )),
         ),
     ),
     "session_model_usage": _TableHistory(