Configure Edge and Brave too, not just Chrome

They are Chromium: same CRX, same update manifest, same policy — only the
registry vendor key differs. The script now defaults to every one of the three
it finds installed, which is what the Linux counterpart already did.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

deploy/README.md

@@ -93,12 +93,16 @@ powershell -NoProfile -ExecutionPolicy Bypass -File scripts\install-extension-po
 sudo scripts/install-extension-policy.sh
 ```
 
+Both configure every Chromium-family browser they find — Chrome, Edge and Brave
+take the same CRX, the same update manifest and the same policy, differing only
+in where that policy is written. Narrow it with `-Browser Edge` if you would
+rather not.
+
 The Windows script writes to the current user's policy hive and needs no
 elevation; `-Scope Machine` covers every account on the box and does need an
 elevated shell. Linux has no per-user equivalent — Chrome only reads managed
 policy from `/etc` — so that one is root-only and machine-wide. Both take
-`-Remove` / `--remove`, and the Windows one takes `-Browser Edge` or
-`-Browser Brave`.
+`-Remove` / `--remove`.
 
 Afterwards, remove the unpacked copy from `chrome://extensions` — it now has the
 same id, and Chrome will not load both — and restart the browser.