crawlio-browser 1.6.0 → 1.6.2

package/README.md

@@ -5,7 +5,7 @@
 
 ## [Documentation](https://docs.crawlio.app/browser-agent/overview) | [API Reference](https://docs.crawlio.app/browser-agent/tools) | [Chrome Extension](https://www.crawlio.app/browser-agent)
 
-MCP server that gives AI full control of a live Chrome browser via CDP. 100 tools (93 browser + 3 extraction + 3 recording + 1 compiler) with framework-aware intelligence, typed evidence infrastructure, and confidence-tracked findings — captures what static crawlers can't see.
+MCP server that gives AI full control of a live Chrome browser via CDP. 114 tools with framework-aware intelligence, typed evidence infrastructure, tracking pixel analysis, technographic fingerprinting, SEO auditing, and confidence-tracked findings — captures what static crawlers can't see.
 
 > **Note:** This repo supersedes [`crawlio-browser-mcp`](https://github.com/AshDevFr/crawlio-browser-mcp). All development now happens here.
 
@@ -29,7 +29,7 @@ That's it. Auto-detects and configures 14 MCP clients: Claude Code, Cursor, VS C
 
 ```bash
 npx crawlio-browser init              # Default: code mode, stdio transport
-npx crawlio-browser init --full       # Full mode (100 individual tools)
+npx crawlio-browser init --full       # Full mode (114 individual tools)
 npx crawlio-browser init --portal     # Portal mode (persistent HTTP server)
 npx crawlio-browser init --cloudflare # Add Cloudflare MCP (89 tools, no wrangler)
 npx crawlio-browser init --dry-run    # Show what would happen
@@ -160,7 +160,7 @@ The JIT Context MCP Runtime is a layered execution architecture where each layer
 │  │  ↳ Absorbs: connection drops, tab refreshes,              │  │
 │  │    port conflicts, extension lifecycle                     │  │
 │  ├────────────────────────────────────────────────────────────┤  │
-│  │  133 RAW COMMANDS  (bridge.send)                           │  │
+│  │  147 RAW COMMANDS  (bridge.send)                           │  │
 │  │  CDP-level browser control via Chrome extension            │  │
 │  └────────────────────────────────────────────────────────────┘  │
 └─────────────────────────────────────────────────────────────────┘
@@ -206,7 +206,7 @@ The JIT Context MCP Runtime is a layered execution architecture where each layer
 | **Framework awareness** | None | None | 17 namespaces, injected JIT |
 | **Action resilience** | Model must handle timing | N/A (no DOM) | Built-in actionability polling + settle delays |
 | **Error recovery** | Re-call individual tool | Re-create isolate | Re-execute against same live state (Agentic REPL) |
-| **Multi-step patterns** | Model improvises | Model writes loops | 8 tested higher-order methods + behavioral protocol |
+| **Multi-step patterns** | Model improvises | Model writes loops | 17 tested higher-order methods + behavioral protocol |
 
 [Read the full architecture guide →](https://docs.crawlio.app/browser-agent/overview)
 
@@ -214,7 +214,7 @@ The JIT Context MCP Runtime is a layered execution architecture where each layer
 
 ### Code Mode (3 tools) — default
 
-Collapses 100 tools into 3 high-level tools with ~95% schema token reduction:
+Collapses 114 tools into 3 high-level tools with ~95% schema token reduction:
 
 | Tool | Description |
 |------|-------------|
@@ -230,7 +230,7 @@ const screenshot = await bridge.send({ type: 'take_screenshot' }, 10000);
 return screenshot;
 ```
 
-### Full Mode (100 tools)
+### Full Mode (114 tools)
 
 Every tool exposed directly to the LLM. Enable with `--full`:
 
@@ -425,15 +425,15 @@ When a framework is detected, the smart object exposes framework-specific helper
 
 ## Method Mode
 
-Method Mode is a domain layer built on top of Code Mode. It adds higher-order methods, a typed evidence system, and a behavioral protocol to the `execute` sandbox — without changing the tool surface. The model still sees three tools. The same `smart` object. The same 133-command catalog underneath. What changes is what happens *inside* `execute`.
+Method Mode is a domain layer built on top of Code Mode. It adds higher-order methods, a typed evidence system, and a behavioral protocol to the `execute` sandbox — without changing the tool surface. The model still sees three tools. The same `smart` object. The same 147-command catalog underneath. What changes is what happens *inside* `execute`.
 
 ### The Maturity Ladder
 
 | Layer | Optimizes For | Behavioral Variance | Evidence Quality |
 |-------|---------------|---------------------|-----------------|
-| **Raw MCP** (100 tools) | Completeness | High — flat tool list, no composition guidance | None — unstructured text |
+| **Raw MCP** (114 tools) | Completeness | High — flat tool list, no composition guidance | None — unstructured text |
 | **Code Mode** (3 tools) | Token efficiency | Medium — right primitives, ad-hoc composition | None — model-defined shapes |
-| **Method Mode v1** (+ 8 methods + protocol) | Consistency | Low — proper methods, protocol constraints | Convention — `{ finding, evidence, url }` |
+| **Method Mode v1** (+ 17 methods + protocol) | Consistency | Low — proper methods, protocol constraints | Convention — `{ finding, evidence, url }` |
 | **Method Mode v2** (+ typed evidence + gaps + confidence) | Correctness | Minimal — typed schemas, tool-enforced findings | Structural — typed records, gap tracking, confidence propagation |
 
 ### Architecture
@@ -462,7 +462,7 @@ Method Mode is a domain layer built on top of Code Mode. It adds higher-order me
 │  │  Framework Namespaces  [up to 17, injected JIT]      │  │
 │  │  react · vue · angular · nextjs · shopify · ...      │  │
 │  ├──────────────────────────────────────────────────────┤  │
-│  │  bridge.send()  — 133 raw commands                   │  │
+│  │  bridge.send()  — 147 raw commands                   │  │
 │  └──────────────────────────────────────────────────────┘  │
 └────────────────────────────────────────────────────────────┘
 ```
@@ -631,7 +631,7 @@ Multi-framework detection returns a **primary** framework (meta-framework takes
 ## Tools Reference
 
 <details>
-<summary><b>All 100 tools</b> — Connection, Capture, Navigation, Network, Storage, Emulation, and more</summary>
+<summary><b>All 114 tools</b> — Connection, Capture, Navigation, Network, Storage, Emulation, Tracking, SEO, and more</summary>
 
 ### Connection & Status
 

package/dist/mcp-server/{chunk-CSSOZILQ.js → chunk-T4GKS2PG.js}

@@ -1,7 +1,7 @@
 // src/shared/constants.ts
 import { homedir } from "os";
 import { join } from "path";
-var PKG_VERSION = "1.6.0";
+var PKG_VERSION = "1.6.2";
 var WS_PORT = 9333;
 var WS_PORT_MAX = 9342;
 var WS_HOST = "127.0.0.1";