Recover ordered physical pair collision lifecycle
This commit is contained in:
1 parent
27d91ad697
commit
924ad2f67b
17 files changed
+815
-1
No files matched your search
@@ -1,5 +1,16 @@
|
||||
# Compatibility and validation
|
||||
|
||||
2026-11-06 pair lifecycle checkpoint:28 copied-original pair/sphere/exclusion/
|
||||
base-contact cases match the C# dispatch component's complete callbacks, contact
|
||||
masks, integration/enabled flags and roots. Fixed reference tests also pass without
|
||||
local traces. Actors, response hooks and box results are synthetic adapters;
|
||||
mode2 geometry, whole original and native Windows behavior are not established.
|
||||
The component is not admitted to live gameplay. All338 Python tests, targeted
|
||||
dynamic/body-ownership/Director checks and Debug build pass; Windows cross-publish
|
||||
succeeds with a NU1900 vulnerability-metadata warning.539 originals are unchanged.
|
||||
See [pair contract](checkpoint/pair-lifecycle.md). Package refresh is recorded
|
||||
separately; earlier BUILD-INFO identities do not describe intermediate publishing.
|
||||
|
||||
2026-11-06 TSK startup correction: the original menu creates backgroundLevel1D/
|
||||
Jimmy before successful TSK story entry, then retains that player ahead of the
|
||||
new level-game input callback. Program now models this on first story entry as
|
||||
|
||||
Reference in new issue
Block a user