docs: simplify

Author: posva

docs/content/1.guide/12.in-page-channel.md

@@ -64,7 +64,7 @@ Channel names are namespaced with the devframe id, like RPC ids. Function names
 
 ## The page script endpoint
 
-The required `functions` option and optional `events` option declare every incoming name on the endpoint's protocol side; use `{}` for an empty direction. Functions require a `handler`. Events accept an optional `handler`, and `{}` registers an event for runtime subscriptions through `on()`. Handlers are contextually typed from the shared protocol and support Standard-Schema argument validation and `jsonSerializable` metadata. `defineChannelFunction` retains the named definition shape for lower-level authoring.
+The required `functions` option and optional `events` option declare every incoming name on the endpoint's protocol side; use `{}` for an empty direction. Functions require a `handler`. Events accept an optional `handler`, and `{}` registers an event for runtime subscriptions through `on()`. Handlers are contextually typed from the shared protocol and support Standard-Schema argument validation and `jsonSerializable` metadata. A function with `agent` metadata must set `jsonSerializable: true` and is available to coding agents through MCP. `defineChannelFunction` retains the named definition shape for lower-level authoring.
 
 `call()` accepts names from `functions`, including actions returning `void` or `Promise<void>`: callers can await completion and catch errors or timeouts. `emit()`, its deprecated alias `callEvent()`, and `on()` use the names declared in `events`. Function and event names have separate namespaces.
 
@@ -100,12 +100,6 @@ pageChannel.events.on('panel:disconnected', () => pauseWorkIfNobodyWatches())
 
 `emit` on the page-script endpoint fans out to every connected panel endpoint. Functions declared under `functions.panel` are called through a specific `pageChannel.panels[0].call()` peer handle.
 
-### Agent tools over MCP
-
-A function carrying `agent` metadata is registered with the page's DevFrame client and becomes available through the node MCP endpoint used by `devframe connect`. The channel name qualifies the otherwise-bare function name. Only functions are exposed; events remain channel-only. Agent functions require `jsonSerializable: true`, and their Standard-Schema `args` produce the advertised `arg0` / `arg1` / … input schema.
-
-The registration follows the endpoint and browser connection lifecycle. Closing the channel or browser tab removes its tools. No panel needs to be open: loading the page establishes the bridge.
-
 ## The panel endpoint
 
 ```ts

docs/content/1.guide/15.agent-native.md

@@ -157,8 +157,6 @@ rpc.client.register({
 
 `connectDevframe()` wires this on its own when the browser provides a model context; `webmcp: false` keeps the browser side off the WebMCP surface. `registerWebMcpTools(collector)` (from `devframe/client`) applies the same projection to a hand-built collector and returns a dispose that unregisters every tool.
 
-[In-page channel functions](/guide/in-page-channel#agent-tools-over-mcp) use the page's DevFrame connection instead: adding `agent` makes the original handler available through the regular node MCP endpoint without exposing it through WebMCP.
-
 > [!WARNING]
 > WebMCP is an experimental proposal; `registerWebMcpTools` tracks the current draft (`AbortSignal`-based unregistration) and earlier handle-returning drafts, but the browser API may still change.
 

docs/content/1.guide/17.client-context.md

@@ -67,9 +67,9 @@ A client-only dock can also carry `type: 'json-render'` with an inline [JSON-ren
 
 ## Dock client scripts
 
-A client script is a `ClientScriptEntry`: `{ importFrom, importName?, eager? }` (`importName` defaults `'default'`). The field varies by entry kind: an `action` entry's `action` runs when the dock button is activated, a `custom-render` entry's `renderer` renders its panel, and an `iframe` entry's optional `clientScript` runs alongside the iframe panel inside the host page ([Hub API reference](/references/hub-api#dock-client-script-fields)).
+A client script is a `ClientScriptEntry`: `{ importFrom, importName? }` (`importName` defaults `'default'`). The field varies by entry kind: an `action` entry's `action` runs when the dock button is activated, a `custom-render` entry's `renderer` renders its panel, and an `iframe` entry's optional `clientScript` runs alongside the iframe panel inside the host page ([Hub API reference](/references/hub-api#dock-client-script-fields)).
 
-Hub UI normally imports an iframe's client script when its dock is first activated. Set `eager: true` when the script must start observing the host app earlier: the module is imported and its exported function runs once, as soon as both the client context and dock entry are available. This is execution timing, not module preloading; it does not wait for the dock panel to open.
+An iframe entry normally runs its client script on first activation. Set `clientScript.eager: true` to run it once as soon as the client context and dock entry are available.
 
 The exported function (`DockClientScriptContext`) receives the client context and two dock-scoped extras:
 

docs/content/8.references/5.browser-api.md

@@ -52,8 +52,6 @@ The browser-only endpoint methods of the [in-page channel](/guide/in-page-channe
 
 `InPageChannelProtocol` separates `functions` and `events`. Each section has optional `pageScript` and `panel` maps naming the receiving direction. Endpoint options require a complete `functions` map with handlers; `events` is optional, and when provided can include optional handlers (use `{}` to declare an event without a handler for `channel.on()`). `call()` uses function names regardless of return type, while `emit()`, `callEvent()` (deprecated), and `on()` use event names. A function returning `void` or `Promise<void>` remains an awaitable request/response call.
 
-In-page endpoint functions carrying `agent` are synchronized through the page's DevFrame connection to the node MCP endpoint. Agent functions require `jsonSerializable: true`; events cannot be exposed.
-
 | Method or property | Page-script endpoint | Panel endpoint |
 |--------------------|-------------|-------|
 | `emit(name, ...args)` | Fans an event out to every connected panel. | Sends an event to the page script, buffering while connecting. |

docs/content/8.references/6.hub-api.md

@@ -127,13 +127,13 @@ The properties of `DevframeClientContext`: [The client context](/guide/client-co
 
 Which `ClientScriptEntry` field carries an entry's client script, and when it runs: [Dock client scripts](/guide/client-context#dock-client-scripts).
 
-Every client script specifies `importFrom` and may specify `importName` (default: `default`). An iframe `clientScript` may additionally set `eager: true` to import and execute once as soon as the client context and dock entry are available, before activation.
+`ClientScriptEntry` requires `importFrom` and accepts `importName` (default: `default`).
 
 | Entry kind | Field | Runs |
 |---|---|---|
 | `action` | `action` | when the dock button is activated |
 | `custom-render` | `renderer` | to render the entry's panel |
-| `iframe` | `clientScript` (optional) | alongside the iframe panel, inside the host page |
+| `iframe` | `clientScript` (optional) | on first activation, or when the client context and dock entry become available with `clientScript.eager: true` |
 
 ## Frame-nav messages