Frame 95 of 107 · windows-private-badge
Explicit private-metadata lock retained beside the repository logo
960 × 660 px · 87,517 bytes · batch windows-private-badge
呢一頁只講一張相：邊個 scene 出，邊個 batch 收，尺寸、指令、憑證全部照抄記錄，冇記錄就照直講冇。
What the sources record
- Asset file
- docs/assets/screenshots/private-repository-lock-badge.png
- Pixel dimensions
- 960 × 660 px, read from the PNG IHDR header
- File size
- 87,517 bytes on disk
- PNG encoding
- 8-bit truecolour (IHDR colour type 2)
- Gallery output id
- private-repository-lock-badge
- Scene
- exact-private-metadata-badge
- Capture batch
- windows-private-badge
- Platform
- windows-headless
- Feature Gallery section
- Repository administration
- Guided workflow caption
- Explicit private-metadata lock retained beside the repository logo
- Publication status
- Published asset retained; current Windows refresh is blocked (blocked)
- Current refresh gap
- blocked: At the existing 200% / 480x330 logical viewport, the real private-repository fixture renders zero complete rows inside the gate list. Required evidence: A genuine hidden-Windows-desktop 200% capture with one complete private-repository 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 disposable repository, set exact isPrivate=true through the app-native state hook, open the repository picker, then capture_screenshot(client_only=true, hwnd=<resolved-app-hwnd>, path=<owned-temp-run-root>\captures\private-repository-lock-badge.png)
Alternative text
Repository picker showing the private-repository lock beside the
repository logo
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 repository picker after the app-native hook sets exact private metadata; retain the ordinary repository logo and separate focusable localized lock.
Fixture the capture batch requires
One disposable repository and deterministic exact private metadata; no provider inference, account, or network lookup.
Privacy gate the capture must pass
Assert the lock is driven by exact isPrivate=true, then scan the renderer and original 960x660 frame for user paths and credentials.
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 the disposable repository, set exact isPrivate=true through the app-native state hook, open the repository picker, then capture_screenshot(client_only=true, hwnd=<resolved-app-hwnd>, path=<owned-temp-run-root>\captures\private-repository-lock-badge.png)
Dated acceptance receipt
No dated receipt under docs/verification/ names
private-repository-lock-badge.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.