Shift tier2 kind-8 frontier past importer branch

docs/rehost-queue.md

@@ -643,6 +643,23 @@ Working rule:
     test whether the shipped `5200 :: [7:0]` `Add Building Warehouse05` strip is tied to that
     minimal imported-cluster shape specifically, rather than to the mere presence of one reused
     `0x00080000 / 0x00004080` triplet inside a broader recipe profile.
+  - the same split is tighter even inside the broader “single imported row” family:
+    eight bundled maps currently materialize only one nonzero recipe row, but `Louisiana.gmp` is
+    the only one whose supporting token surface is just two additional demand rows instead of three
+    or four extra token-bearing rows. So the next checked discriminator is now narrower than
+    “single imported row” too:
+    test whether the `5200 :: [7:0]` add-building strip tracks that exact two-demand-plus-one-
+    imported minimal cluster, not just the existence of one imported row or one reused
+    `0x00080000 / 0x00004080` triplet.
+  - the importer-side boundary is tighter now too:
+    direct `inspect-smp` checks show `Louisiana.gmp`, `Britain.gmp`, and `South East USA.gmp` all
+    collapse to the same first importer shape of exactly one
+    `imports_to_runtime_descriptor = true` line on `nonzero-supply-branch`, while the broader
+    reuse case `Ireland.gmp` imports four such rows. So the next queue head is no longer
+    “prove the first importer branch differs”; it is:
+    recover the later runtime-record / named-availability consequence under
+    `0x00412d70 / 0x00412fb0 / 0x00412c10` that makes the minimal cluster land on
+    `5200 :: [7:0]` only in `Louisiana.gmp`.
     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: