[Bug] Write: Chat sidebar inherits stale context

[felipevaz]

Summary / 问题概述

The chat sidebar is often unaware of the text currently being worked on, and it just inherits previous context — often mentioning files that aren't there anymore.

Steps to reproduce / 复现步骤

Open a file in Write and have a conversation about it in the chat sidebar.
Close that file and open a different file.
Ask a question about the new file in the chat sidebar.
Observe that the assistant references the previous file or context instead of the current file.

Expected behavior / 期望行为

The chat sidebar should be aware of which file is currently open and base its context on the current text.

Actual behavior / 实际行为

The sidebar inherits stale context from previous conversations and mentions files that are no longer relevant and that were eventually deleted, as somehow the chat is continuing from a previous context.

Kun version / Kun 版本

0.2.25

Operating system / 操作系统

Mac OS 14.8.3

Logs / 日志

Checklist / 检查清单

• I searched existing issues before opening this report. / 我已经搜索过现有 issue。
• I removed sensitive information from logs and screenshots. / 我已经从日志和截图中移除敏感信息。

[luoye520ww]

Thanks for the detailed reproduction. I opened #848 to fix the stale context at the conversation registry level.

Write conversations are now scoped to both the workspace and the active file, so switching files no longer reuses another document's model history. Returning to a file restores its own conversation, while an unmapped file starts clean. Rename and delete operations also migrate or remove file mappings, so old context is not resurrected for a path that was removed and later recreated.

[felipevaz]

Thanks for addressing this!