From the last CI run

Screenshots

42 captures across 3 platforms, taken by the extension's own end-to-end run. Every one of them was produced by a script, on a clean runner, against the same.vsix the release publishes.

Download every capture as one zip, or read gallery.json for the list: each image with its platform, theme, caption, pixel size and SHA-256. Both keep these addresses from one run to the next, and both are attached to every tagged release. The manifest uses the schema a Day app's gallery publishes, so a reader of one reads the other.

How these are made

The e2e driver downloads a pinned VS Code, installs the packaged extension into it, scaffolds a Day project on the runner withday new app, then drives the UI: open the Day view, tick the host's own target, run it, wait for the app to launch, photograph each step. macOS buildsmacos-appkit, Windows builds windows-xaml, and Linux buildslinux-gtk under a virtual display that holds both the editor and the app it launched.

Each editor surface is photographed twice, once in each of VS Code's default themes, and the gallery shows whichever one matches the theme you are reading in.

Because the same script produces the pictures and the assertions, a screenshot that looks right is also a test that passed. Anything the extension stops doing shows up here as a missing image rather than as stale marketing.