← Commit history
dev_reload 2-pass verified reliable (loads fresh version in ~7s); doc the bridge-restart-churn caveat; ext 0.0.6
2 files changed
+4−2
extension/manifest.json+1−1@@ -2,7 +2,7 @@ "manifest_version": 3, "name": "Adom for Chrome & Edge", "short_name": "Adom",- "version": "0.0.5",+ "version": "0.0.6", "description": "Drive your real, logged-in Chrome/Edge from the Adom ecosystem — the native-browser counterpart to pup.", "minimum_chrome_version": "116", "background": {
skills/driving-the-extension/SKILL.md+3−1@@ -234,7 +234,9 @@ only after you push it there and reload: 2. `nbrowser_dev_reload` — **self-completing 2-pass**: it does a soft reload, then arms a one-shot flag so the SW does a second *hard* reload on restart that re-reads disk. A single call now reliably picks up your changes (older builds needed two manual calls because the soft reload served cached files).- Throttled 1/90s.+ Throttled 1/90s. Verified: a fresh version loads in ~7s under clean conditions. **Gotcha:** if you+ ALSO restart the bridge in the same beat, the SW's reconnect churn can delay the 2nd pass — wait+ ~10s and don't read `nbrowser_status` until it settles (the version eventually lands; it's not stuck). 3. Verify: `nbrowser_status` → `version` should reflect your `manifest.json` bump (bump it so you can tell). - **Bridge** (`server.js`, `bridge.json`) runs from `…\bridges-cache\native-browser\` — the **single** runtime (`bridge_list` shows each bridge's `entrypoint`/`source`). `write_file` the changes there, then