browser4-cli 4.13.19 → 4.13.21

package/README.md

@@ -249,7 +249,7 @@ These flags can appear before any command.
 | Tool | Best for | Input model | Output model |
 |---|---|---|---|
 | `snapshot` | clicking, typing, finding interactive elements | live accessibility tree | refs like `e15` |
-| `htmlsnapshot` | DOM inspection, CSS extraction, X-SQL | stored HTML snapshot | CSS selectors and query results |
+| `htmlsnapshot` | DOM inspection, CSS extraction, X-SQL | live page DOM (capture is optional) | CSS selectors and query results |
 
 #### LLM configuration
 
@@ -326,7 +326,7 @@ All interaction commands accept a snapshot ref such as `e15` or a CSS selector u
 | `wait [target]` | Wait for a selector/ref, duration, text, URL pattern, page-load state, or JavaScript expression. Supports `--timeout`, `--text`, `--url`, `--load`, `--fn`. |
 | `upload <ref> <file> [file...]` | Upload one or more local files to a page file input. The target must be an `<input type="file">` (anything else errors); the paths must be readable by the browser process — local mode: the same machine, and empty/missing files are rejected with a hint; remote backend: paths resolve on the backend host. Supports `--no-snapshot`. |
 
-`wait --load` accepts `domcontentloaded`, `load`, and `networkidle`.
+`wait --load` accepts `domcontentloaded`, `load`, and `networkidle`. `networkidle` only proves the network went quiet — it does **not** mean late-rendered results exist; for result pages poll the element instead: `wait "<result-selector>"`.
 
 ```bash
 browser4-cli click e8 --follow
@@ -393,8 +393,8 @@ browser4-cli cdp Runtime.evaluate --json '{"expression":"document.title"}'
 |---|---|
 | `htmlsnapshot` | Short form of `htmlsnapshot capture`. |
 | `htmlsnapshot capture` | Capture and store a static HTML snapshot with metadata about the page and interactive elements. |
-| `htmlsnapshot get <field> [selector] [name]` | Extract the first matching `text`, `html`, or `attr` from the stored snapshot. |
-| `htmlsnapshot get all <field> [selector] [name]` | Extract all matching values from the stored snapshot. Supports `--offset` and `--limit`. |
+| `htmlsnapshot get <field> [selector] [name]` | Extract the first matching `text`, `textcontent`, `html`, or `attr` from the live page DOM. |
+| `htmlsnapshot get all <field> [selector] [name]` | Extract all matching values from the live page DOM. Supports `--offset` and `--limit`. |
 | `htmlsnapshot query [url]` | Run X-SQL. Supports `--sql <query\|@file>`, `--sql-stdin`, `--sql-base64`, result pagination, and extraction-focused output flags. |
 | `htmlsnapshot export` | Export stored HTML to a file. Supports positional file path or `--file <path>` plus `--clean`. |
 | `htmlsnapshot summary` | Generate a compressed Web Page Summary Index (WPSI). |
@@ -655,6 +655,13 @@ The runtime bundle is stored separately in a platform-conventional application-d
    that auto-build from source. Use `./b4w.ps1 <command>` (PowerShell),
    `./b4w.sh <command>` (Git Bash / Linux / macOS), or `./b4w.bat <command>`
    (CMD) — all accept the same arguments as the installed `browser4-cli` binary.
+   Dev mode only ever serves the checked-out code: a local runtime bundle built
+   from a **different project version** makes the command refuse to start (naming
+   the reason, the bundle's versions and build time, and the rebuild command)
+   rather than silently testing an outdated backend; a checkout whose sources
+   merely look newer than the bundle jars is rebuilt before the server starts —
+   see
+   [CLI install & upgrade](docs/cli-install-upgrade.md#dev-mode-the-backend-must-match-the-checkout).
 
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "browser4-cli",
-  "version": "4.13.19",
+  "version": "4.13.21",
   "description": "Browser automation CLI for AI agents",
   "type": "module",
   "files": [