What changed
The original Japanese player starts with Create or Load for a local .snessave session. Its native cartridge and retained SNES engine bytes are unchanged.
With write access, a source-verified completed original Save updates the same selected file. The success notice follows the completed write, close and complete file readback.
Session files retain the original state plus Matchbox version2 metadata and the existing walkthrough history and manual corrections. Browser snapshots and portable exports keep their existing namespaces and formats.
Older .shadowrun-original files keep the original v1 JSON format on same-file saves. Raw states require explicit game association; preserving enhancement metadata may require Save as to a new bound session file.
File selection and restore hold keyboard, touch and controller input. A restored position must be observed byte-exact in the native core before controls and snapshot capture resume.
Read-only files remain loadable. Explicit permission, Save as with a new filename and Download a copy are separate actions; a download request never claims the original file was updated.
Verification
Native source tests:28 checks across retained modern and legacy cores,120 polling-cadence cases, both original slots and repeated saves with identical SRAM. Cancel, No, Cortex-blocked saves and load boundaries do not create completed-save events.
Paired codec8 tests, runtime9 tests, serialized-restore tracker8 tests, startup-reader7 tests, native witness9 tests, complete adapter6 model tests and guide-startup5 model tests passed. These retain the distinction between mock-handle checks and actual disk persistence.
The shared source freeze records69 core tests with212 assertions and196 controlled-DOM UI checks.
Actual generated-file browser tests passed: native Create/Open, repeated original Save to the same OS file with readback, cancel without writing, Save as to a second new filename and fresh reload. The final build restored the saved Matchbox unlock and manual walkthrough choice; download-mode reload left the source file unchanged.
The nonfield startup reader was checked against16 actual boot samples with zero heap scans or state changes. The final browser reload completed with no diagnostic errors; initialized gameplay retains its original exact live-allocation verification.
Limits
Direct updates require a browser-granted writable file handle. The in-app browser may reopen an existing file read-only and deny write permission; use a new Save as filename or a downloaded copy in that case.
Create and Save as require a new filename. Do not replace an existing file through the in-app browser Save picker: its host may truncate the file before returning control to the page.
A download starts a new copy and requires the player to keep it. It does not overwrite or verify an existing local file.
A complete Japanese campaign and physical controller hardware were not tested. The separate JavaScript recreation remains incomplete at0.13.0; its saves remain separate.