Passing edges when the type is custom

[ronnorthrip]

Passing edges when the type is custom

[zachiler]

Thanks for this, @ronnorthrip — this is a nice catch. You correctly identified that forcing per-edge routing through a closure meant it couldn't survive toObject()/fromObject(), and passing the edge to the generator is exactly the right fix. Clean, non-breaking, well-documented. 🙏

I've merged it with a few maintainer touch-ups on top of your commit:

1. Dropped the dist/ bundle rebuild. Just a repo convention thing for next time — the committed dist/ bundle is a release artifact we regenerate at merge/resync, so feature branches should leave it untouched (it's easy to miss since it's normally gitignored). I reverted those two files to dev so the PR reads as its actual ~15-line source change.
2. Tightened the edgeTypes param types. The public FlowCanvasConfig.edgeTypes typed sourcePosition/targetPosition as string; I narrowed them to the 'top' | 'right' | 'bottom' | 'left' cardinal union to match getEdgePath's internal signature, so consumers get proper narrowing.
3. Added a serialization round-trip test. Since the headline benefit is "a custom-routed edge survives a reload," I added a test that stashes route data on edge.data, round-trips it through the same JSON serialization toObject()/fromObject() use, and asserts the generator still produces the routed path — locking in the exact behavior your change enables.

Full suite green (2919 tests) and typecheck clean. Appreciate the report and the fix!