NB - Native Browser Bridge

@@ -49,11 +49,11 @@ Deps: none (core `http`/`net`), so the payload is source-only (no `node_modules` 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>"`-   - `adom-wiki release upload adom/adom-browser-extension <ver> native-browser-bridge-v<ver>.bin --platform any`-   The download then serves anon at `https://wiki.adom.inc/download/adom/adom-browser-extension/<ver>/native-browser-bridge-v<ver>.bin` (verify: `curl -sI` → 200). (The pkg's own release stays 0.3.x; the bridge release is 0.0.x — separate version streams on the same page, that's expected.)+   - `adom-wiki release upload adom/adom-browser-extension <ver> native-browser-bridge-v<ver>.zip --platform any`+   The download then serves anon at `https://wiki.adom.inc/download/adom/adom-browser-extension/<ver>/native-browser-bridge-v<ver>.zip` (verify: `curl -sI` → 200). (The pkg's own release stays 0.3.x; the bridge release is 0.0.x — separate version streams on the same page, that's expected.) 4. **sha256 + byte size** → write `native-browser-bridge-manifest.json` with the `url` pointing at that    **`/download/` path** (NOT a `/files` blob):-   `{manifest_version:1, version, url:"https://wiki.adom.inc/download/adom/adom-browser-extension/<ver>/native-browser-bridge-v<ver>.bin", sha256, size, released_at}`.+   `{manifest_version:1, version, url:"https://wiki.adom.inc/download/adom/adom-browser-extension/<ver>/native-browser-bridge-v<ver>.zip", sha256, size, released_at}`. 5. **Push manifest + source as TEXT** with `adom-wiki repo push adom-browser-extension --files native-browser-bridge-manifest.json bridge/bridge.json bridge/package.json bridge/server.js bridge/BRIDGE_VERSION ...` (the manifest lives on `/files`; only the binary is off it). 6. **Land it:** `refresh_bridges {name:"native-browser"}` → verify `nbrowser_readiness` routes and    `bridge_check_updates`/`bridge_list` show `liveVersion==<ver>` (no `staleProcess`). *(bridge_check_updates