Clarify loader defaults provenance and record checkpoint packages
This commit is contained in:
1 parent
531883aaac
commit
117db77c7b
6 files changed
+43
-5
No files matched your search
@@ -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
|
||||
|
||||
Reference in new issue
Block a user