Bind world-region restore callback strip

This commit is contained in:
Jan Petykiewicz 2026-04-18 13:18:10 -07:00
commit 2d2a83957f
3 changed files with 21 additions and 11 deletions

View file

@ -3650,6 +3650,10 @@ fn build_region_service_trace_report(
"0x00421510 world_region_collection_refresh_records_from_tagged_bundle".to_string(),
"0x0041f5c0 world_region_load_tagged_payload_and_profile_collection_0x37f".to_string(),
"0x00455fc0 shared region tagged-payload reload companion".to_string(),
"0x00455870 region triplet-band tagged restore callback (world-region vtable +0x48)"
.to_string(),
"0x00455930 region triplet-band tagged serializer callback (world-region vtable +0x4c)"
.to_string(),
];
let next_owner_questions = vec![
"Which persisted owner seam rebuilds or restores [region+0x25e/+0x276/+0x302/+0x316]?".to_string(),
@ -3696,11 +3700,12 @@ fn build_region_service_trace_report(
"the checked-in function map already grounds 0x00421510 as the tagged region-collection load owner that dispatches each live record through vtable slot +0x40".to_string(),
"the checked-in function map already grounds 0x0041f5c0 as the per-record load slot that reloads the tagged payload through 0x00455fc0 and then rebuilds profile collection [region+0x37f]".to_string(),
"constructor-side evidence now proves the latches are initialized locally, so the remaining gap can legitimately be framed as post-construction restore or rebuild".to_string(),
"direct disassembly of 0x00455fc0 now shows the shared loader only clearing and reseeding the common 0x23a-family string/scalar bands before dispatching vtable slot +0x48, which means [region+0x276/+0x302/+0x316] are not restored directly by that shared helper".to_string(),
"direct disassembly of 0x0041f590/0x0041f5b0 now proves the world-region vtable root is 0x005c9a28, so the 0x00455fc0 dispatch at slot +0x48 lands on 0x00455870 and the serializer sibling at +0x4c lands on 0x00455930".to_string(),
"direct disassembly of 0x00455870/0x00455930 now shows that callback pair only restores and serializes two triplet-like three-lane scalar bands through 0x531150/0x531030 plus 0x530720/0x52e8b0, not [region+0x276/+0x302/+0x316]".to_string(),
],
blockers: vec![
"which region-specific vtable slot +0x48 callback runs after 0x00455fc0 on the world-region table".to_string(),
"whether [region+0x276/+0x302/+0x316] are serialized in that region-specific callback or rebuilt immediately after payload load".to_string(),
"which later restore or rebuild owner rehydrates [region+0x276/+0x302/+0x316] after the shared payload loader and triplet-band callback complete".to_string(),
"whether [region+0x25e] severity/source and any stable region id/class discriminator are serialized elsewhere in the tagged region body or recomputed immediately post-load".to_string(),
],
},
SmpServiceConsumerHypothesis {
@ -21853,7 +21858,7 @@ mod tests {
assert_eq!(trace.queued_notice_record_count, 0);
assert!(!trace.atlas_candidate_consumers.is_empty());
assert_eq!(trace.known_owner_bridge_fields.len(), 6);
assert_eq!(trace.known_bridge_helpers.len(), 9);
assert_eq!(trace.known_bridge_helpers.len(), 11);
assert_eq!(trace.next_owner_questions.len(), 3);
assert_eq!(trace.candidate_consumer_hypotheses.len(), 4);
assert_eq!(