Restart-restored named group chip with visible repository membership and real collapse/expand behavior

What the sources record

Asset file

docs/assets/screenshots/material-tab-groups.png

Pixel dimensions

1,000 × 687 px, read from the PNG IHDR header

File size

91,222 bytes on disk

PNG encoding

8-bit truecolour (IHDR colour type 2)

Gallery output id

material-tab-groups

Scene

restored-tab-group

Capture batch

windows-ui-state-lowlevel

Platform

windows-headless

Feature Gallery section

Tab groups and command palette

Guided workflow caption

Restart-restored named group chip with visible repository membership and real collapse/expand behavior

Publication status

Published asset retained; current Windows refresh is blocked (blocked)

Current refresh gap

blocked: The disposable tab-group fixture is on a temporary drive that is unavailable after renderer reload; persisted group state was confirmed, but no current capture was produced. Required evidence: A genuine hidden-Windows-desktop run with a fixture path that remains available across reload, the original PNG, and the renderer privacy receipt. Exact batch commands: 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\material-tab-groups.png)

Alternative text

Restart-restored named tab-group chip with its visible repository member

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

Create a named colored tab group through the tab menu, relaunch the isolated profile, and leave the restored expanded group chip and member 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.

1. Step 1 of 2

   npx --no-install cross-env RELEASE_CHANNEL=development DESKTOP_SKIP_PACKAGE=1 yarn build:prod

2. Step 2 of 2

   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:

• docs/verification/tab-groups-command-palette-2026-07-22.md

Undated verification documents that also name this file (indexes and ledgers, not dated acceptance evidence):

• docs/verification/README.md

Where else this frame appears

• Open the PNG on its own
• Feature Gallery, where this frame is captioned
• Feature Gallery Markdown source
• Capture plan that declares this frame