Narrow tier2 kind-8 setup gate role

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

@@ -138,6 +138,17 @@ So the bridge is now narrower and more concrete:
 - 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
 
+The `+0x20` side is tighter in a second way too. Current grounded downstream consumers of the
+mirrored world byte `[world+0x66de]` are mostly:
+
+- the editor metadata checkbox or campaign-scenario flag path
+- the campaign-gated branches inside
+  `0x00442c30 shell_apply_scenario_name_specific_post_load_world_and_object_fixups`
+
+The currently grounded Tier 2 relevance of `+0x20` therefore reads more like a branch gate on the
+selected-year/reactivation path inside `0x00436d10 / 0x00443a50`, not like a later direct input to
+`0x00435630 / 0x00412bd0 / 0x00412c10` through the ordinary `[world+0x66de]` consumer set.
+
 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

docs/rehost-queue.md

@@ -592,7 +592,12 @@ Working rule:
     stays zero across the checked recipe-book surface while `Louisiana.gmp` keeps the sparse
     nonzero `book00` profile. So the next pass should keep the setup bridge narrowed to the
     unique `+0x20` campaign/setup-byte side while still treating the sparse recipe/runtime family
-    as the stronger remaining differentiator.
+    as the stronger remaining differentiator. The same note now also sharpens the `+0x20` bridge
+    itself: current grounded downstream consumers of mirrored `[world+0x66de]` are mostly the
+    editor metadata checkbox and campaign-gated branches inside `0x00442c30`, not the core
+    Tier 2 helpers directly. So the likely Tier 2 relevance of `+0x20` is the branch gate inside
+    `0x00436d10 / 0x00443a50` before the rebuild family runs, not a later direct
+    `[world+0x66de] -> 0x00435630/0x00412bd0/0x00412c10` data path.
     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: