Record airborne bridge regression and package verification

This commit is contained in:
UnixNight committed 2026-11-05 10:28:10 -05:00
1 parent 27be8ed630
commit 3845ea7114
4 files changed
+53 -9

No files matched your search

+31 -1
View File
@@ -43,7 +43,7 @@ with body motion, so enabling/debug-stopping flight cannot retain an unseen tilt
request. This is modern tool policy, separate from original script preparation.
Script STOP still preserves destination and queued body/effect work.
## Verification in progress
## Component and integration verification
12 destination observations compare against the managed target helper. New
integrated cases cover Init/dirty/current writes, control locks, ordinary tilt,
@@ -87,3 +87,33 @@ The300-step fixture travels359.19 versus the prior flat-air403.88; maximum rise
measurement, not original whole-game trajectory evidence. Native Carl input lock
and control-independent body/fire/resumption also pass. Logs, images and all25
hashes: artifacts/jimmy-air-bridge/window/.
### Whole regression verification
All checks in scripts/test.sh complete across the main invocation and recorded
resumption:325 Python tests,2 HUD extraction tests,44 managed projects,36 main
Vulkan render completions, asset decoder checks, save/load, animation and SDL
dummy audio/lifecycle, plus539 unchanged originals. The initial invocation stopped
at a Director fixture that expected a tilt to survive five active ground-input
steps without full-Euler sync. Its corrected fixture seeds current tilt immediately
before the command, preserving the test's intended camera-vs-AI preparation
boundary; the Director suite passes. The resumed tail is retained separately.
This records the resumed checks, not a successful exit of the initial invocation.
Logs: artifacts/jimmy-air-bridge/full-tests.log, director-corrected.log and
test-tail.log. No gameplay math was tuned to restore obsolete fixture assumptions.
### Packaged checkpoint
Both self-contained packages identify clean runtime commit
`27be8ed63079ae2e3bf7e965ee205c4a57a96559`, source_dirty=no. Each contains519
unchanged original asset copies and4271 scene/resource files matching preparation.
Artifacts: package.log and package-identity.json. Standalone Linux from /tmp with
DOTNET_ROOT/DOTNET_CLI_HOME/NUGET_PACKAGES unset passes right-mouse powered flight
and Shift walking with actual SDL input/resize, zero Vulkan validation errors.
All five final/forward/braking/ordinary-air readbacks match development byte-for-byte;
package-{walk,jetpack}.log and package-readbacks.json retain evidence. Post-package
original audit verifies all539 hashes unchanged. Windows cross-build/resource
checks remain distinct from native Windows and whole-original gameplay verification.
Subsequent documentation commits record validation; package BUILD-INFO preserves
its exact runtime source provenance.
+5 -8
View File
@@ -121,13 +121,10 @@ facing interpolation, body or original whole-game entrypoint ran. A Python guard
checks source/provenance and saved writes; this is recovery evidence, not a
managed/runtime implementation claim.
Live ordinary-air pitch targets are deliberately still the baseline simplification.
The source-backed input/velocity helper is integrated, but enabling this target
requires the full Euler/actor-root visual bridge and retained mode-field ownership
to move together. Otherwise horizontal velocity would gain pitch attenuation
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.
At the initial controller checkpoint these targets stayed behind the paired
render/state gate. They are now live with retained apply-owned seeds, destination
Init/dirty and the logical-root hierarchical render bridge. See
[air bridge](jimmy-air-bridge.md) for implementation,146 component comparisons,
route/native/package verification and remaining visual precision/body limits.
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.