Record Jimmy movement integration and package validation

This commit is contained in:
UnixNight committed 2026-11-05 09:56:25 -05:00
1 parent acd1b287cf
commit a61f1b0284
6 files changed
+64

No files matched your search

+2
View File
@@ -129,3 +129,5 @@ while the ordinary rendered Jimmy remains upright. Follow-up must retain source
7EC/7F0 across Bubble→ordinary and fresh/retained callback order, then verify
model pivot, takeoff, turning, landing and route returns. This is an identified
original mismatch, not a recovered behavior that is already live.
Live integration/route/native/package status (2026-11-05): [movement stabilization](jimmy-movement-stabilization.md). The audit API notes above describe the isolated component boundary; parent integration is now recorded in that continuation.
+2
View File
@@ -97,3 +97,5 @@ route/render/platform checks and root status documents; this agent made no share
runtime edits or commits. Whole-original/native Windows movement parity remains
unverified. Mouse/analog, camera side timers, generic clock registration, full
standing/pose/climb branches and engine cadence remain separate evidence gates.
Live integration/route/native/package status (2026-11-05): [movement stabilization](jimmy-movement-stabilization.md). The audit API notes above describe the isolated component boundary; parent integration is now recorded in that continuation.
@@ -104,3 +104,43 @@ The immediate throttle assertion admits that source result; the sustained manage
case still requires negative lean. Both headless and native1920×1080 SDL Bubble
replays pass all eight phases with zero validation errors. This correction changes
only the smoke predicate, not movement or gadget behavior.
## Verification and package checkpoint
The checks in scripts/test.sh pass across the main run and recorded resumed runs:
320 Python tests,2 HUD extraction checks,43 managed projects, main Vulkan replays,
asset decoder checks, dummy SDL audio/lifecycle and539 original hashes. The main
run first stopped at the obsolete Grappler attachment expectation. Its corrected
13-group suite passes; the remaining script tail then found the first-step Bubble
canonical360 smoke assumption. Corrected headless/native Bubble replays pass, and
the final GPU/save/load/animation/audio tail exits0. The initial failure logs are
preserved. This is a resumed verification record, not a claim that the initial
single script invocation exited successfully.
Artifacts under artifacts/jimmy-movement-audit: full-tests-final.log,
grappler-integrated.log, remaining-tests.log, bubble-final.log, gpu-tail.log and
validation-summary.json. These include36 main Vulkan render completion lines,
all zero validation errors, plus the corrected Bubble replay. Managed component
fixtures compare108 original observations. Both lab/underground navigation and
all source-body gates pass.
Native Linux GTX1070/private Xvfb1920×1080 runs pass walking and powered steering
with shift/right-shift/insert/keypad0/right-mouse, received SDL input and resize.
Each set of five final readbacks is byte-identical. Native Carl/control-phase,
9-stage Grappler and8-stage Bubble pass, with zero Vulkan validation errors.
Logs and captures are in window/. This is port runtime verification; actual
whole-original/native Windows gameplay remains unverified for this checkpoint.
Both self-contained packages identify clean runtime commit
`acd1b287cfdc19e6b5d16c5c10a1d9e9b90c6d41`, source_dirty=no.
Final packaging log: artifacts/jimmy-movement-audit/package-final.log. Each has519
unchanged original asset copies and4271 scene/resource files matching preparation;
package-identity.json records executable/DLL digests and build information.
Standalone Linux from /tmp with DOTNET_ROOT/DOTNET_CLI_HOME/NUGET_PACKAGES unset
passes300-step right-mouse powered flight and240-step Shift walking, received SDL
input and resize, zero validation errors. Both final readbacks match development
byte-for-byte; package-{walk,jetpack}.log and package-readbacks.json retain results.
Post-package audit verifies all539 originals unchanged. Windows cross-publishing
and resource checks do not establish native Windows gameplay. Documentation after
this runtime commit records validation; BUILD-INFO.txt preserves package provenance.
+2
View File
@@ -70,3 +70,5 @@ Two Python groups guard identity, ranges/offsets, double factors, complete fixtu
and provenance/gates. This is component execution plus managed conformance, not
whole-original/native Windows gameplay, full animation/visual-root parity or a
complete scene registry/cadence implementation. Parent records live verification.
Live integration/route/native/package status (2026-11-05): [movement stabilization](jimmy-movement-stabilization.md). The audit API notes above describe the isolated component boundary; parent integration is now recorded in that continuation.