Bound tier2 kind-8 setup profile bridge

artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-setup-core-note.md

@@ -93,6 +93,55 @@ One narrower outlier still survives that wider scan:
   - `Spanish Mainline.gmp`: same header pair, but `payload_word_0x14 = 1876`,
     `payload_byte_0x20 = 0xe3`, `payload_word_0x3b2 = 1`
 
+## Known owner path for the compared fields
+
+The named consumer path for the compared setup-core fields is now bounded too:
+
+- `0x00442400`
+  `shell_setup_load_selected_profile_bundle_into_payload_record`
+  materializes the larger setup payload record from the map-style chunk family
+- `0x00502220`
+  `shell_setup_window_publish_selected_profile_labels_and_preview_surface`
+  then copies the small compared field set through
+- `0x0047be50`
+  `shell_setup_profile_copy_payload_scroll_count_and_campaign_byte_and_seed_row_categories`
+
+That grounded copy path currently lands on staged runtime-profile fields, not on the Tier 2
+candidate rebuild strip directly:
+
+- payload `+0x14 -> [profile+0x77]`
+- payload `+0x3b2 -> [profile+0x79]`
+- payload `+0x3ba -> [profile+0x7b]`
+- payload `+0x20 -> [profile+0xc5]`
+
+That setup/profile bridge is not the end of the path, though. The later scenario reset or
+reactivation owners already import a subset of those staged values back into the live world before
+the coupled Tier 2 rebuild strip runs:
+
+- `0x00436d10`
+  `scenario_state_reset_defaults_seed_named_availability_collections_and_rebuild_runtime_bridges`
+  checks `[profile+0xc5]` and, when the setup-not-sandbox branch is active, copies
+  `[profile+0x77]` into the selected-year world lanes before rerunning
+  `0x00435603`, `0x00435630`, `0x0041e970`, `0x00412bd0`, `0x00434130`, and `0x00436af0`
+- `0x00443a50`
+  `world_entry_transition_and_runtime_bringup`
+  mirrors `[profile+0xc5]` into `[world+0x66de]`, restores the selected-year lane from
+  `[profile+0x77]`, and then re-enters the same rebuild family in the load-side rehydrate band
+
+So the bridge is now narrower and more concrete:
+
+- setup payload `+0x14 -> [profile+0x77] -> selected-year restore -> Tier 2 rebuild family`
+- setup payload `+0x20 -> [profile+0xc5] -> campaign/setup gate -> world-entry/reset branch`
+- setup payload `+0x3b2/+0x3ba -> [profile+0x79/+0x7b]` are still only grounded on the setup-side
+  panel and scroll-threshold path, not yet on the later Tier 2 rebuild owners
+
+That means the next upstream question is now smaller than before:
+
+- whether `Louisiana.gmp`'s unique `+0x14/+0x20` setup-core pair is enough to explain its coupled
+  Tier 2 runtime shape through the already-grounded `[profile+0x77/+0xc5]` bridge
+- or whether the remaining differentiator still sits elsewhere, most likely in the sparse
+  recipe/runtime side rather than the setup-panel-only `+0x3b2/+0x3ba` pair
+
 ## Current implication
 
 The upstream side of the Tier 2 strip is now bounded more tightly:

docs/rehost-queue.md

@@ -565,7 +565,19 @@ Working rule:
     (`payload_word_0x14 = 1870`, `payload_byte_0x20 = 0x3a`, `payload_word_0x3b2 = 2`,
     `candidate_header = 0xcdcdcdcd / 0xcdcdcdcd`) is still unique across the 41-map corpus even
     after the coarse header class is demoted, so the next pass should compare that tighter tuple to
-    the sparse recipe/runtime family rather than reopening the broad header-pair question.
+    the sparse recipe/runtime family rather than reopening the broad header-pair question. The same
+    note now also carries the grounded owner bridge for those compared setup-core fields. The early
+    copy path is still `0x00442400 -> 0x00502220 -> 0x0047be50`, but the later reset or
+    reactivation owners are now bounded too:
+    `0x00436d10` and `0x00443a50` both reimport the staged subset
+    `[profile+0x77/+0xc5]` before rerunning the same rebuild family that includes
+    `0x00435603`, `0x00435630`, `0x0041e970`, `0x00412bd0`, `0x00434130`, and `0x00436af0`.
+    That narrows the open question again:
+    `+0x14/+0x20` now have one real bridge into the Tier 2 strip through
+    `[profile+0x77/+0xc5]`, while `+0x3b2/+0x3ba` still stop on the setup-panel threshold or
+    scroll path. The next pass should therefore test whether the unique `Louisiana.gmp`
+    `+0x14/+0x20` pair is enough to explain its Tier 2 runtime shape through that grounded bridge,
+    or whether the sparse recipe/runtime side is still the more plausible differentiator.
     kinds”; it is the smaller set of scenario-specific records where that sweep explicitly writes
     `[event+0x7ef]` itself or a still-later owner does.
   - two explicit trigger-kind materializations are now grounded inside that retagger: