From 4f8dce1f6215082781a79778657a09253329cfad Mon Sep 17 00:00:00 2001 From: Ouroboros <311266734+ouroboros-agent@users.noreply.github.com> Date: Sat, 26 Sep 2026 01:58:04 +0300 Subject: [PATCH] test: pin the owner-marking wrapper composition, not a renamed local test_live_task_message_marker_uses_my_human_wording looked for the literal `noted_owner_text(owner_ctx, entry, dmsg)`; ee5011158 renamed that local to `model_msg` in loop_round_limits.py while the wrapper stayed in place, so quick-test on ouroboros went red for a spelling. Pin the composition `_owner_marked_content(noted_owner_text(owner_ctx, entry, ...` instead. --- tests/test_identity_wording.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/test_identity_wording.py b/tests/test_identity_wording.py index f5517b892..0a652b8bc 100644 --- a/tests/test_identity_wording.py +++ b/tests/test_identity_wording.py @@ -31,7 +31,7 @@ def test_live_task_message_marker_uses_my_human_wording(): assert "[Message from my human]" in system # The drained mailbox text (plus its optional surface note) must still go # through the owner-marking wrapper before injection. - assert "_owner_marked_content(noted_owner_text(owner_ctx, entry, dmsg))" in loop + assert "_owner_marked_content(noted_owner_text(owner_ctx, entry, " in loop # Addressed task-tree messages are peer/ancestor/peer-root communication, # not owner dialogue, and must never borrow the owner's priority marker. # Ask the render ladder itself: every provenance it can frame — including