Gaps at tile boundaries on recast result

Hi there,

We’ve been using this fix for a while and haven’t encountered any issues so far. May I ask why the tile gap issue hasn’t been addressed upstream? It seems to have been raised multiple times (for example, Gap on tile border? - #5 by moyummy). Is the main reason that fixing it would introduce additional performance overhead, interfere with runtime/tiled incremental updates, or is it simply considered unnecessary since it doesn’t affect pathfinding correctness? I’m a bit concerned that our change might lead to tricky side effects down the line.

Any insights would be greatly appreciated—thank you for your time.