Narrow tier2 kind-8 availability path

docs/rehost-queue.md

@@ -481,6 +481,20 @@ Working rule:
     port/warehouse recipe rebuild `0x00435630`,
     and only then the later world bringup / event-service neighborhood
     `0x004384d0 / 0x00443a50 / 0x00432f40`.
+  - the strongest same-stem title pair has a Tier 2 availability note now too:
+    `artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-named-availability-note.md`
+    shows `Louisiana.gmp` and `Dutchlantis.gmp` share the direct named-availability bit for
+    `Warehouse05` (`1/1`), as well as `Port01`, `Furniture Factory`, `FarmGrain`, and
+    `Logging Camp`; their current `18` named-availability differences fall elsewhere
+    (`Bauxite Mine`, `AluminumMill`, `Farm Corn`, `FarmCotton`, `FarmRice`, `FarmSugar`, etc.).
+    The same note now folds in two deeper grounded constraints too:
+    `0x00412d70` does not consult the scenario-side recipe-book name at `[state+0x0fe8]`, and
+    `0x00434f20` writes only a boolean availability override bit. So the current Tier 2 question
+    is no longer “is `Warehouse05` simply toggled differently?” or “is a recipe-book display name
+    leaking through?” but
+    “which broader candidate-state rebuild or latch sequencing difference above
+    `0x00437737 / 0x00412c10 / 0x00412bd0 / 0x00412d70 / 0x00412fb0` leads to the shipped
+    `Add Building Warehouse05` row 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: