dsh-builtin-browser 0.4.7 → 0.4.8

package/lib/tool-browser/element-fields.js

@@ -8,9 +8,9 @@
  * and the tool's `output.schema` declared the properties. Nothing connected them, and the
  * result is this project's most repeatable bug:
  *
- *   - `browser_a11y`'s `selector` — computed by the provider, declared by the schema,
+ *   - `dsh_browser_a11y`'s `selector` — computed by the provider, declared by the schema,
  *     printed by the renderer, and dropped by the projection. 134 tests stayed green.
- *   - `browser_screenshot`'s `width`/`height` — measured by the provider, declared by the
+ *   - `dsh_browser_screenshot`'s `width`/`height` — measured by the provider, declared by the
  *     schema, and dropped by the projection. 172 tests stayed green. It was found a round
  *     later, by reading the three places that agree and noticing the fourth did not.
  *
@@ -24,7 +24,7 @@
  * projection forgets is silently dropped. One table cannot get either wrong on its own.
  */
 /**
- * The fields of one entry in `browser_snapshot` / `browser_open`'s `elements`.
+ * The fields of one entry in `dsh_browser_snapshot` / `dsh_browser_open`'s `elements`.
  *
  * `selector` is the reason this file exists; see the header. It was added to the schema and
  * the projection separately, and only one of them landed.
@@ -39,7 +39,7 @@ const ELEMENT_FIELDS = {
     frame: { schema: { type: 'boolean' } },
 };
 /**
- * The fields of one entry in `browser_a11y`'s `nodes`.
+ * The fields of one entry in `dsh_browser_a11y`'s `nodes`.
  *
  * Different shape from an element on purpose: a role and an accessible name carry meaning a
  * tag and a label string do not, and `depth` is what renders the tree.
@@ -80,7 +80,7 @@ function project(fields, source) {
     return out;
 }
 /**
- * The `elements` item schema for browser_snapshot and browser_open.
+ * The `elements` item schema for dsh_browser_snapshot and dsh_browser_open.
  *
  * Written as a literal rather than generated, because `defineTool` validates the output schema
  * against its own `ValueSchemaSpec` and a generated `Record<string, …>` is too wide to satisfy
@@ -102,7 +102,7 @@ export const ELEMENT_ITEM_SCHEMA = {
     },
 };
 /**
- * The `nodes` item schema for browser_a11y.
+ * The `nodes` item schema for dsh_browser_a11y.
  *
  * Same reasoning as {@link ELEMENT_ITEM_SCHEMA}: literal for the type checker, table-backed by
  * test.

package/lib/tool-browser/index.d.ts

@@ -1,14 +1,14 @@
 /**
- * Model-facing browser tools over `ctx.browser`: `browser_open`,
- * `browser_snapshot`, `browser_execute`, `browser_content`,
- * `browser_screenshot`, and tab management (`browser_list_tabs`,
- * `browser_switch_tab`, `browser_close_tab`, `browser_reset`).
+ * Model-facing browser tools over `ctx.browser`: `dsh_browser_open`,
+ * `dsh_browser_snapshot`, `dsh_browser_execute`, `dsh_browser_content`,
+ * `dsh_browser_screenshot`, and tab management (`dsh_browser_list_tabs`,
+ * `dsh_browser_switch_tab`, `dsh_browser_close_tab`, `dsh_browser_reset`).
  *
  * The tool layer owns only the model-facing schema, argument validation, and
  * result formatting — never provider selection or page driving, which belong
  * to the seam. Session lifecycle is owned here at the plugin level: each
  * calling task (a DSH session) gets its own browser session — the first
- * `browser_open` (or any tool when no session exists) opens it, and later
+ * `dsh_browser_open` (or any tool when no session exists) opens it, and later
  * tools in the same task reuse it. Concurrent tasks therefore never fight
  * over tabs, history, or navigation state.
  * @module dsh-browser/tool-browser
@@ -38,7 +38,7 @@ export interface Config {
  * Tools that only observe, plus the ones that undo a restriction.
  *
  * Never subject to an allow-list: restricting what the agent may *do* must not also
- * blind it or trap it, and the tool descriptions promise as much. browser_restrict
+ * blind it or trap it, and the tool descriptions promise as much. dsh_browser_restrict
  * is in here so a task that restricted everything can still lift it.
  */
 export declare const READ_ONLY_TOOLS: ReadonlySet<string>;