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

+18 -1
View File
@@ -1,4 +1,4 @@
# Progress — 2026-11-05
# Progress — 2026-11-06
Workflow update: the user authorizes pushing completed, verified commits to the
existing `Gitea/main` upstream from now on. See docs/decisions.md and AGENTS.md.
@@ -7,6 +7,23 @@ 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
The accepted plan is underway; its gameplay correction gate remains open.
[Integrated lifecycle trace](gameplay/jimmy-cutscene-lifecycle.md) records292 new
bounded original-code cases:96 contact,8 input/controller/skip-prefix,48 task/
objective and140 base/STOP. Complete DEFAULT pseudocode is recovered through a
verified mapped analysis carrier. None supplies a source-supported movement reset;
the original components reproduce the port's order-sensitive stale-bank writer.
A read-only Windows32 observer now launches or attaches to a verified **copied**
original. Wine32 attach/read/leave-running integration passes928 samples, with
observer exit0 and original still running. Local original rendering remains black:
only MAIN, no Jimmy/gameplay reference, was observed. Native Windows Carl state,
actual entry mode/turn, registry order and first-resume timing remain required.
All539 originals are unchanged. Runtime a2e89c6/packages dae13ac and the48-case
port diagnostic remain unchanged; no new gameplay fix or fidelity claim is made.
## Decompilation first: Carl skip-to-idle remains open
User reports the remaining tilt after skipping Carl and confirms original landing