Save Selector Map-Set Aliases

• route: map1_01a -> map2_02d
• duplicate map-set groups: 5 / selectors in duplicate groups: 13
• target alias selectors: 1:0, 10:0, 17:0
• target alias public sample count: 0
• current equals target alias plus source: True
• source+target union extra maps: map1_02b
• address predecessor equals logical predecessor map set: True
• address predecessor -> current root refs: 1
• address contiguity proves execution: False
• promotion status: blocked

The target-side map set for map2_02d has three selector aliases: 1:0, 10:0, and 17:0. Selector 1:0 is the logical selector-table predecessor and the only public-sample-covered alias; selector 10:0 is the address-adjacent root immediately before 2:0 and has many secondaryBranchState fills; selector 17:0 is another target-side alias without public sample coverage. The current 2:0 map set equals that target-side map set plus map1_01a, while source selector 0:0 plus the target-side set over-covers the current map set by map1_02b. This supports selector list recomposition/aliasing, but it still does not prove runtime execution order, state persistence into the 0x00542b0c reader, or a strict map1_01a source hotspot.

Target Alias Group

Duplicate Groups