Favor tier2 kind-8 recipe profile over header peers

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

@@ -211,6 +211,18 @@ So the only current `+0x14` bridge peer does **not** reproduce the sparse `Louis
 profile. That keeps the recipe/runtime side as the stronger remaining differentiator even after the
 setup bridge was narrowed to `+0x14/+0x20`.
 
+One same-header-class check points the same way:
+
+- `compare-recipe-book-lines Louisiana.gmp "Argentina Opens Up.gmp"`
+  keeps `Louisiana.gmp` sparse while the same `0xcdcdcdcd / 0xcdcdcdcd` header-class peer stays
+  broader
+- `Louisiana.gmp` still only keeps nonzero `book00`
+- `Argentina Opens Up.gmp` keeps additional mixed `book01` and `book02` content with nonzero mode,
+  supplied-token, and demanded-token lanes
+
+So the coarse `0xcdcdcdcd` setup-header class still does not predict the sparse `Louisiana`
+recipe/runtime shape.
+
 ## Current implication
 
 The upstream side of the Tier 2 strip is now bounded more tightly:

docs/rehost-queue.md

@@ -604,7 +604,12 @@ Working rule:
     numeric Tier 2 input; on the current evidence it collapses to the ordinary nonzero campaign or
     setup branch before `0x00436d10 / 0x00443a50` run. That shifts even more weight back onto the
     sparse recipe/runtime family, with `+0x14` the only currently grounded preserved setup-side
-    scalar still crossing the bridge.
+    scalar still crossing the bridge. The same note now also adds a same-header-class recipe check:
+    `compare-recipe-book-lines Louisiana.gmp "Argentina Opens Up.gmp"` shows that even another
+    `0xcdcdcdcd / 0xcdcdcdcd` peer keeps a broader mixed `book01/book02` profile while
+    `Louisiana.gmp` stays sparse. So the coarse setup-header class is no longer a plausible
+    predictor of the Tier 2 runtime shape either; the recipe/runtime family remains the dominant
+    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: