test(release): complete deferred packaged-Windows v0.7.2 GUI save smoke

[scawful]

Context

PR #69 cut the tested v0.7.2 release candidate while explicitly deferring the remaining interactive packaged-Windows GUI smoke. Automated hosted Windows build/test/package checks are green, but the native desktop interaction path still needs one focused follow-up when Windows testing resumes.

Release candidate evidence:

• PR [release] Prepare yaze 0.7.2 metadata #69 candidate: 24a2504c6be22f3321e44a01805f52127925c3ce
• merged release commit: 8fed46dcbe2006fcb9aea856fe9bed46ab12b03f
• exact-candidate Release dry run: 29460874535
• Windows artifact: 8362116237
• v0.7.2 portable zip SHA-256: 94cfe092c54a906338eda312db4f45ef12ef751cab86f88be42bf052d0fd235f

Acceptance criteria

On an interactive Windows desktop, using the packaged v0.7.2 artifacts:

• Extract/install and launch yaze.exe successfully.
• Open a clean/disposable ROM.
• Use Save As to create a separate ROM.
• Reopen the saved ROM in packaged yaze.exe.
• Run packaged z3ed.exe rom-doctor --rom <saved-copy> --format json and attach the result.
• Record Windows version, artifact checksum, and pass/fail notes.

Hotfix threshold

A reproducible packaged-Windows startup, runtime-DLL, file-dialog, Save As, reopen, or ROM-integrity regression is v0.7.2 hotfix criteria. Do not broaden this issue into general Windows automation work.