"/home/yossef/notes/git/projects/maplibra/risks/Debug Routing.md"

path: maplibra/risks/Debug Routing.md

- **fileName**: Debug Routing
- **Created on**: 2026-06-16 00:48:42

Debug Routing

Migrated from: obs_vault

Parent: ./Risk Map.md

This note is the shortest path for diagnosing a route bug.

First Facts To Capture

• startup mode from ../flows/Startup Sequence.md
• active graph format from ../modules/Pathfinding.md
• requested engine vs active engine from ../modules/WASM Routing.md
• route endpoint candidates from ../modules/Snapping.md
• whether smoothing changed the raw path from ../modules/Route Smoothing.md

If Routing Is Missing

1. Check whether the package contains routing/ assets.
2. Check whether active graph format is slices, binary, or json.
3. If no graph exists, inspect ../decisions/Deferred Bootstrap.md and ./Offline Packaging Risks.md.

If The Door Is Wrong

1. Inspect the containing room in ../modules/Doors and Rooms.md.
2. Inspect door features in ../modules/Doors and Rooms.md.
3. Inspect candidate ranking in ../modules/Snapping.md.
4. Compare with ./Wrong Door Risk.md.

If The Path Crosses A Wall

1. Check graph edges from ../flows/Graph Construction.md.
2. Check blockers and walkable areas in ../flows/Wall Detection.md.
3. Check smoothing in ../modules/Route Smoothing.md.
4. Compare with ./Cross Wall Risk.md.

If WASM Falls Back

1. Check worker construction.
2. Check WASM init errors or timeouts.
3. Check fallbackReason.
4. Compare requested engine and active engine.

See Also

• ./Risk Map.md

• ./Test Gaps.md

• ./Source Map.md

  continue:[[]]
  before:[[]]