Clarify loader defaults provenance and record checkpoint packages

This commit is contained in:
UnixNight committed 2026-10-25 12:59:09 -04:00
1 parent 531883aaac
commit 117db77c7b
6 files changed
+43 -5

No files matched your search

+14
View File
@@ -45,6 +45,20 @@ in `artifacts/re-checkpoint/python-final.log`. Build succeeds without warnings.
These are port/static checks; no new native Windows runtime or original whole-game
runtime verification is claimed. Physical audio and original cadence remain open.
Self-contained Linux/Windows packages were rebuilt by `scripts/package.sh` from
clean531883a; both BUILD-INFO records identify that source and source_dirty=no.
The preserved baseline DLL hash remains distinct from the new binary. Linux
release launch from `/tmp` passes the60-frame Carl cutscene held-input lock check
(`linux-package-carl.log`); validation layers were unavailable in that package
invocation, unlike the enabled full integration runs. Subsequent changes only
refine loader evidence and this validation record, not runtime code.
Final loader consistency review verifies that the lab predicate-zero writer is
in class-default initialization44D3D0, reached from constructor44F3B3 through
4749A0→completeB4→44F4B0. It is not inside base constructor44D2B0. Five targeted
loader regressions pass after adding that provenance. This strengthens the
old-game lifetime question rather than silently assuming pointer overwrite deletes it.
## Plan continuation and exact next gates
C3 investigation recovered fresh game input→Jimmy→fire order after physics. C5
+14 -5
View File
@@ -65,15 +65,24 @@ can be fields on the character object across a scene change. It does not prove
every character field remains unchanged: initialization, property loading,
gadget cleanup and PostLoad can reset fields independently.
The lab game object also explicitly sets predicate0 at44D456/44D472. An object's
The lab game object's class-default initializer sets predicate0 at44D456/44D472;
this is **not inside the constructor44D2B0 body** (which returns44D350).
Normal factory construction does nevertheless reach it: LV1B constructor44F300
installs derived vtables44F36A/44F37C, passes its+8C interface to4749A0 at44F3B3,
and4749BE..4749CA converts back to complete and dispatches virtualB4. Complete
vtable4C3CD0+B4 resolves44F4B0, which calls base class-default initializer44D3D0
at44F4D5. Therefore this writer is constructor-reachable through an explicit
virtual defaults bridge, not inferred from proximity or an editor-only caller.
An object's
retention and the current-level global509948 are distinct: GAM loading assigns
509948 to the destination's game object at46E360 after factory construction.
Further class-specific lifecycle flags or later predicate changes require their
own evidence; do not generalize the constructor default into a full object map.
**Critical integration consistency gate: old level-game ownership.** The lab game
is itself selected for preservation (interface4C386C slots200/204 resolve
4719B0/C0;44D456 pushes0 before44D472 dispatches204). Ordinary GAM loading then
is initialized for preservation (interface4C386C slots200/204 resolve
4719B0/C0; defaults bridge above reaches44D456's push0/44D472's dispatch204).
Later changes to that predicate remain part of the lifetime audit. GAM loading then
constructs a new destination game. A bounded inspection of46E170 through factory
46E335 found prefix46E26C→4766E0, whose literal is`UnInitCaptions()` and whose
registry is5099FC;46E271→479000 clears physics records rooted509B04. Neither
@@ -186,8 +195,8 @@ transferring every arbitrary field unchanged would still be unsupported. The
source chain and editor-reset correction replace an unbounded “loader unknown”
task with these concrete tests.
Validation: five Python tests pass, covering the original hash,39 exact byte
sites,14 virtual targets, object factory/destruction/timer dependencies and R key
Validation: five Python tests pass, covering the original hash,42 exact byte
sites,15 virtual targets, object factory/destruction/timer dependencies and R key
identity. Run `python3 -m unittest discover -s tests -p
test_checkpoint_scene_loader.py -v`. Helper JSON is reproducible with
`python3 tools/binary/checkpoint_scene_loader.py ../Original`. These are static