diff --git a/features/steps/tui_persona_state_coverage_steps.py b/features/steps/tui_persona_state_coverage_steps.py
index c9153f84a..a82c95d4e 100644
--- a/features/steps/tui_persona_state_coverage_steps.py
+++ b/features/steps/tui_persona_state_coverage_steps.py
@@ -236,7 +236,7 @@ def step_verify_session_active_persona(context, session_id, expected):
     assert context.state.active_by_session[session_id] == expected
 
 
-@then('the registry last persona should be set to "{expected}"')
+@then('the mock registry last persona should be set to "{expected}"')
 def step_verify_last_persona_set(context, expected):
     context.mock_registry.set_last_persona.assert_called_with(expected)
 
diff --git a/features/tui_persona_state_coverage.feature b/features/tui_persona_state_coverage.feature
index 5141c737b..cf1d4c6f9 100644
--- a/features/tui_persona_state_coverage.feature
+++ b/features/tui_persona_state_coverage.feature
@@ -33,7 +33,7 @@ Feature: TUI Persona State Coverage
     When I set persona "coder" for session "sess-6"
     Then the returned persona name should be "coder"
     And session "sess-6" should have active persona "coder"
-    And the registry last persona should be set to "coder"
+    And the mock registry last persona should be set to "coder"
 
   Scenario: set_active_persona skips preset init when session already has one
     Given the preset for session "sess-6b" is already set to "turbo"