# Review scope: Carry a four-file selection into a completed project set

Draft; changes required. An empty project-file dialog opens a separate OS picker. Four of seven file rows select cumulatively, then the picker dismisses through an empty return frame. Four pending rows appear together; one file glyph resolves first, then the remaining three resolve with a stable-identity row reorder. The restored home shows four files using a three-icon stack. Original garden and workshop file records replace source names, metadata and branding. Camera, exposure, fades, pointer and ring rotation are authored approximations. No generated answer or instruction edit is shown. Parent-informed sampled still review only; no independent moving or native Resolve approval.

The parent inspected source overview and boundary samples before building, then
sampled actual candidate renders. This was not a fresh independent or blind
review. No perceived moving-source review, native Resolve execution or source-
quality approval is claimed. The retained complete rendition was decoded at its actual integer PTS. It is not
asserted equivalent to an absent historical master. Research excerpts
are 960×540, while the new outputs are 1920×1080. No source image is a renderer input.

Selected native source interval: [630,952),
24/1 fps. The discrete replacement gates are observed at native frames.
Project/dialog geometry, camera transforms, blur, picker opacity, pointer path, ring rotation, background and art are authored approximations. Cumulative selection, pending rows, staged glyph completion, the B/C identity reorder and restored four-file home retain observed native gates. The last twelve context frames overlap the following instruction study, but no instruction edit or shared action is counted twice.
Source material, production detail and typography are not reproduced exactly.

The two content variants form one candidate. Resolve delivery comprises a manual
construction guide and generated controls, not an executed or verified .drp file.
Existing pinned dependencies support the checks; a clean npm install was not run.