NB - Native Browser Bridge

@@ -1,6 +1,6 @@ --- name: cross-platform-dev-description: How adom-browser-extension ships across Windows and macOS — Windows-first, Kyle ports to Mac. Read before adding platform-specific code.+description: How adom-browser-extension ships across Windows and macOS - Windows-first, Kyle ports to Mac. Read before adding platform-specific code. ---  # Cross-platform dev flow (Windows-first → Kyle ports to Mac)@@ -18,7 +18,7 @@ a thin layer, never a rewrite. ## The rule  Keep the **bridge** (`bridge/server.js`), the **native host** (`host/native-host.js`), and the-**extension** (`extension/`) **OS-agnostic** — plain Node + standard MV3 APIs. Isolate everything+**extension** (`extension/`) **OS-agnostic** - plain Node + standard MV3 APIs. Isolate everything Windows-specific to the **install/registration layer** only:  | Concern | Windows (build first) | macOS (Kyle ports) |@@ -27,12 +27,12 @@ Windows-specific to the **install/registration layer** only: | Host launcher | `native-host.bat` → `node native-host.js` | `native-host.sh` → `node native-host.js` (chmod +x) | | Bridge cache path | `%LOCALAPPDATA%\Adom Desktop\bridges-cache\native-browser\` | `~/Library/Application Support/Adom Desktop/bridges-cache/native-browser/` | | Extension force-install | `HKLM\...\ExtensionInstallForcelist` | configuration profile / MDM `ExtensionInstallForcelist` |-| Discovery file | `os.homedir()/.adom/bridges/native-browser/host.json` | identical (uses `os.homedir()` — already cross-platform) |+| Discovery file | `os.homedir()/.adom/bridges/native-browser/host.json` | identical (uses `os.homedir()` - already cross-platform) |  ## Implications  - Never put `process.platform === 'win32'` branches in `bridge/` or `host/` core logic. If you need a-  platform path, derive it from `os.homedir()` (already cross-platform) — don't hardcode `%...%`.+  platform path, derive it from `os.homedir()` (already cross-platform) - don't hardcode `%...%`. - The `--silent-debugger-extension-api` launch-flag wiring and registry writes are Windows-only by   nature; keep them in `install/` so Kyle swaps that folder, not the engine. - When you add a Windows install step, add a one-line "macOS equivalent" note next to it so the port