test: stabilize channel mode and discussion coverage

test/multi-message-mode.test.ts

@@ -1,7 +1,7 @@
 import { describe, it, beforeEach, afterEach } from "node:test";
 import assert from "node:assert";
 import { enterMultiMessageMode, exitMultiMessageMode, isMultiMessageMode } from "../plugin/core/channel-modes.ts";
-import { initTurnOrder, checkTurn, onNewMessage, resetTurn } from "../plugin/turn-manager.ts";
+import { initTurnOrder, checkTurn, getTurnDebugInfo, onNewMessage, resetTurn } from "../plugin/turn-manager.ts";
 
 describe("Multi-Message Mode Tests", () => {
   const channelId = "test-channel";
@@ -70,8 +70,9 @@ describe("Multi-Message Mode Tests", () => {
       // Even with mention override conceptually, multi-message mode should take precedence
       // In real usage, mention overrides happen in message-received hook before multi-message mode logic
       const turnResult = checkTurn(channelId, "agent-a");
+      assert.ok(typeof turnResult === "object");
       // The actual behavior depends on the before-model-resolve hook which forces no-reply in multi-message mode
-      
+
       // Exit multi-message mode to resume normal operation
       exitMultiMessageMode(channelId);
       assert.strictEqual(isMultiMessageMode(channelId), false);