Tighten remaining atlas edge conclusions

docs/atlas/route-entry-and-trackers.md

@@ -127,8 +127,15 @@ What this note is for:
 
 Highest-value open edge:
 
-- The remaining semantic edge here is narrower now:
-  whether the pre-`1.03` versus `1.03+` tracker metric split has any meaningful downstream effect
-  beyond ranked linked-transit site choice and seeded peer-route choice, since current evidence
-  says the company train-pressure target still sums raw site cache `+0x12` rather than the
-  weighted lanes fed by step count and continuity.
+- The remaining semantic edge here is now mostly about ranking, not company pressure:
+  the pre-`1.03` versus `1.03+` tracker metric split still looks meaningful for the weighted
+  linked-transit site-score cache at `company_rebuild_linked_transit_autoroute_site_score_cache`
+  `0x00407bd0` and the seeded peer-route chooser at `company_build_linked_transit_autoroute_entry`
+  `0x00408380`, but current evidence says the company train-pressure target still sums raw site
+  cache `+0x12` rather than the weighted lanes fed by step count and continuity. The lower
+  route-entry pair metric still has other grounded consumers such as the initial route sweep and
+  the train route validator through `0x004a6630`, but no downstream consumer of the cached weighted
+  site lanes `+0x0e/+0x16` is currently grounded beyond the autoroute selector `0x00408280` and
+  builder `0x00408380`. So the remaining question here is no longer about current local ownership;
+  it is only whether some still-ungrounded consumer outside the current corpus also reads those
+  cached weighted lanes.