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

+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.