@orkestrel/browser 0.0.7 → 0.0.9

package/README.md

@@ -5,8 +5,9 @@ browser automation library for the `@orkestrel` line. The environment-agnostic
 core (`src/core` — `CDPClient` speaking the CDP wire protocol over an injected
 `CDPTransportInterface`, plus `BrowserContext`, `BrowserPage`, and
 `BrowserFrame`, semantic locators, trusted input, network/HAR controls,
-diagnostics, structured DOM snapshots, and `BrowserCodegen`) never touches
-`node:*` or the DOM; the Node runtime (`src/server`)
+diagnostics, structured DOM snapshots, content distillation that selects a
+document's article rather than its whole body text, and `BrowserCodegen`)
+never touches `node:*` or the DOM; the Node runtime (`src/server`)
 adapts it with a `WebSocketCDPTransport`, browser process launch/discovery
 (`node:child_process` + `fetch`), a filesystem screenshot writer, and the
 `Browser` façade that ties launch → context → page together. Part of the
@@ -37,6 +38,7 @@ await page.click('#submit')
 const frame = await page.frame('checkout')
 await frame?.fill('[name=email]', 'ada@example.com')
 const snapshot = await page.snapshot({ styles: ['display'] })
+const article = await page.article() // reader-facing prose, boilerplate pruned
 await page.screenshot({ path: 'example.png' })
 await browser.destroy()
 ```
@@ -59,9 +61,6 @@ const result = await client.send('Page.navigate', { url: 'https://example.com' }
 For the full surface — the CDP dispatch core, the `BrowserContext` /
 `BrowserPage` / `BrowserCodegen` entities, the server transports, and usage
 patterns — see [`guides/src/browser.md`](guides/src/browser.md).
-The researched Playwright comparison, known semantic limits, and prioritized
-Chromium/CDP roadmap live in
-[`guides/src/playwright.md`](guides/src/playwright.md).
 
 ## Package