Narrow tier2 kind-8 setup core path

docs/rehost-queue.md

@@ -542,6 +542,21 @@ Working rule:
     `0x004120b0 -> 0x00412d70 -> 0x00412ab0 -> 0x00412c10`.
     That keeps the next pass focused on the internal sequencing and handoff across the coupled
     recipe/runtime/availability rebuild strip, not on one isolated helper.
+    The same note now carries the first upstream feed-in difference too:
+    `compare-setup-payload-core Louisiana.gmp Dutchlantis.gmp` already differs on
+    `payload_word_0x14` (`1870` vs `2025`), `payload_byte_0x20` (`0x3a` vs `0xfd`),
+    `payload_word_0x3b2` (`2` vs `1`), and the candidate-header words
+    (`0xcdcdcdcd` vs `0x00000000`). So the next pass can now work on both sides of the coupled
+    Tier 2 strip: the upstream setup payload core and the downstream recipe/runtime rebuild loop.
+  - the carrier-set setup-core comparison is checked in now too:
+    `artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-setup-core-note.md`
+    widens that upstream comparison across all six bundled add-building carriers. It shows
+    `Louisiana.gmp` is not unique on `payload_word_0x3b2` (`Chicago to New York.gmp` also has `2`)
+    but is unique among the shipped carrier set on the candidate-header sentinel pair
+    `0xcdcdcdcd / 0xcdcdcdcd`, while `Alternate USA.gmp` stays separately unique on the
+    recognized `rt3-105-map-container-v1` header pair. That narrows the next upstream Tier 2
+    question to whether the `Louisiana` candidate-header state actually matters to the coupled
+    rebuild strip or is just another container-side artifact.
     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: