← Commit history
INSTALL-FLOW: add step-by-step screenshot sequence (navigate-not-committed -> picker wrong dir -> picker correct -> card loaded clean)
2 files changed
+29−10
docs/INSTALL-FLOW.md+26−9@@ -122,10 +122,33 @@ loaded: > the user pastes) rather than by stealing focus to type. Foreground is a narrated, last-resort > exception, never the default. -The native folder picker, navigated to the `extension/` folder (it opens in an arbitrary last-used-directory, so the path is always set + screenshot-verified before committing with **Select Folder**):+### What each step looks like (real screenshots) -+**a) After `desktop_navigate`, verify the page ACTUALLY loaded - not just the omnibox.** The posted-Enter+sometimes does not commit: below, the URL bar reads `chrome://extensions` but the page never changed (it+still shows the prior content), so there is no Load unpacked button yet. Screenshot-verify the real+Extensions page rendered (tab title becomes "Extensions"); re-issue `desktop_navigate` if it did not.+Note: `desktop_navigate` can also surface the window to the front to commit, so check it did not steal+focus.++++**b) Load unpacked opens the native picker in an ARBITRARY last-used directory** (here, Downloads) with+an empty Folder field. Never trust "it remembers the folder" - you must set the path:++++**c) After setting the path** (clipboard-assist preferred, or the address bar) the picker is in the+`extension/` folder (`icons`, `src`, Folder = "extension"). **Screenshot-verify this path before** you+click **Select Folder** - selecting the wrong folder loads a broken/old build silently:++++**d) After Select Folder, the card loaded clean** - Developer mode on, the Adom card Enabled, the pinned+ID, an active service worker, and **no red "Errors" button** (the only check that catches a card that+loaded *with* errors):++ Chrome and Edge are independent: load it in whichever the user wants, or both. The host is registered per browser (step 3), so each browser the extension runs in connects its own host.@@ -143,12 +166,6 @@ If `nbrowser_status` says not connected, the usual cause is that the profile has (an MV3 service worker sleeps when its profile has no windows). Opening a window wakes it. The bridge knows the extension is **connected**; it cannot see an installed-but-asleep extension until it dials in. -What "loaded clean" looks like on `chrome://extensions`: Developer mode on, the **Adom** card present-and Enabled, the pinned ID, an active service worker, and **no red "Errors" button** (the screenshot is-the only check that catches a card that loaded *with* errors):--- ### 6. Your first useful action Always work in a window **you** open (never the user's existing ones - see `native-browser-safety`): ```
package.json+3−1@@ -41,7 +41,9 @@ "docs/UNINSTALL-FLOW.md", "screenshots/extensions-adom-card.png", "screenshots/install-folder-picker.png",- "screenshots/uninstall-confirm-bubble.png"+ "screenshots/uninstall-confirm-bubble.png",+ "screenshots/install-navigate-not-committed.png",+ "screenshots/install-picker-wrong-dir.png" ], "scripts": { "install": "./install.sh",