NB - Native Browser Bridge

@@ -41,9 +41,11 @@ Deps: none (core `http`/`net`), so the payload is source-only (no `node_modules`    `server.js` reads `VERSION` from `bridge.json` (authoritative) so it can't drift — keep it that way.    AD reads that same `version` off your `/status` JSON as `liveVersion`, so keep `/status` accurate. 2. **Build the zip with files at the ROOT** (there is no `zip` binary — use Python `zipfile`):-   members = `bridge.json`, `package.json`, `server.js`, `BRIDGE_VERSION`. Name it-   `native-browser-bridge-v<ver>.bin` (the `.bin`/`.zip` extension is irrelevant for a **Release** asset —-   AD's manifest `url` is extension-agnostic; only the OLD `/files` base64 API rejected `.zip`).+   members = `bridge.json`, `package.json`, `server.js`, `BRIDGE_VERSION`, `adom-favicon.png`. Name it+   `native-browser-bridge-v<ver>.zip` (as of 0.1.29 — it always WAS a zip; the old `.bin` naming was a+   scar from the retired `/files` base64 API which rejected `.zip`. Release assets are extension-agnostic+   and AD only follows the manifest `url`, so no AD-side change was needed for the rename; old `.bin`+   releases stay valid at their existing URLs). 3. **The runtime is a RELEASE ASSET, not a `/files` blob** (SDK "two-artifact" rule — fusion + pup do    exactly this). Cut a Release for the bridge version + upload the zip:    - `adom-wiki release create adom/adom-browser-extension <ver> --title "native-browser bridge runtime v<ver>"`