refactor: remove channelTypeKnown workaround (now dead code)

dave · claude · dave · commit 02de7789bcfb · 2026-03-31T13:41:28.000+11:00
The early-exit guard for kind === "unknown" in handlePost (from the
unknown-chat-type PR) means we never reach the threading logic with an
unresolved channel type. The channelTypeKnown conditional was the old
workaround for this exact scenario and is now unreachable.

Co-Authored-By: Claude Sonnet 4.6 &lt;noreply@anthropic.com&gt;
diff --git a/extensions/mattermost/src/mattermost/monitor.ts b/extensions/mattermost/src/mattermost/monitor.ts
@@ -1220,11 +1220,7 @@ export async function monitorMattermostProvider(opts: MonitorMattermostOpts = {}
     });
 
     const baseSessionKey = route.sessionKey;
-    // Don't thread if channel lookup failed and the websocket event didn't include
-    // channel_type — we might be in a DM masquerading as "channel" via the
-    // mapMattermostChannelTypeToChatType fallback.
-    const channelTypeKnown = channelInfo != null || payload.data?.channel_type != null;
-    const threadRootId = channelTypeKnown ? (post.root_id?.trim() || undefined) : undefined;
+    const threadRootId = post.root_id?.trim() || undefined;
     const replyToMode = resolveMattermostReplyToMode(account, kind);
     const threadContext = resolveMattermostThreadSessionContext({
       baseSessionKey,
