Preserve retained Jimmy update order on initial story entry

This commit is contained in:
UnixNight committed 2026-11-06 17:08:59 -05:00
1 parent 4cd62d3627
commit ea04210f52
24 files changed
+1209 -22

No files matched your search

+30 -1
View File
@@ -7,7 +7,36 @@ Next-work plan: [recover interactions, then implement verified changes](checkpoi
It defines the Carl source/differential gate, the bounded implementation step,
movement/contact/animation recovery and the end-to-end platform checkpoint.
## Carl lifecycle investigation and original-state observer
## Carl neutral return: TSK startup lifetime correction
[Menu/player lifetime](gameplay/main-menu-player-lifetime.md) closes the missing
ordering distinction: the original initializes a backgroundLevel1D/Jimmy before
a successful TSK story load. The loader retains Jimmy and appends the new level
game later. First playable story entry therefore uses player-before-input, just
like subsequent retained transitions. Fresh direct-GAM order remains separate.
Program previously used that order only when carriedSave was non-null. The
correction includes TSK-backed story entry and adds no movement/Euler reset.
The strengthened Vulkan control-phase replay fails on baseline neutral tick0
(destination roll−10.000001), then passes first input plus300 idle ticks after
the correction, preserving heading and held-input/body/fire continuation.
Eight managed trajectories coverLeft/Right, natural/skip and repeated scenes.
All336 Python+2 HUD, managed projects and36 GPU/render passes succeed. Native Linux
SDL/Vulkan1920×1080 control replay and VR04 powered keyboard/steering/resize pass
with zero validation errors; the first returned-frame readback is inspected upright.
Final build has zero warnings/errors; Windows x64 cross-publish passes. Source/
test provenance is in artifacts/main-menu-player-lifetime/verified-change.json.
Clean package validation follows; historical a2e89c6/dae13ac is not the identity of
an in-progress cross-build. Native Windows/original Carl execution stays unverified.
The additional derived-frame caller50 native cases and static body/visual-sync
audit close their bounded omissions. A matched original-resolution Wine startup
diagnostic progresses to backgroundJimmy allocation only after the recorded
repaint acknowledgement; frames remain black. See
[startup observations](gameplay/original-startup-diagnostic.md). These are
perturbed allocation observations, not full original Carl or Windows fidelity.
## Earlier Carl lifecycle investigation and original-state observer
The accepted plan is underway; its gameplay correction gate remains open.
[Integrated lifecycle trace](gameplay/jimmy-cutscene-lifecycle.md) records292 new