Trace GPS provider filters

docs/red4ext-logging-shim.md

@@ -64,6 +64,18 @@ Current behavior:
 - Resolves the native mappin system when one of those paths fires, logs relevant
   vtable slot addresses, and temporarily hooks the route-adjacent slots.
 
+Active build note:
+
+- The currently installed build is read-only. It disables provider class
+  multiplier overrides and enables local GPS search tracing.
+- It hooks `GPSSearch` (`0x44f054`), `GPSRouteProducer` (`0x44cc7c`),
+  `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.
+
 Current route-probe focus:
 
 - `FrameMappinPath` wrapper/core: `0x27c4314`, `0x27bc1ec`

docs/tooling.md

@@ -8,6 +8,9 @@ Installed inside that toolbox:
 - GCC/G++, CMake, make
 - `jq`, `ripgrep`
 - WolvenKit CLI NuGet tool `wolvenkit.cli` 8.18.1
+- `rizin` 0.7.4
+- `python3-capstone` 5.0.5
+- `python3-pefile` 2024.8.26
 
 The WolvenKit command is: