← Commit history

Publish 1.0.1

Kyle Bergstedt ·d2e565a9ee ·1mo ago ·parent 0074e38
3 files changed +27−12
SKILL.md+6−6
@@ -150,7 +150,7 @@ adom-desktop -t AdomLapper pull_file '{"filePaths":["<path>"],"saveTo":"/tmp"}' adom-desktop -t AdomLapper nbrowser_reload '{"sessionId":"app"}' ``` Rules that matter (full reference: the **driving-the-extension** skill):-- **One-time install — AD installs it for you** (Step 1.5); it's not there by default.+- **One-time install — Adom Bridge installs it for you** (Step 1.5); it's not there by default. - **Never reuse a window the user is working in — always open a FRESH one**, and `nbrowser_close_window`   it when done. Yanking their live page is hostile. - **Stay in the background — never foreground to grab a shot.** `nbrowser_screenshot` captures an@@ -175,21 +175,21 @@ ralph loop needs to diagnose a failed reload.  ## Step 1.5 — Installing the native browser extension (adom-desktop installs it for you) It isn't there by default, but **it largely self-installs — don't just hand the user manual steps.**-Your container never talks to the extension directly; it drives **adom-desktop (AD)** on the laptop and-AD does the setup. First-time flow (the extension page's `INSTALL-FLOW.md` walks every step):+Your container never talks to the extension directly; it drives **Adom Bridge (ab)** on the laptop and+Adom Bridge does the setup. First-time flow (the extension page's `INSTALL-FLOW.md` walks every step):  1. **Get the skills + mechanics:** `adom-wiki skills install adom/adom-browser-extension` — installs    `driving-the-extension`, `native-browser-safety`, `driving-the-desktop`, the site recipes, etc.-2. **AD installs the bridge** (one call) and registers the tiny **native-messaging host** on the laptop.+2. **Adom Bridge installs the bridge** (one call) and registers the tiny **native-messaging host** on the laptop. 3. **The extension gets loaded into Chrome/Edge.** Chrome 137+ removed `--load-extension`, so this is a-   one-time `chrome://extensions → Developer mode → Load unpacked`. **AD can drive that OS-level flow for+   one-time `chrome://extensions → Developer mode → Load unpacked`. **Adom Bridge can drive that OS-level flow for    the user** — the **driving-the-desktop** skill owns the extension's whole install / uninstall / reload    lifecycle with a proven, validated recipe. Production uses a Chrome Web Store force-install. 4. **Confirm:** `nbrowser_status` → connected, and the full `nbrowser_*` surface (navigate, screenshot,    reload, click, type, login_state, fetch_url…) is live.  So **install it FOR the user, not at them** — only ask them to approve a click when their machine isn't-Adom-managed and AD can't complete the OS step silently.+Adom-managed and Adom Bridge can't complete the OS step silently.  ## Step 2 — Analyze → fix → reload - **Analyze:** read the screenshot. Compare against intent — what's broken, wrong, missing, or ugly.
package.json+20−5
@@ -3,11 +3,23 @@   "slug": "ralph-loop-test",   "title": "Ralph Test",   "brief": "Screenshot, fix, reload. Loop until your app is right.",-  "version": "1.0.0",+  "version": "1.0.1",   "description": "The Adom 'ralph test': a screenshot-driven fix loop. Load the user's web or desktop app, screenshot it, let the AI analyze and fix what is wrong, reload, screenshot again, and loop until it is right. Covers every Adom screenshot surface (Hydrogen webview, pup, the native Chrome/Edge extension, desktop bridges) and the shotlog viewer workflow.",-  "tags": ["ai-agent", "screenshot", "debugging", "ralph", "loop", "browser-automation", "shotlog", "testing"],+  "tags": [+    "ai-agent",+    "screenshot",+    "debugging",+    "ralph",+    "loop",+    "browser-automation",+    "shotlog",+    "testing"+  ],   "dependencies": {},-  "scripts": {"install": "./install.sh", "uninstall": "./uninstall.sh"},+  "scripts": {+    "install": "./install.sh",+    "uninstall": "./uninstall.sh"+  },   "needs_sudo": false,   "discovery_triggers": [     "ralph",@@ -23,5 +35,8 @@     "fix loop"   ],   "discovery_pitch": "Run a ralph test: load your app, screenshot it, and let the AI loop on fix, reload, screenshot until it looks right.",-  "hero": {"type": "image", "path": "screenshots/hero.png"}-}+  "hero": {+    "type": "image",+    "path": "screenshots/hero.png"+  }+}\ No newline at end of file
page.json+1−1
@@ -3,7 +3,7 @@   "slug": "ralph-loop-test",   "title": "Ralph Test",   "brief": "Screenshot, fix, reload. Loop until your app is right.",-  "version": "1.0.0",+  "version": "1.0.1",   "description": "The Adom 'ralph test': a screenshot-driven fix loop. Load the user's web or desktop app, screenshot it, let the AI analyze and fix what is wrong, reload, screenshot again, and loop until it is right. Covers every Adom screenshot surface (Hydrogen webview, pup, the native Chrome/Edge extension, desktop bridges) and the shotlog viewer workflow.",   "tags": [     "ai-agent",