Dump GPS result object fields

docs/red4ext-logging-shim.md

@@ -144,18 +144,29 @@ Latest GPS-query finding:
 - During a controlled route test, the normal world-map GPS path did not call
   the script-native `RunGPSQuery`/`UpdateGPSQuery` bodies.
 - Each deliberate quest/custom route click called the shared submitter
-  `0x70a42c` from return RVA `0x8d20d4`, then returned query IDs `3`, `4`, `5`,
-  and `6` for the three quest routes plus the custom pin.
+  `0x70a42c` from return RVA `0x8d20d4`. In the 2026-06-20 19:03 run, the
+  deliberately plotted routes returned query IDs `17`, `18`, `19`, and `20`
+  for the side job, Sinnerman, Claire's Garage, and a custom pin.
 - Each submitted route produced three `0x70a570` dispatches: current/player
   position, a nearby snapped/lane position, then the destination position.
-- The dense log stream immediately after Space-to-Continue was repeated
-  `0x7094b8` result polling for startup query IDs `0`/`1`, matching the HUD /
-  minimap route initialization delay. The next probe tracks submitted IDs so
-  route-click completion can be captured without being drowned by startup
-  polling.
+- The dense log stream immediately after Space-to-Continue is repeated
+  `0x7094b8` result polling for startup/minimap route queries, matching the HUD
+  route initialization delay.
+- `GPSQueryResultFetch 0x7094b8` returning `1` is the route-solve completion
+  signal. The caller at return RVA `0x52069c` starts handling a completed
+  result, then the caller at return RVA `0x520783` drains result records.
+  The visible route record currently appears as a packed point/count pair in
+  the object passed as `outPath`: the deliberate routes produced `11`, `16`,
+  `15`, and `14` point-like counts.
 - Static disassembly confirms `0xaa5704` takes `(manager, queryId)` and returns
-  a small status code; one caller checks for value `1` as the completed-query
-  state.
+  a small status code; one caller checks for value `1`. Runtime logging shows
+  this is HUD/display lifecycle polling rather than solve completion: it polls
+  the currently displayed query once per second and pauses when the minimap is
+  not rendered.
+- The current installed probe adds a read-only dump of suspected result-object
+  fields around offsets `0x20` through `0x5f` on successful active-route
+  fetches. This is intended to identify whether the returned route is a raw
+  solver path, a smoothed draw path, or both.
 
 Build and install from the Fedora toolbox: