The packaged Home/example/guide, State Clear bends/Undo/Redo, picker dismissal, immediate attachment cancellation, Save and fresh-process reopen workflows passed on Windows. This is bounded prerelease acceptance, not completion of the full application specification. The package is the unchanged release ZIP 5554e32533e3cb2c33fb4143a5a0902733d5a8d47577303cb2842d268e7bc76d (34,168,661 bytes), tested by launching its extracted executable with a private profile, restricted PATH and unrelated working directory.

The evidence archive is native-gui-715036e.zip, SHA-256 f18c21d262ca78bc9c2d8a339c3389fa31c50a81187cc53cc472f3253cda2815 (10,357,627 bytes, 351 members). Extract it to inspect reviews/native-observations.md, the predeclared workflow in recipes/PLAN.md, and raw results under native/. Absolute paths in raw receipts identify this builder machine; peers consume the archived bytes and published commit references.

Check	Result
Complete saved Project comparisons	Ten passes: B/C/B/C/P/P/P/P/C/P
Clear bends, Undo, Redo	Authored square disappears/restores/disappears; exact saved C/B/C
Show-unplaced and Add existing type popups	First Escape dismisses only popup; dialog query/filter retained; outside dismissal and second Escape cancellation work
Source/target attachment cancellation	Immediate Escape restores Select/move; exact P and saved-source bytes retained
Fresh-process reopening	Exact C and P; saved-source bytes match earlier accepted checkpoints
Two launched GUI runs	Normal Alt+F4 observed; exit0, empty logs, unchanged package

The original restart harness refused before launching run02 because its reused working directory contained cache files. The original failed attempt and file inventory are preserved in reviews/cwd-incident.json. Independently reviewed launcher v2 used a fresh working directory for run03 with the same package/profile/environment. Cache attribution remains unproven; no product crash or silent failed-test replacement is claimed.

State label congestion (#36) remains visible. This trial does not establish broad accessibility/DPI/performance, all OA/SA workflows, held-drag/reconnect coverage, physically disconnected operation, or Linux support. Independent downloaded-package QA and release publication are separate coordination steps in Gitea #37.

Source 715036e132677dd2bc2fb37ed316d93dc9987aec. Every launched GUI run has a terminal close receipt. Failed prelaunch run directories remain identified separately, with original cwd cache metadata/digests in the incident. Original staging manifest SHA-256 c90371bee1c2b2ae850b5d8e64ab9f1368f541ef51104e3b888a721e05d49c13 is preserved verbatim in the ZIP. All saved-source snapshots, complete typed expected Projects, actual comparator outputs, captures and metadata, launch/close logs and immutable evaluator recipes are included. Individual failures remain labelled as recorded; mechanical acceptance is reported in manifest.json, not inferred from screenshots. Package/helper provenance is bound to c82eca1eca204dd28994f5c2e8595d8acd2e148e package-server evidence. Executables, private profile and unrelated-cwd contents are omitted. No broader GUI or release completeness is claimed. Each ZIP member was reread for exact bytes, SHA-256 and CRC. Normal-close cause and visual acceptance need the parent review.