fix(app): allow static segments as siblings of dynamic route segments

[benedikt-bartscher]

_find_route_conflict flagged a conflict whenever an existing route's dynamic segment lined up with a different static segment of a new bracket-containing route (e.g. /posts/[id] vs /posts/all/[x]), and only in that registration order. React Router resolves such siblings fine (static wins), so only two dynamic segments with different names at the same position are a real conflict.

[greptile-apps]

Greptile Summary

The PR makes route-conflict detection symmetric and permits static route segments alongside dynamic segments while continuing to reject differently named dynamic segments in the same position.

• Normalizes both routes before comparing segment types.
• Stops conflict checking once a differing static segment separates the route trees.
• Adds registration-order coverage for static and dynamic sibling routes.

Confidence Score: 5/5

The PR appears safe to merge, with the updated conflict detection matching the router’s static-over-dynamic specificity behavior.

The changed logic retains rejection of competing dynamic segment names while allowing route shapes that the router resolves deterministically, and the tests cover both registration orders.

Important Files Changed

Filename	Overview
reflex/app.py	Updates route-conflict comparison so only differently named dynamic segments at the same position conflict; the behavior aligns with route specificity rules.
tests/units/test_route.py	Adds bidirectional coverage showing that static siblings of dynamic route segments are valid.

_{Reviews (1): Last reviewed commit: "fix(app): allow static segments as sibli..." | Re-trigger Greptile}

[codspeed-hq]

Merging this PR will not alter performance

✅ 27 untouched benchmarks
⏩ 8 skipped benchmarks¹

---

_{Comparing benedikt-bartscher:fix-static-dynamic-route-conflict (46aba35) with main (9f7f82c)}

Footnotes

1. 8 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[cubic-dev-ai]

No issues found across 2 files

_{Re-trigger cubic}