What this is
Edge extensions get their own store listing path, since Edge's extension ecosystem — while Chromium-based and largely compatible with Chrome extension packages — has its own listing and distribution conventions worth tracking separately.
How it works
In practice, an Edge extension often shares most of its underlying code with the Chrome build given the shared Chromium base, but is tracked and surfaced as its own listing so users specifically on Edge can find and install it without confusion about compatibility.
Holding BOT for this path
The same BOT-holding developer access requirement applies here — there's no separate per-browser BOT requirement, just one developer-wide holding that covers publishing across every browser target you build for.
Related paths in Extensions