Teams chat link queries return messages from wrong threads

Problem

When providing a specific Teams chat link to \sk_work_iq\ (e.g., \https://teams.microsoft.com/l/chat/19:xxx@thread.v2/conversations?context=...\), the tool returns messages from other chat threads rather than the one specified in the link.

Evidence

The citation URLs in the response contained different thread IDs (e.g., \19:3746a407-136f-4152-bed7-842b6cf1fbcc_..., \19:db0566a4...) than the thread ID provided in the query (\19:224760b7...). The tool appeared to search broadly across the user's chats rather than scoping to the specific linked conversation.

Impact

This caused us to act on completely wrong information: we interpreted another conversation's requests as the task at hand, made incorrect changes to a documentation repository, and had to revert and redo the work. The tool's output was confidently presented with citations, making it non-obvious that the results were from the wrong thread.

Expected behavior

When a specific Teams chat link is provided, \sk_work_iq\ should scope its response to messages from that specific conversation thread, or clearly indicate if it cannot resolve the link to a specific thread.

Reproduction

1. Call \sk_work_iq\ with a question referencing a specific Teams chat link
2. Observe that the returned messages and citation URLs reference different thread IDs than the one in the provided link

The issue names no source files or tests. Start by reproducing the request with the provided Teams chat-link format and compare the input thread ID with the citation URLs; done means results are limited to that thread or the tool clearly reports that it cannot resolve the link.