Freshly fetched ordinary pull review bound to one exact upstream OID

What the sources record

Asset file

docs/assets/screenshots/material-pull-preview.png

Pixel dimensions

960 × 660 px, read from the PNG IHDR header

File size

62,882 bytes on disk

PNG encoding

8-bit truecolour (IHDR colour type 2)

Gallery output id

material-pull-preview

Scene

reviewed-pull-preview

Capture batch

windows-pull-preview

Platform

windows-headless

Feature Gallery section

Clone, pull, and working-tree scope

Guided workflow caption

Freshly fetched ordinary pull review bound to one exact upstream OID

Publication status

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

Current refresh gap

blocked: At the existing 200% / 480x330 logical viewport, the real pull-preview fixture renders zero complete rows inside the gate list. Required evidence: A genuine hidden-Windows-desktop 200% capture with one complete pull-preview row in the bounded list, plus the original PNG and 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 the owned local/bare-origin fixture, activate Pull, wait for the frozen fetched preview, then capture_screenshot(client_only=true, hwnd=<resolved-app-hwnd>, path=<owned-temp-run-root>\captures\material-pull-preview.png)

Alternative text

Reviewed ordinary Git pull with exact branch identities, incoming commits, changed files, and a clean-worktree confirmation gate

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

Fetch once, open the exact frozen fast-forward review, and leave branch identities, incoming commits, changed files, and clean-worktree confirmation visible without confirming Pull.

Fixture the capture batch requires

Owned bare origin, seed checkout, and app checkout where origin/main has two incoming commits and three controlled changed paths.

Privacy gate the capture must pass

Require exact reviewed upstream OID, clean-worktree gate, fixture-only paths, and an original 960x660 privacy inspection.

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 the owned local/bare-origin fixture, activate Pull, wait for the frozen fetched preview, then capture_screenshot(client_only=true, hwnd=<resolved-app-hwnd>, path=<owned-temp-run-root>\captures\material-pull-preview.png)

Dated acceptance receipt

No dated receipt under docs/verification/ names material-pull-preview.png. The frame is published without its own dated acceptance document; the build, interaction and privacy evidence for its batch is recorded in HANDOFF.md and in the Feature Gallery's refresh notes instead.

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