Trace Carl lifecycle and add read-only original state observer

This commit is contained in:
UnixNight committed 2026-11-06 10:27:10 -05:00
1 parent c642b69849
commit 4cd62d3627
28 files changed
+2387 -5

No files matched your search

+8
View File
@@ -1,5 +1,13 @@
# Core architecture coverage map
2026-11-06: [Carl lifecycle trace](../gameplay/jimmy-cutscene-lifecycle.md) adds
292 bounded original-code cases and closes local contact/task/animation/STOP and
DEFAULT-provider questions. Actual first-resumed-frame state remains unobserved.
The new original-state observer passes Wine32 attach/read/leave-running; local
original captures show MAIN only and remain visually unusable. This expands S/P
and investigation-tool coverage, not original gameplay comparison or a new port fix.
MOVE/CONTROL/INPUT's Carl gate and full-body/OMT dependencies stay open.
2026-11-05 follow-up: camera-entry reset is verified, but post-skip neutral idle
remains a port bug. CONTROL/INPUT/skip coverage is reopened around Carl's full
lifecycle;48 port traces and additional original boundaries are documented in
+6
View File
@@ -5,6 +5,12 @@ Gameplay expansion remains paused. Current research checkpoint68154df preserves
runtime a2e89c6 and packaged runtime dae13ac. This plan does not mark the remaining
post-skip tilt fixed or authorize an unsupported rotation reset.
Execution update2026-11-06: [integrated lifecycle findings](../gameplay/jimmy-cutscene-lifecycle.md)
add292 bounded original-code cases, complete DEFAULT recovery and a working
read-only copied-original observer. Steps1–2 remain open at the actual original
Carl entry/resumed-frame observation. Step3 has not begun; source composition
agrees with the port's stale writer under the same synthetic order/state.
## Objective
Establish the original ownership and timing of player state across gameplay,