Probe GPS packed handle resolver

This commit is contained in:
2026-06-20 21:45:09 -05:00
parent bf72dcf6e3
commit 407c44b1ad
3 changed files with 134 additions and 9 deletions
+7 -2
View File
@@ -74,12 +74,17 @@ Active build note:
`0x70a42c` submissions, `0x7094b8` result records, and local
search/provider-cost stats.
- It hooks `GPSSearch` (`0x44f054`), `GPSRouteProducer` (`0x44cc7c`),
`GPSEdgeCost` (`0x44f838`), and the two cost-provider filters
`0x44ff68`/`0x450b08`.
`GPSResolveHandle` (`0x44e1a8`), `GPSEdgeCost` (`0x44f838`), and the two
cost-provider filters `0x44ff68`/`0x450b08`.
- The filter probe records pass/fail counts by point class and by the
`point + 0x10` mask bits tested against provider masks at `+0x108`/`+0x10a`.
This is meant to identify whether class/mask filtering, rather than the edge
multiplier table, is dominating route choice.
- The resolver probe logs selected packed-handle resolutions from the
search/materialization corridor. It decodes point index, segment index, and
generation bits, then dumps the resolved 0x68-byte segment record and
0x14-byte point record. The purpose is to see whether the edge-cost stage can
reach final lane hashes/resource-side road classes before a path is chosen.
Current route-probe focus: