New "Median Crossover / Transfer" item (virtual X-junction) with boundary detection, temporary contraflow, and pre-configured safety overrides during Freeway closures

Note: You can read this proposal with full formatting and further details in the Waze Discuss forum post:
https://www.waze.com/discuss/t/new-median-crossover-transfer-item-virtual-x-junction-with-boundary-detection-temporary-contraflow-and-pre-configured-safety-overrides-during-freeway-closures/415393

CURRENT PROBLEM:
Divided highways and Freeways are mapped as separate one-way carriageways. During roadworks or incidents, contraflow bypasses using physical median crossovers (transfers) are often enabled on the ground. However, Waze lacks a native way to manage this:
1. Partner Feeds or manual closures on one carriageway force Waze to assume total blockage, causing massive multi-kilometer detours because the routing engine cannot use the opposite carriageway.
2. Manually changing freeway segments to two-way or opening micro-segments is error-prone, risks forgetting to revert changes, and requires map tile builds.

SUGGESTED SOLUTION:
1. Introduce a dedicated "Median Transfer" map item in WME acting as an inactive virtual X-junction by default.
2. When a closure is applied (manually or via Partner Feeds), Waze prompts: "Do you want to enable a contraflow bypass using boundary transfers?"
3. If "Yes", Waze automatically opens ONLY the entry and exit (boundary) transfers, ignores intermediate ones, temporarily converts the opposite carriageway between them to two-way (bidirectional) traffic for live routing, and applies L5+-preconfigured safety overrides (contraflow speed limits, mandatory headlight alerts, and hyperlocal yellow work-zone sign icons).
4. If "No", a standard closure is applied, ignoring transfers.
5. Once the closure expires, everything automatically reverts to normal without touching base map geometry.

Please check the forum post link above for the full technical breakdown and workflow details!