Interface captures: --ui

--ui photographs the app’s own interface — the browser, the settings menu, the corner name, the console, the now-playing banner and the diagnostics panel — without a window, a keyboard or a live track. Each state is built by the same functions the running app draws with, fed fixed data rather than the machine’s: a fixed browser roster with two marks and a truncated name, a fixed filter string, a fixed banner string and a fixed settings view. So two runs differ only where the code does.

# Every state, at the two sizes an aspect mistake shows up between (ADR-0037)
cargo run -p standalone --example shot -- --ui all --size 1920x1080 --out target/ui-audit/1080
cargo run -p standalone --example shot -- --ui all --size 1280x800 --out target/ui-audit/800

# One state, over a preset of your choosing
cargo run -p standalone --example shot -- --ui settings --preset "Whorl" --out target/ui-audit

state	what it shows
hud	the corner preset name carrying a favourite mark, and the rotation countdown under it
browse	the browser freshly opened, highlight on the playing preset, the preview pane’s placeholder
browse-filtered	the browser narrowed by a typed filter, the header naming it
browse-thumbs	the browser with a picture in the preview pane — the scene itself, shrunk to the thumbnail cache’s size
settings	the settings menu freshly opened
console	the operator console’s header, transport labels and staging line, scaled to the capture as a console window of that size scales them
banner	the now-playing banner at full opacity, under the corner name
diagnostics	the F3 panel and the audio line under it
help	the key help sheet ? opens on the show, drawn from the table the keys are dispatched from
all	every state above, in this order

The scene is Nebula unless --preset names another; a library without it falls back to its first preset and says so on stderr. --frames, --set, --size and --tier mean what they mean for a single shot.

A capture, never a golden. Text is shaped on the machine’s system sans-serif font, so the same command draws different glyphs on two machines. Compare captures taken on one machine. Two states are approximations of what the app shows. The console capture draws the scene full-frame behind the lines, where the real console window shows a letterboxed preview. The diagnostics panel’s frame times read zero, because a capture measures no frames.