Files
HMDesign/PORTABLE-R5-VERIFICATION.md
T

2.2 KiB

HMDesignTest Portable r5 Verification

Result

PORTABLE R5 AUTO OPEN RESULT: PARTIAL

Artifact

  • Path: HMDesignTest-Portable-Test-r5-2026-10-08.zip
  • Size: 108,382,038 bytes
  • SHA-256: 547FB98292406D5BF3FC8B8EF4FA229196115FB1C3111358B5F56EE85D6FC234
  • ZIP entries: 2,062
  • Inventory file count: 1,946
  • ZIP root: HMDesignTest/

Applied change

  • Reused the existing candidate/r4-derived portable contents.
  • Replaced only HMDesignTest/preview-server.cjs with the current source launcher.
  • Browser launch occurs from the server listening event, uses the selected 127.0.0.1 port, invokes the Windows default browser through cmd /c start, and is guarded to one launch per process.
  • Browser launch errors are reported while the server remains running and the URL is printed.

Verification

Check Result Evidence
Bundled Node runtime PASS Node v22.23.3 (x64) started the staged server
Default port 6007 PASS Server printed http://127.0.0.1:6007/
6007 collision fallback PASS Test occupant remained running; server selected port 6009 and printed its URL
Browser launch code path PASS by execution path listening invoked the launch function in both runs
Visual browser opened once NOT RUN Browser UI was not independently observable in this environment
BAT double-click NOT RUN Same limitation; equivalent bundled-node server invocation was run
Korean/space extraction path NOT RUN No separate user-style extraction/double-click run performed
Storybook render, Theme, Font, Asset NOT RUN No browser-level rendering verification claimed
Dashboard and H-2 NOT RUN Not changed or rebuilt

Source/archive note

The requested HMDesignTest-Portable-Test-r4-final-2026-10-08.zip was not present at the specified path. The existing HMDesignTest-Portable-Test-r5-candidate-2026-10-08.zip, together with PORTABLE-R4-VERIFICATION.md, was used as the preserved r4-derived staging source. The candidate launcher did not contain the browser patch; only the launcher was replaced.

Original r3/r4 archives were not overwritten. No Git commit/push, npm install/ci, production upload, component/pattern/theme change, or additional ZIP was performed.