Correlate infrastructure prelude patterns with mode families

docs/rehost-queue.md

@@ -104,10 +104,19 @@ Working rule:
   - mode `0x02` with decoded tunnel table stems plus zero-stem fallbacks
   - mode `0x01` with decoded bridge table stems plus zero-stem fallbacks
 
-  So the remaining infrastructure question is no longer “what does `0x00490960` build?” but “how
-  do those grounded mode families collapse into the save-side compact-prefix/name-pair classes,
-  especially the already-grounded bridge-only `0x0002/0xff` class and BallastCap `0x0055/0x00`
-  class?”.
+  The current grounded `q.gms` name corpus now also maps directly onto most of those families:
+  `BridgeSTWood_Section.3dp -> mode 0x01`, `TunnelSTBrick_* -> mode 0x02`,
+  `BallastCapST_Cap.3dp -> mode 0x0a`, and `TrackCapST_Cap.3dp -> mode 0x0b`, with only
+  `Overpass` still static-only in the current save corpus.
+
+  So the remaining infrastructure question is no longer “what does `0x00490960` build?” or even
+  “which family is this name row?” but “how do the surviving compact-prefix regimes subdivide
+  those already-mapped families, especially inside bridge mode `0x01` and track-cap mode `0x0b`?”.
+- The new probe correlation now makes that residual even more concrete: on grounded `q.gms`, the
+  dominant mixed `0x0001/0xff` class splits as `bridge:62 / track_cap:21 / tunnel:19`, while the
+  pure `0x0002/0xff` class is all bridge and the pure `0x0055/0x00` class is all ballast-cap.
+  So the next infrastructure slice should focus on subdividing the mixed one-child `0x0001/0xff`
+  class rather than revisiting the already-grounded pure classes.
 - The sibling `0x00490200` is tighter now too: it reads the seeded lanes
   `[this+0x206/+0x20a/+0x20e]` back through the live route collection at `0x006cfca8`, compares
   them against the current owner using `[this+0x216/+0x218/+0x201/+0x202]`, and behaves like a