From 530aa7b10f89baa3a63bf139df199c5a2a3fe79d Mon Sep 17 00:00:00 2001
From: Teknium <127238744+teknium1@users.noreply.github.com>
Date: Tue, 1 Sep 2026 01:51:04 -0700
Subject: [PATCH] test(cache): fix stale Studio construction-order paragraph in
 the bridge witness docstring

The module intro still described the pre-b449d7c1 order (row first, agent
second); _reply_scope and numbered item 2 already state the correct one.
---
 tests/agent/test_studio_bridge_affinity.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/tests/agent/test_studio_bridge_affinity.py b/tests/agent/test_studio_bridge_affinity.py
index 72917d2a05..e7141855d1 100644
--- a/tests/agent/test_studio_bridge_affinity.py
+++ b/tests/agent/test_studio_bridge_affinity.py
@@ -2,8 +2,8 @@
 
 Studio's group chat is the reproduction reported on #96811, and it reaches
 Hermes as a LIBRARY rather than through the gateway: its Python bridge
-pre-creates the session row and then constructs ``AIAgent(...)`` directly with
-a fresh physical ``session_id`` for every reply.
+constructs ``AIAgent(...)`` directly with a fresh physical ``session_id`` for
+every reply, and only then persists the session row.
 
 ``tests/agent/test_declared_conversation_scope.py`` pins the declaration
 contract on synthetic agent doubles, and