Live public Bambu build inventory with ten tracked Release-backed pointer objects

What the sources record

Asset file

docs/assets/screenshots/cheap-lfs-bambu-build-live.png

Pixel dimensions

960 × 660 px, read from the PNG IHDR header

File size

98,404 bytes on disk

PNG encoding

8-bit truecolour (IHDR colour type 2)

Gallery output id

cheap-lfs-bambu-build-live

Scene

bambu-build-live-inventory

Capture batch

windows-cheap-lfs-live

Platform

windows-headless

Feature Gallery section

Large-file commit preparation

Guided workflow caption

Live public Bambu build inventory with ten tracked Release-backed pointer objects

Publication status

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

Current refresh gap

blocked: The live Cheap LFS scene needs its bespoke sparse-file/provider fixture; it was not re-run by the canonical gallery refresh. Required evidence: A genuine hidden-Windows-desktop run of the owning Cheap LFS live fixture, its original PNG, and the scene 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 named disposable Cheap LFS fixture, perform the entry interaction exactly, then capture_screenshot(client_only=true, hwnd=<resolved-app-hwnd>, path=<owned-temp-run-root>\captures\cheap-lfs-bambu-build-live.png)

Alternative text

Live public Bambu build Cheap LFS inventory with ten tracked Release-backed pointer objects

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

Clone the public Bambu build fixture afresh, open Cheap LFS, and show its ten verified Release-backed pointers without exposing an account.

Fixture the capture batch requires

A newly cloned or newly created fixture named by the entry; never a developer checkout. Provider mutation is allowed only where the entry explicitly requires it.

Privacy gate the capture must pass

Use synthetic filenames and example.invalid identity; scan the renderer and original PNG for credentials, signed URLs, personal email, and user paths.

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 named disposable Cheap LFS 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

No dated receipt under docs/verification/ names cheap-lfs-bambu-build-live.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