GoldenEye USA website edition 1.0.3 — October 31, 2026
New editable entry player-1.0.3.js imports original/speed-controls-1.0.3.js, original/runtime-health-1.0.3.js and original/modern-controls-1.0.3.js. Matching source copies accompany this edition. Retained original/modern-controls-1.0.2.js, saves-1.0.1.js and data/runtime-config-1.0.1.json remain byte-for-byte unchanged, as do the supplied cartridge, standard nonthreaded WebGL2 core and runtime identity.
Background native rewind history starts disabled, including over conflicting saved frontend settings. An unchecked startup checkbox explicitly opts into EXPERIMENTAL session history with the retained 32 MiB / granularity-six configuration. History choice is fixed for that session; reload for a different choice. In the default history-off session, playback controls offer fast-forward only: when enabled, RT fast-forwards and LT keeps aiming. Experimental history can enable rewind; state-load blocking remains controlled by the unchanged save helper.
Playback diagnostics read a runtime callback counter and scoped runtime errors/context-loss events. Callback count is not FPS, rendered-frame acceptance, stage progress, game liveness or successful save evidence. A stopped counter can produce a delayed message after 15 seconds when ready/unpaused. The monitor reads no game RAM and changes no native preferences or saves.
The other-computer Dam loading/opening-scene freeze has not been reproduced here, and its cause remains unestablished. Disabling normal background history is a precaution, not proof of an Edge-specific fix. Upstream https://github.com/libretro/mupen64plus-libretro-nx/pull/662 describes an Android/OpenSL serialization deadlock; that is a platform-specific risk clue. No patch from that PR or replacement core is included.
Current candidate source verification: 33 speed/input, 28 runtime-health, 31 modern-setup and nine integration synthetic checks passed for the new five-body player. The first Edge comparison remains incomplete: both cases had black native imagery, and a minimized Edge window was observed during the candidate inspection. Wrapper responsiveness and callback counts do not establish changing native imagery or continuing native watch responsiveness. Both cases were paused/closed. A later final candidate session on an isolated foreground Microsoft Edge origin observed Dam 00 Agent world/HUD with changing weapon animation for 40.936 seconds, then native watch open, close and resumed world in order. It used one 242.359-second core launch with Original mapping, experimental history unchecked, time/cheats off, and normal Pause/close. The web Modern selection showed pending setup, unchecked acknowledgement and disabled Apply; the optional watch controller page showed 1.1 Honey, and native 2.2/Upright/Hold were not all established. No acknowledgement, Apply, physical-controller test, verified walking or manual save/load/import/export was performed. These are local observations, not proof of the other-computer freeze, its cause, experimental-history behavior or public delivery. Acceptance/freeze/publication remain separate root-owned steps. Exact eventual release scope belongs in data/stage-startup-verification-1.0.3.json and dev-blog/2026-10-31-stage-startup.html. Native save/reload, state execution, full campaign, physical-controller behavior and cheat effects remain unverified.
prepare-stage-startup-source.txt contains the bounded 1.0.2-to-1.0.3 preparation helper, retained as text to avoid server script execution. Copy/rename locally to .py for inspection/use. It verifies accepted 1.0.2, makes new ordinary copies, preserves historical metadata, and freezes only with actual source/local-Edge evidence. It never publishes or runs a browser/game. Earlier prepare-modern-controls-source.txt and prepare-renderer-repair-source.txt remain historical dated recipes; build.mjs, freeze.mjs and package.py are historical 1.0.0 recipes, not current rebuild commands.
Previous source README/file identities are under source/history/1.0.0/, source/history/1.0.1/ and source/history/1.0.2/. Exact archived releases are releases/1.0.0.json, releases/1.0.1.json and releases/1.0.2.json. Previous modules, articles and online downloadable ZIPs stay unchanged.
Stable storage identities: cosom-goldeneye-usa-v1-native; cosom-goldeneye-usa-v1-player; cosom-goldeneye-usa-v1-states; cosom-goldeneye-usa-state-v1; goldeneye-usa-v1.n64; goldeneye-usa-v1.srm (296960 bytes); cosom:goldeneye:usa:v1:mission-notebook. The native .srm is a combined N64 storage container, not raw EEPROM or a PlayStation memory card. Recognized legacy-renderer states remain in their original slots and exportable after checksum validation; loading/import requires matching runtime identity. Never migrate, delete, overwrite or relabel old states.
Modern solo controls retain native 2.2 Galore, Upright and Hold setup, explicit enablement, left movement/strafe, right look, native aiming behavior and neutral-release handling. The new 1.0.3 wrapper keeps original input active when Modern is merely selected. Its setup acknowledgement plus Apply are required before the bridge enables. This is player confirmation, not automatic detection or modification of native watch settings. State loading and rewinding reset acknowledgement. The startup history choice changes optional playback-trigger reservations without changing native preferences. Retained modern-controls-1.0.2.js stays unchanged beside the new versioned setup wrapper. See the retained dated modern-controls note for setup and actual prior check scope.
Keep private receipts, screenshots, user saves, credentials, RAM, states and session data out of public payloads. Serve the offline tree over HTTP at /n64/goldeneye-usa/ with supplied /assets/; storage requires localhost or HTTPS. Wider COSOM links require the live site. Archives exclude downloads/ to avoid recursively nesting old ZIP envelopes. Each future update needs a fresh actual dated note, preserved history, hashes/archive and guarded coordinated publication.
