Frame 80 of 107 · windows-ui-state-lowlevel
Rich command results beside the compact aligned appearance editor with stable random-per-repository mode
1000 × 687 px · 77,615 bytes · batch windows-ui-state-lowlevel
呢一頁只講一張相：邊個 scene 出，邊個 batch 收，尺寸、指令、憑證全部照抄記錄，冇記錄就照直講冇。
What the sources record
- Asset file
- docs/assets/screenshots/material-command-palette-appearance.png
- Pixel dimensions
- 1,000 × 687 px, read from the PNG IHDR header
- File size
- 77,615 bytes on disk
- PNG encoding
- 8-bit truecolour (IHDR colour type 2)
- Gallery output id
- material-command-palette-appearance
- Scene
- command-palette-appearance
- Capture batch
- windows-ui-state-lowlevel
- Platform
- windows-headless
- Feature Gallery section
- Tab groups and command palette
- Guided workflow caption
- Rich command results beside the compact aligned appearance editor with stable random-per-repository mode
- Publication status
- Published target in the current Windows guided gallery
Alternative text
Full-app command palette showing matched commands with their live
settings controls beside the compact aligned row appearance
editor
The alternative text above is the Feature Gallery's own Markdown alt text for this frame, so the image describes itself identically in the wiki and here.
The interaction the harness performs
Open the command palette, type ollama, open its appearance editor, exercise deterministic random-per-repository mode, and leave a full screen of rich results (at least eight) plus the aligned, fully contained editor and Reset control visible at 1000x687.
Fixture the capture batch requires
Fresh throwaway repositories and isolated renderer profile; all persisted UI state is created through app-owned interactions or an explicitly named app-native state hook.
Privacy gate the capture must pass
Run the pre-capture renderer privacy gate used by script/capture-app.js and inspect the original client-only PNG.
Regenerating this capture
Run these commands in order, exactly as the capture batch records them. Placeholders in angle brackets are the verifier's own run root, fixture path and CDP port.
-
npx --no-install cross-env RELEASE_CHANNEL=development DESKTOP_SKIP_PACKAGE=1 yarn build:prod -
Lowlevel launch the production bundle with isolated user data and the entry fixture, perform the entry interaction exactly, then capture_screenshot(client_only=true, hwnd=<resolved-app-hwnd>, path=<owned-temp-run-root>\captures\<output>.png)
Dated acceptance receipt
One dated acceptance receipt names this exact PNG:
Undated verification documents that also name this file (indexes and ledgers, not dated acceptance evidence):