Frame 70 of 107 · windows-branches-sheet

Branches side sheet with its tab strip, filter, branch list and merge footer at their real sizes

1280 × 900 px · 89,608 bytes · batch windows-branches-sheet

呢一頁只講一張相：邊個 scene 出，邊個 batch 收，尺寸、指令、憑證全部照抄記錄，冇記錄就照直講冇。

Branches side sheet with its Local and Remote tabs clear of the control beneath them, the default branch listed with its current-branch check, and two ordinary pill-sized merge actions in the footer — Branches side sheet with its tab strip, filter, branch list and merge footer at their real sizes

What the sources record

Asset file: docs/assets/screenshots/branches-sheet.png
Pixel dimensions: 1,280 × 900 px, read from the PNG IHDR header
File size: 89,608 bytes on disk
PNG encoding: 8-bit truecolour (IHDR colour type 2)
Gallery output id: branches-sheet
Scene: branches-sheet
Capture batch: windows-branches-sheet
Platform: windows-headless
Feature Gallery section: Search, history, accounts, and automation
Guided workflow caption: Branches side sheet with its tab strip, filter, branch list and merge footer at their real sizes
Publication status: Published target in the current Windows guided gallery

Alternative text

Branches side sheet with its Local and Remote tabs clear of the control beneath them, the default branch listed with its current-branch check, and two ordinary pill-sized merge actions in the footer

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 Branches sheet from the application menu on a throwaway single-branch repository and drop focus, so the tab strip, filter row, branch list and merge footer are all measurable in one frame.

Fixture the capture batch requires

One throwaway Git repository created by the harness, with a single commit and only its default branch — the case that exposed both defects this frame documents as fixed.

Privacy gate the capture must pass

A throwaway user-data directory, a fake HOME for Git, and a repository created inside the run root, so no real repository path or author appears in the frame.

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.

Step 1 of 2
```
yarn compile:prod
```

Step 2 of 2

node script/capture-app.js --out=<owned-run-root>ranches-sheet.png --tabs=1 --size=1280x900 --step=wait:1200 --step=menu:show-branches --step=wait:2000 --step=blur

Dated acceptance receipt

No dated receipt under docs/verification/ names branches-sheet.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.