Ground widened add-building descriptor names

docs/rehost-queue.md

@@ -289,18 +289,21 @@ Working rule:
     cover the full `614`-row export instead of the old truncated `520`-row slice
   - that closes the earlier unlabeled cluster:
     grouped descriptor ids `521`, `526`, `528`, `548`, and `563` are now recovered as
-    `Add Building Slot 19`, `Add Building Slot 24`, `Add Building Slot 26`, `Add Building Slot 46`,
-    and `Add Building Slot 61` respectively, all in the widened shell-owned add-building strip
-    `503..613`
+    `Add Building FarmGrain`, `Add Building Furniture Factory`, `Add Building Logging Camp`,
+    `Add Building Port01`, and `Add Building Warehouse05` respectively. The checked-in
+    `event-effects-building-bindings.json` artifact grounds those names from the stable RT3 1.05
+    candidate-table order plus the direct `descriptor_id - 503` candidate-id bridge in
+    `0x00430270`
   - the earlier `label_id - 2000` bridge for `548` and `563` is now known to be a false lead:
     those numeric collisions hit the special-condition label table
     (`Disable Building Stations`, `Completely Disable Money-Related Things`), but the extended
     EventEffects table proves the actual grouped descriptors are add-building slots, not
     special-condition verbs
   - the compact opcode-`8` frontier therefore shifts:
-    the next static-analysis pass should target which add-building slot numbers correspond to which
-    concrete building classes and whether opcode `8` on that shell-owned strip means a distinct
-    add-building shell flow, not more missing-label recovery
+    the next static-analysis pass should widen the concrete add-building candidate-name bridge
+    beyond the already grounded `521/526/528/548/563` rows and then determine whether opcode `8`
+    on that shell-owned strip means a distinct add-building shell flow, not more missing-label
+    recovery
   - the concrete owner strip above that bundle is grounded now too:
     `0x00433060` is the direct non-direct serializer loop that writes `0x4e99/0x4e9a/0x4e9b`,
     calls `0x00430d70` per live collection row, and sits beside the sibling `0x00433130` size/load