LATEST LINUX RELEASE TO WINDOWS: FIX COVERAGE AUDIT

Release: Linux-with-controller-support
Archive SHA256:
c4be6ef5f27ef41a67fd9ab427e10f478ea362918bf05a44c70981b03a1f39c8
Published source base: b1fa1ca87922cd905da1be2521e412e0758b4d7e
Later release work: ce1059a06be929d413300f2663ccd7e0541a5406
The release tag and the later controller/sensor branch are not the same tree.

VFP/COLLISION AND SKYBOX
The translator uses shared per-thread VFP/FPSCR state on Windows as on Linux.
Verified the cross-function, callee-save and thread-isolation fixture passes.
This checks the regression mechanism, not every gameplay collision or scene.

ORIGINAL PHYSICS SOLVER
The donor-locked Memchr-to-memset correction is applied during generation.
Verified the 136-byte row is cleared without changing adjacent memory or
the semantics of unrelated Memchr calls.

DISPLAY AND INTERACTION
The common JNI/SDL code keeps display, surface and touch drawable sizes aligned.
Windows queries the desktop mode and defaults to DPI-aware native-resolution
borderless fullscreen. F11 toggles windowed mode; -Windowed starts windowed.
The launcher retains resolution-scaled Reanimated touch thresholds.
The original game's 1200-unit OpenGL far-plane correction is enabled.

AUDIO
The audio pacing rebuild adds donor-locked hooks only at the original EA
submit and mixer thread entries. Windows scheduling changes are scoped to
those audio threads; other guest nanosleep calls retain their original path.
Native audio sleeps use accumulated deadlines and a per-thread high-resolution
waitable timer, with handles released when guest threads exit. Two device
periods are queued before playback, within the existing bounded buffer.
The submit thread promptly refills a low queue using 1 ms yielding deadlines;
normal startup retains the 4096-frame queue. After underruns, bounded adaptive
headroom grows to at most 12288 frames at 48 kHz (256 ms), then decays after
stable playback. Resizing never clears or discards queued PCM.
The donor-reported source format remains 48000 Hz stereo; no pitch, resampling,
decoder, mix or controller-event modifications are applied for this repair.
The common host invokes the original EA mixer and supplies SDL AudioTrack PCM.
The supplied hardware log confirms the Windows WASAPI device opened at
48000 Hz, stereo. Audible playback and all campaign audio remain unverified.

SAVES
Writable userdata/var is separate from the immutable extracted APK assets.
The JNI AssetManager excludes legacy var and published/var save directories.
The launcher preserves userdata and game files when adding an HD pack.
Setup preservation is tested; campaign save/reload is a separate test.

REANIMATED AND HD TEXTURES
The common KTX/ETC1/ATC renderer was already present, but the old Windows
launcher only accepted the Fixes layout and did not set DS_HD_TEXTURES.
The updated launcher accepts the original library from either supported APK,
normalizes original assets to game/assets, and installs texture_hd KTX files.
It also supports adding the HD pack to an existing Fixes installation.
The KTX bounds, dimensions, mip data and ATC fixture passes.

ACCELEROMETER / SENSORLESS STARTUP
The later Linux branch already supplied stationary gravity when no IIO
accelerometer was available. That existing fallback is now included alongside
the real IIO code, and the native Windows branch supplies a stationary logical
sensor through the same original JNI callback and timing controls.
The Linux real-IIO, Linux sensorless and Windows sensorless fixtures pass.
This is not physical Windows gyroscope/controller-motion support.

NATIVE CONTROLLER: RECONSTRUCTED FROM THE RELEASE BINARY
The RAR contains a compiled native-controller executable, libds2controls.so,
its button-remapper C source, and three binary-only unarmed-action patches.
The committed source explicitly says the controller base is a different
implementation. ds_native_pad_hud/frame/button and their translation hooks
are absent from the release tag, later source branch and RAR.
The native module was reconstructed by tracing the unstripped Linux executable,
verifying guest function RVAs, vtables, event layouts and widget callbacks.
The Windows frontend now only publishes a locked SDL controller snapshot.
Four donor-locked generated-function hooks consume it on the guest update thread.
Movement/look use original Vector2Event dispatch; combat uses HUD semantic
actions and stomp uses original ActionEvent13. Menus use live button callbacks.
The loading-screen confirm calls the original world-start/remove-layer methods,
only after loading has finished; it never injects the screen's pointer-up event.
The latest owner-directed DS2 layout, unarmed actions, equipped-weapon guard
and D-pad Up Zero-G mapping are included without the ELF-only SDL remap shim.
The pad path has no raw touchscreen down/move/up or Android keyboard dispatch. Physical mouse
and keyboard fallback remain available separately. This is a reconstruction,
not a claim of byte-identical Linux implementation or complete-game equivalence.

ENEMY-GRAB TAP/SWIPE RESPONSE
State-9 grabs consume Cross/A as the original phase-5 semantic tap event,
right-stick flicks as native gesture displacement, and R1 through the game's
emulateGrappleGestureEvent controller routine in swipe phases 1/7. Native
handlers retain their timing, direction, target and transition checks. No
progress or animation state is forced, and a held input does not repeatedly
complete later phases. The controller never injects SDL mouse/touch input.
The host publishes only a timestamped pointer-mode flag to the SDL thread.
Capture releases during grabs/menus or stale contexts; physical cursor taps
and drags remain usable. Requested capture resumes after ordinary gameplay
returns, unless explicitly cancelled or focus was lost. Separate regressions
exercise capture intent and focus-release behavior, including uncaptured input.
Campaign enemy/grapple and motion-only coverage remains incomplete.

WINDOWS RUNTIME
The download-branch workflow tests this exact EXE and launcher on Windows,
using the genuine APKs and test-only Mesa. Check its current result and
framebuffer evidence through downloads/README.md on that branch.
Source inspection and unit fixtures are not substitutes for hardware gameplay.
