Trace infrastructure mixed exact prefix classes

docs/control-loop-atlas/runtime-roots-camera-and-support-families.md

@@ -2986,12 +2986,19 @@ The low helper strip beneath that shared family is tighter now too: `0x0052ecd0`
   next infrastructure pass should stop treating all short rows as equally ambiguous and focus on
   the smaller outlier families inside that class, especially the `BallastCap`-style zero-like
   rows and any remaining non-`0x0001 / 0xff` prelude candidates.
-  Those outliers are explicit now too: the remaining `10` short-span rows on grounded `q.gms`
-  break into `9` `BallastCapST_Cap.3dp / Infrastructure` rows with compact prefix
-  `0xf3010100 / 0x0055 / 0x00` and candidate pattern `0x0055 / 0x00`, plus `1`
-  `TrackCapST_Cap.3dp / Infrastructure` row with compact prefix `0xff0000ff / 0x0001 / 0xff`.
-  So the next infrastructure pass should target the `BallastCap` outlier family first instead of
-  spending time on the already-dominant bridge-section class.
+  The exact compact-prefix classes are explicit now too:
+  `0xff0000ff / 0x0002 / 0xff` is a pure bridge class, `0xff000000 / {0x0001,0x0002} / 0xff`
+  are pure bridge classes, `0xf3010100 / 0x0055 / 0x00` is a pure `BallastCap` class, and
+  `0x0005d368 / 0x0001 / 0xff` is a pure one-row `TrackCap` class.
+  That sharpens the remaining infrastructure unknowns considerably: the only mixed exact
+  compact-prefix classes left on grounded `q.gms` are `0x000055f3 / 0x0001 / 0xff` and
+  `0xff0000ff / 0x0001 / 0xff`.
+  The current `0x000055f3 / 0x0001 / 0xff` class is tunnel-dominant and stays entirely on prior
+  profile span `0x03`, while the current `0xff0000ff / 0x0001 / 0xff` class is `TrackCap`-
+  dominant but still carries `4` tunnel rows spread across many spans.
+  So the next infrastructure pass should stop treating the remaining frontier as a generic
+  “mixed 0x06/outlier” problem and instead target the owning constructor/restore semantics for
+  those two exact mixed compact-prefix classes.
   The candidate-pattern classes are explicit now too: `0x0055 / 0x00` is a pure
   `BallastCapST_Cap.3dp / Infrastructure` class across `18` rows, always preceded by a zero-length
   prior profile span, while `0x0002 / 0xff` is a pure

docs/rehost-queue.md

@@ -180,12 +180,26 @@ Working rule:
   next infrastructure slice should stop treating the `0x06` class as uniformly ambiguous and focus
   on the smaller outlier families inside that class, especially the zero-like `BallastCap`-style
   rows and any remaining non-`0x0001 / 0xff` prelude candidates.
-- Those outliers are explicit now too: the remaining `10` short-span rows on grounded `q.gms`
-  break into `9` `BallastCapST_Cap.3dp / Infrastructure` rows with compact prefix
-  `0xf3010100 / 0x0055 / 0x00` and candidate pattern `0x0055 / 0x00`, plus `1`
-  `TrackCapST_Cap.3dp / Infrastructure` row with compact prefix `0xff0000ff / 0x0001 / 0xff`.
-  So the next infrastructure slice should target the `BallastCap` outlier family first, not the
-  already-dominant bridge-section class.
+- The exact compact-prefix classes are explicit across the whole prelude now too:
+  `0xff0000ff / 0x0002 / 0xff` is a pure bridge class, `0xff000000 / {0x0001,0x0002} / 0xff`
+  are pure bridge classes, `0xf3010100 / 0x0055 / 0x00` is a pure `BallastCap` class, and
+  `0x0005d368 / 0x0001 / 0xff` is a pure one-row `TrackCap` class.
+- That sharpens the remaining infrastructure unknowns considerably: the only mixed exact
+  compact-prefix classes left on grounded `q.gms` are `0x000055f3 / 0x0001 / 0xff` and
+  `0xff0000ff / 0x0001 / 0xff`.
+- The current `0x000055f3 / 0x0001 / 0xff` class is tunnel-dominant:
+  `TunnelSTBrick_Section.3dp / Infrastructure:13`, `TunnelSTBrick_Cap.3dp / Infrastructure:4`,
+  `TrackCapST_Cap.3dp / Infrastructure:0` in the exact-prefix correlation, with all `17` rows
+  staying on prior profile span `0x03`.
+- The current `0xff0000ff / 0x0001 / 0xff` class is `TrackCap`-dominant but still carries `4`
+  tunnel rows:
+  `TrackCapST_Cap.3dp / Infrastructure:18`,
+  `TunnelSTBrick_Cap.3dp / Infrastructure:2`,
+  `TunnelSTBrick_Section.3dp / Infrastructure:2`.
+  Its rows are spread across many spans rather than one dominant restore span.
+- So the next infrastructure slice should stop treating the remaining frontier as a generic
+  “mixed 0x06/outlier” problem and instead target the owning constructor/restore semantics for
+  those two exact mixed compact-prefix classes.
 - The candidate-pattern classes are now explicit across the whole stream too: `0x0055 / 0x00`
   is a pure `BallastCapST_Cap.3dp / Infrastructure` class across `18` rows, always preceded by a
   zero-length prior profile span, while `0x0002 / 0xff` is a pure