@perspective-dev/viewer 5.1.0 → 5.2.0

package/dist/esm/ts-rs/ViewerConfigInitial.d.ts

@@ -0,0 +1,175 @@
+import type { Aggregate } from "./Aggregate.js";
+import type { Expressions } from "./Expressions.js";
+import type { Filter } from "./Filter.js";
+import type { FilterReducer } from "./FilterReducer.js";
+import type { GroupRollupMode } from "./GroupRollupMode.js";
+import type { Sort } from "./Sort.js";
+import type { SplitRollupMode } from "./SplitRollupMode.js";
+import type { Windows } from "./Windows.js";
+import type { JsonValue } from "./serde_json/JsonValue.js";
+/**
+ * The initial configuration of a NEW panel (`addPanel`, `restore`'s
+ * panel-creating upsert, `restoreWorkspace` `panels` entries). Unlike
+ * [`ViewerConfigUpdate`] — a patch against existing state — creation has
+ * no prior state: `table` is REQUIRED (a placed panel without a table
+ * binding would be permanently blank), absent fields mean "default"
+ * rather than "leave unchanged" (so no [`OptionalUpdate`] tri-state), and
+ * there is no `settings` field (element-level, not per-panel).
+ */
+export type ViewerConfigInitial = {
+    /**
+     * Name of the `Table` the new panel renders, as hosted on the
+     * `Client`. REQUIRED: a placed panel with no table binding would be
+     * permanently blank.
+     */
+    table: string;
+    /**
+     * The `@perspective-dev/viewer` version a saved config was written
+     * by. Omit it when creating a panel.
+     */
+    version?: string;
+    /**
+     * Name of the visualization plugin, from the set registered on the
+     * page (the `list_plugins` agent tool, or the plugin picker).
+     * Decides what the view fields MEAN: `columns` is positional and
+     * every plugin reads the positions differently, and
+     * `group_by`/`split_by` draw different things per plugin. Absent
+     * uses the default plugin.
+     */
+    plugin?: string;
+    /**
+     * Panel title, shown in its tab. Absent renders the default title.
+     */
+    title?: string;
+    /**
+     * Theme NAME (e.g. `"Pro Dark"`) — not a CSS value. Valid names are
+     * the Perspective themes loaded on the page. Absent uses the
+     * default.
+     */
+    theme?: string;
+    /**
+     * Plugin-wide settings (as opposed to the per-column
+     * [`Self::columns_config`]). Opaque to the viewer and defined by
+     * the ACTIVE plugin; query the valid keys with `get_style_schema`
+     * rather than guessing.
+     */
+    plugin_config?: {
+        [key in string]?: JsonValue;
+    };
+    /**
+     * Per-column styling — formatting, colors, and other per-column
+     * controls — keyed by column name. Plugin-defined like
+     * [`Self::plugin_config`]; see `get_style_schema`.
+     */
+    columns_config?: {
+        [key in string]?: {
+            [key in string]?: JsonValue;
+        };
+    };
+    /**
+     * A group by _groups_ the dataset by the unique values of each column used
+     * as a group by - a close analogue in SQL to the `GROUP BY` statement.
+     * The underlying dataset is aggregated to show the values belonging to
+     * each group, and a total row is calculated for each group, showing
+     * the currently selected aggregated value (e.g. `sum`) of the column.
+     * Group by are useful for hierarchies, categorizing data and
+     * attributing values, i.e. showing the number of units sold based on
+     * State and City. In Perspective, group by are represented as an array
+     * of string column names to pivot, are applied in the order provided;
+     * For example, a group by of `["State", "City", "Postal Code"]` shows
+     * the values for each Postal Code, which are grouped by City,
+     * which are in turn grouped by State.
+     */
+    group_by?: Array<string>;
+    /**
+     * A split by _splits_ the dataset by the unique values of each column used
+     * as a split by. The underlying dataset is not aggregated, and a new
+     * column is created for each unique value of the split by. Each newly
+     * created column contains the parts of the dataset that correspond to
+     * the column header, i.e. a `View` that has `["State"]` as its split
+     * by will have a new column for each state. In Perspective, Split By
+     * are represented as an array of string column names to pivot.
+     */
+    split_by?: Array<string>;
+    /**
+     * The `columns` property specifies which columns should be included in the
+     * [`crate::View`]'s output. This allows users to show or hide a specific
+     * subset of columns, as well as control the order in which columns
+     * appear to the user. This is represented in Perspective as an array
+     * of string column names.
+     */
+    columns?: Array<string | null>;
+    /**
+     * The `filter` property specifies columns on which the query can be
+     * filtered, returning rows that pass the specified filter condition.
+     * This is analogous to the `WHERE` clause in SQL. There is no limit on
+     * the number of columns where `filter` is applied, but the resulting
+     * dataset is one that passes all the filter conditions, i.e. the
+     * filters are joined with an `AND` condition.
+     *
+     * Perspective represents `filter` as an array of arrays, with the values
+     * of each inner array being a string column name, a string filter
+     * operator, and a filter operand in the type of the column.
+     */
+    filter?: Array<Filter>;
+    /**
+     * The `sort` property specifies columns on which the query should be
+     * sorted, analogous to `ORDER BY` in SQL. A column can be sorted
+     * regardless of its data type, and sorts can be applied in ascending
+     * or descending order. Perspective represents `sort` as an array of
+     * arrays, with the values of each inner array being a string column
+     * name and a string sort direction. When `column-pivots` are applied,
+     * the additional sort directions `"col asc"` and `"col desc"` will
+     * determine the order of pivot columns groups.
+     *
+     * `sort` is the ONLY thing that orders a `View`'s rows — without it
+     * they keep the `Table`'s natural (insertion) order, which any
+     * consumer reading rows sequentially will reflect. Not to be
+     * confused with a window column's `order_by`, which orders rows
+     * WITHIN a window frame and does not reorder the `View`.
+     */
+    sort?: Array<Sort>;
+    /**
+     * The `expressions` property specifies _new_ columns in Perspective that
+     * are created using existing column values or arbitary scalar values
+     * defined within the expression. In `<perspective-viewer>`,
+     * expressions are added using the "New Column" button in the side
+     * panel.
+     */
+    expressions?: Expressions;
+    /**
+     * The `windows` property declares ordered, partitioned rolling
+     * computations (moving aggregates, cumulative sums) as _new_ columns
+     * keyed by output alias (`{"name": {...spec}}`, symmetric with
+     * `expressions`), analogous to SQL window functions. See
+     * [`crate::config::WindowSpec`].
+     */
+    windows?: Windows;
+    /**
+     * Aggregates perform a calculation over an entire column, and are
+     * displayed when one or more [Group By](#group-by) are applied to the
+     * `View`. Aggregates can be specified by the user, or Perspective will
+     * use the following sensible default aggregates based on column type:
+     *
+     * - "sum" for `integer` and `float` columns
+     * - "count" for all other columns
+     *
+     * Perspective provides a selection of aggregate functions that can be
+     * applied to columns in the `View` constructor using a dictionary of
+     * column name to aggregate function name.
+     *
+     * An aggregate also determines the column's RESULT TYPE, which need
+     * not match the input: `"count"` yields an `integer` whatever it
+     * counts, so a `date` column left on the default `"count"` is an
+     * `integer` in the resulting `View` — no longer a date. Set an
+     * aggregate that preserves the type (e.g. `"any"`, `"last"`) when
+     * the original type matters, such as a date used as a chart axis.
+     */
+    aggregates?: {
+        [key in string]?: Aggregate;
+    };
+    group_by_depth?: number;
+    filter_op?: FilterReducer;
+    group_rollup_mode?: GroupRollupMode;
+    split_rollup_mode?: SplitRollupMode;
+};

package/dist/esm/ts-rs/ViewerConfigUpdate.d.ts

@@ -5,18 +5,67 @@ import type { FilterReducer } from "./FilterReducer.js";
 import type { GroupRollupMode } from "./GroupRollupMode.js";
 import type { OptionalUpdate } from "./OptionalUpdate.js";
 import type { Sort } from "./Sort.js";
+import type { SplitRollupMode } from "./SplitRollupMode.js";
 import type { Windows } from "./Windows.js";
 import type { JsonValue } from "./serde_json/JsonValue.js";
 export type ViewerConfigUpdate = {
+    /**
+     * The `@perspective-dev/viewer` version a saved config was written
+     * by, used to migrate older tokens. Omit it — the viewer stamps
+     * the current version on save.
+     */
     version?: OptionalUpdate<string>;
+    /**
+     * Name of the visualization plugin to switch to, from the set
+     * registered on the page (the `list_plugins` agent tool, or the
+     * plugin picker). Changing it changes what the view fields MEAN:
+     * `columns` is positional and every plugin reads the positions
+     * differently, and `group_by`/`split_by` draw different things per
+     * plugin — so read the new plugin's roles before writing `columns`
+     * for it.
+     */
     plugin?: OptionalUpdate<string>;
+    /**
+     * Panel title, shown in its tab. `null` restores the default
+     * title; omitting the field leaves the current one.
+     */
     title?: OptionalUpdate<string>;
+    /**
+     * Name of the `Table` to render, as hosted on this panel's
+     * `Client`. Rebinding an existing panel to another table keeps the
+     * rest of the config, so column names that do not exist in the new
+     * table will fail validation.
+     */
     table?: OptionalUpdate<string>;
+    /**
+     * Theme NAME (e.g. `"Pro Dark"`) — not a CSS value. Valid names are
+     * the Perspective themes loaded on the page, re-scanned by
+     * `resetThemes()`. `null` selects the default.
+     */
     theme?: OptionalUpdate<string>;
+    /**
+     * Whether the settings sidebar is OPEN. Purely cosmetic chrome —
+     * it does not affect what the viewer renders, and it is
+     * element-level rather than per-panel.
+     */
     settings?: OptionalUpdate<boolean>;
+    /**
+     * Plugin-wide settings (as opposed to the per-column
+     * [`Self::columns_config`]). The viewer passes these through
+     * opaquely — their valid keys are defined by the ACTIVE plugin and
+     * vary by plugin and by state, so query them with the
+     * `get_style_schema` agent tool rather than guessing.
+     */
     plugin_config?: OptionalUpdate<{
         [key in string]?: JsonValue;
     }>;
+    /**
+     * Per-column styling — formatting, colors, and other per-column
+     * controls — keyed by column name. Opaque to the viewer and
+     * plugin-defined like [`Self::plugin_config`]; `get_style_schema`
+     * reports the valid keys for a given column under the active
+     * plugin.
+     */
     columns_config?: OptionalUpdate<{
         [key in string]?: {
             [key in string]?: JsonValue;
@@ -77,6 +126,12 @@ export type ViewerConfigUpdate = {
      * name and a string sort direction. When `column-pivots` are applied,
      * the additional sort directions `"col asc"` and `"col desc"` will
      * determine the order of pivot columns groups.
+     *
+     * `sort` is the ONLY thing that orders a `View`'s rows — without it
+     * they keep the `Table`'s natural (insertion) order, which any
+     * consumer reading rows sequentially will reflect. Not to be
+     * confused with a window column's `order_by`, which orders rows
+     * WITHIN a window frame and does not reorder the `View`.
      */
     sort?: Array<Sort>;
     /**
@@ -107,6 +162,13 @@ export type ViewerConfigUpdate = {
      * Perspective provides a selection of aggregate functions that can be
      * applied to columns in the `View` constructor using a dictionary of
      * column name to aggregate function name.
+     *
+     * An aggregate also determines the column's RESULT TYPE, which need
+     * not match the input: `"count"` yields an `integer` whatever it
+     * counts, so a `date` column left on the default `"count"` is an
+     * `integer` in the resulting `View` — no longer a date. Set an
+     * aggregate that preserves the type (e.g. `"any"`, `"last"`) when
+     * the original type matters, such as a date used as a chart axis.
      */
     aggregates?: {
         [key in string]?: Aggregate;
@@ -114,4 +176,5 @@ export type ViewerConfigUpdate = {
     group_by_depth?: number;
     filter_op?: FilterReducer;
     group_rollup_mode?: GroupRollupMode;
+    split_rollup_mode?: SplitRollupMode;
 };

package/dist/esm/ts-rs/WindowSpec.d.ts

@@ -1,4 +1,3 @@
-import type { WindowAggregate } from "./WindowAggregate.js";
 import type { WindowSort } from "./WindowSort.js";
 /**
  * The serialized form of [`WindowSpec`].
@@ -9,7 +8,7 @@ export type WindowSpec = {
      * alias from the same `ViewConfig`.
      */
     column: string;
-    aggregate: WindowAggregate;
+    aggregate: string;
     /**
      * Columns whose distinct value tuples partition the rows; empty
      * partitions the whole `Table` as one group.
@@ -17,6 +16,8 @@ export type WindowSpec = {
     partition_by?: Array<string>;
     /**
      * The `Table` column which orders each partition, and the direction.
+     * This orders rows WITHIN the window frame only — it does not
+     * reorder the `View`, which is what the view-level `sort` does.
      */
     order_by?: WindowSort | null;
     /**

package/dist/esm/ts-rs/WorkspaceConfigUpdate.d.ts

@@ -1,18 +1,19 @@
 import type { Filter } from "./Filter.js";
 import type { Layout } from "./Layout.js";
-import type { ViewerConfigUpdate } from "./ViewerConfigUpdate.js";
+import type { ViewerConfigInitial } from "./ViewerConfigInitial.js";
 /**
  * The parse target of a whole-element config in
- * [`PerspectiveViewerElement::restore`]. Mirrors [`WorkspaceConfig`],
- * but `panels` entries are full [`ViewerConfigUpdate`]s so a stray per-panel
- * `settings` can be detected (warned, then ignored — `create_panel` strips
- * it).
+ * [`PerspectiveViewerElement::restoreWorkspace`]. Mirrors
+ * [`WorkspaceConfig`], but `panels` entries are [`ViewerConfigInitial`]s —
+ * every entry creates a NEW panel, so `table` is required by type (a
+ * stray per-panel `settings` key is ignored; it is element-level state,
+ * carried by the top-level `active` field).
  */
 export type WorkspaceConfigUpdate = {
     active?: string;
     layout?: Layout;
     panels: {
-        [key in string]?: ViewerConfigUpdate;
+        [key in string]?: ViewerConfigInitial;
     };
     /**
      * The element-level global (master/detail cross-) filters to re-apply as

package/dist/wasm/perspective-viewer.d.ts

@@ -104,22 +104,33 @@ import type {
 
 export type * from "../../src/ts/ts-rs/ViewerConfig.d.ts";
 export type * from "../../src/ts/ts-rs/ViewerConfigUpdate.d.ts";
+export type * from "../../src/ts/ts-rs/ViewerConfigInitial.d.ts";
 export type * from "../../src/ts/ts-rs/PluginStaticConfig.d.ts";
 export type * from "../../src/ts/ts-rs/WorkspaceConfig.d.ts";
 export type * from "../../src/ts/ts-rs/WorkspaceConfigUpdate.d.ts";
 export type * from "../../src/ts/ts-rs/ExportMethod.d.ts";
 export type * from "../../src/ts/ts-rs/PanelOptions.d.ts";
+export type * from "../../src/ts/ts-rs/RestoreOptions.d.ts";
 export type * from "../../src/ts/ts-rs/ClientOptions.d.ts";
 export type * from "../../src/ts/ts-rs/ExportOptions.d.ts";
 export type * from "../../src/ts/ts-rs/GetTableOptions.d.ts";
 export type * from "../../src/ts/ts-rs/GetClientOptions.d.ts";
+export type * from "../../src/ts/ts-rs/CustomNumberFormatConfig.d.ts";
+export type * from "../../src/ts/ts-rs/NumberFormatStyle.d.ts";
+export type * from "../../src/ts/ts-rs/Notation.d.ts";
+export type * from "../../src/ts/ts-rs/DatetimeFormatType.d.ts";
+export type * from "../../src/ts/ts-rs/StringColorMode.d.ts";
+export type * from "../../src/ts/ts-rs/DatetimeColorMode.d.ts";
+export type * from "../../src/ts/ts-rs/FormatMode.d.ts";
 import type {GetTableOptions} from "../../src/ts/ts-rs/GetTableOptions.d.ts";
 import type {PanelOptions} from "../../src/ts/ts-rs/PanelOptions.d.ts";
+import type {RestoreOptions} from "../../src/ts/ts-rs/RestoreOptions.d.ts";
 import type {ExportOptions} from "../../src/ts/ts-rs/ExportOptions.d.ts";
 import type {GetClientOptions} from "../../src/ts/ts-rs/GetClientOptions.d.ts";
 import type {ClientOptions} from "../../src/ts/ts-rs/ClientOptions.d.ts";
 import type {ViewerConfig} from "../../src/ts/ts-rs/ViewerConfig.d.ts";
 import type {ViewerConfigUpdate} from "../../src/ts/ts-rs/ViewerConfigUpdate.d.ts";
+import type {ViewerConfigInitial} from "../../src/ts/ts-rs/ViewerConfigInitial.d.ts";
 import type {WorkspaceConfig} from "../../src/ts/ts-rs/WorkspaceConfig.d.ts";
 import type {WorkspaceConfigUpdate} from "../../src/ts/ts-rs/WorkspaceConfigUpdate.d.ts";
 
@@ -529,14 +540,98 @@ export class PerspectiveViewerElement {
     __get_model(): PerspectiveViewerElement;
     /**
      * Add a new, independent panel to this viewer's layout, rendering the
-     * supplied [`ViewerConfigUpdate`] into it. The panel uses the default
-     * [`perspective_client::Client`] (the first passed to [`Self::load`]) to
-     * resolve its `table`. Returns the generated panel id.
+     * supplied [`ViewerConfigInitial`] into it. Unlike [`Self::restore`]'s
+     * update-shaped argument, a new panel has no prior state, so `table`
+     * is REQUIRED — a table-less call rejects before the layout is
+     * touched. The panel uses the default [`perspective_client::Client`]
+     * (the first passed to [`Self::load`]) to resolve its `table`. Returns
+     * the generated panel id.
+     *
+     * The element-level `settings` field does not exist on the argument
+     * type (it is shared across the element, not per-panel).
+     */
+    addPanel(config: ViewerConfigInitial): Promise<any>;
+    /**
+     * Configure the embedded LLM agent (see `prompt()`), replacing any prior
+     * configuration and conversation.
+     *
+     * The agent core is provider-agnostic: one OpenAI-chat-completions
+     * protocol over primitive connection fields. Exactly one of
+     * `config.url` or `config.engine` is required; the `providers` presets
+     * exported by this package are plain spreadable collections of these
+     * fields (`{...providers.anthropic, apiKey}`).
+     *
+     * - `config.url` - a full chat-completions endpoint URL (any
+     *   OpenAI-compatible service: Anthropic/Gemini compatibility endpoints,
+     *   LM Studio, Ollama, OpenRouter, a proxy...).
+     * - `config.engine` - an in-page engine object with an OpenAI-compatible
+     *   `chat.completions.create(request)` method (e.g. WebLLM's `MLCEngine`);
+     *   mutually exclusive with `url`.
+     * - `config.headers` - extra request headers, sent verbatim.
+     * - `config.apiKey` - sugar for the `Authorization: Bearer` header.
+     * - `config.model` - model id sent with each request; local servers and
+     *   engines generally answer with whatever model is loaded.
+     * - `config.name` - cosmetic label for the chat badge (presets set this).
+     * - `config.systemPrompt` - extra system-prompt context appended to the
+     *   agent's built-in instructions.
+     * - `config.maxTurns` - max model turns (tool-call rounds + the final
+     *   answer) per `prompt()` call. Defaults to 16.
+     * - `config.docs` - the agent metadata bundle, which supplies the
+     *   `search_docs` corpus and the rich tool parameter schemas: the packaged
+     *   `dist/docs/perspective-docs.json` asset as a parsed object (`import
+     *   docs from "…json" with { type: "json" }`), a `fetch()` `Response`, an
+     *   `ArrayBuffer`, a JSON string, or a `Promise` of any of those — and/or
+     *   an inline array of `{title?, text}` entries for host data definitions.
+     *   Omitted, `search_docs` searches an empty corpus and the parameter
+     *   schemas degrade to permissive objects.
+     * - `config.systemRole` - where the preamble (plus `systemPrompt`) is
+     *   placed: `"system"` (default) or `"user"`. Some engines refuse a system
+     *   message alongside `tools` because they substitute their own — WebLLM's
+     *   Hermes function calling throws `CustomSystemPromptError` on ANY system
+     *   message — and those need `"user"`, which folds the same text into the
+     *   opening user turn.
+     * - `config.entitlements` - access grants limiting which tools the agent
+     *   is offered (and may call): any of `"read_view"`, `"configure_view"`,
+     *   `"manage_layout"`, `"read_docs"`, `"read_data"`. Omitted, all but
+     *   `"read_data"` are granted; `["read_view", "read_docs"]` yields a
+     *   read-only agent.
      *
-     * Element-level config fields (`settings`, `theme`) in the argument are
-     * ignored — those are shared across the element, not per-panel.
+     * # JavaScript Examples
+     *
+     * ```javascript
+     * import { providers } from "@perspective-dev/viewer";
+     *
+     * viewer.agentConfig({
+     *     ...providers.anthropic,
+     *     apiKey: "sk-ant-...",
+     *     docs: fetch(
+     *         "node_modules/@perspective-dev/viewer/dist/docs/perspective-docs.json",
+     *     ),
+     * });
+     * ```
+     */
+    agentConfig(config: any): void;
+    /**
+     * Run one conversational turn of the embedded LLM agent (configured via
+     * `agentConfig()`), resolving with the agent's final text response after
+     * any tool calls have been applied to this element. Turns share a
+     * conversation history (and the chat sidebar's transcript) until
+     * `agentReset()`; a call made while a turn is already running rejects.
+     * Tool activity is emitted as `perspective-agent-tool` CustomEvents on
+     * this element.
+     *
+     * # JavaScript Examples
+     *
+     * ```javascript
+     * await viewer.agentPrompt("Show me sales by region as a bar chart");
+     * ```
+     */
+    agentPrompt(prompt: string): Promise<any>;
+    /**
+     * Clear the agent's conversation (history and chat transcript), keeping
+     * its configuration. Cancels any in-flight turn.
      */
-    addPanel(update: ViewerConfigUpdate): Promise<any>;
+    agentReset(): Promise<any>;
     connectedCallback(): void;
     /**
      * Copy this viewer's `View` or `Table` data as CSV to the system
@@ -935,9 +1030,12 @@ export class PerspectiveViewerElement {
      * optional `{panel}` selector.
      *
      * If `panel` names no existing panel, a NEW panel is created with that id
-     * and the config restored into it (an upsert), equivalent to
-     * [`Self::addPanel`] but with a caller-chosen id. As with a created panel,
+     * and the config restored into it (an upsert). As with a created panel,
      * the element-level `settings`/`theme` fields are ignored in that case.
+     * Unlike [`Self::addPanel`], the argument is a PATCH, so a `table` is
+     * optional: creating without one yields a DEFERRED panel that the next
+     * [`Self::load`] binds. Such a panel renders but cannot be serialized —
+     * [`Self::save`] rejects with "Panel has no `table`" until it is bound.
      *
      * On an empty element with a pending [`Self::load`] whose payload is not
      * yet classified, the active-target form (no `panel`) instead claims and
@@ -956,7 +1054,15 @@ export class PerspectiveViewerElement {
      *
      * - `update` - The config to restore to, as returned by [`Self::save`] in
      *   either "json", "string" or "arraybuffer" format.
-     * - `name` - The panel to target, or `None` for the active panel.
+     * - `options.panel` - The panel to target, or the active panel when
+     *   omitted.
+     * - `options.suppress_errors` - when `true`, a failed restore only rejects
+     *   the returned `Promise`; the error is NOT committed to the viewer's
+     *   visible error state and the session remains usable. The view config is
+     *   rolled back to its pre-call value, so a rejected patch cannot re-merge
+     *   into a later restore. Element-level state the call already applied
+     *   (theme, title, a plugin swap) is NOT undone — restore a known-good
+     *   config to recover those exactly.
      *
      * # JavaScript Examples
      *
@@ -974,7 +1080,7 @@ export class PerspectiveViewerElement {
      * await viewer.restore({group_by: ["State"]});
      * ```
      */
-    restore(update: ViewerConfigUpdate, options?: PanelOptions | null): Promise<void>;
+    restore(update: ViewerConfigUpdate, options?: RestoreOptions | null): Promise<void>;
     /**
      * Restore the ENTIRE element from a whole-element
      * [`WorkspaceConfigUpdate`] (`{version, active?, layout, panels, ...}`) —
@@ -1655,6 +1761,9 @@ export interface InitOutput {
     readonly perspectivedebugpluginelement_update: (a: number, b: number) => number;
     readonly perspectiveviewerelement___get_model: (a: number) => number;
     readonly perspectiveviewerelement_addPanel: (a: number, b: number) => number;
+    readonly perspectiveviewerelement_agentConfig: (a: number, b: number, c: number) => void;
+    readonly perspectiveviewerelement_agentPrompt: (a: number, b: number, c: number) => number;
+    readonly perspectiveviewerelement_agentReset: (a: number) => number;
     readonly perspectiveviewerelement_connectedCallback: (a: number, b: number) => void;
     readonly perspectiveviewerelement_copy: (a: number, b: number) => number;
     readonly perspectiveviewerelement_delete: (a: number) => number;
@@ -1791,21 +1900,21 @@ export interface InitOutput {
     readonly virtualdataslice_setStringCol: (a: number, b: number, c: number, d: number, e: number, f: number, g: number) => void;
     readonly virtualserver_handleRequest: (a: number, b: number, c: number) => number;
     readonly virtualserver_new: (a: number, b: number) => void;
-    readonly __wasm_bindgen_func_elem_3667: (a: number, b: number) => void;
-    readonly __wasm_bindgen_func_elem_16364: (a: number, b: number) => void;
-    readonly __wasm_bindgen_func_elem_19409: (a: number, b: number) => void;
-    readonly __wasm_bindgen_func_elem_20067: (a: number, b: number) => void;
-    readonly __wasm_bindgen_func_elem_20096: (a: number, b: number) => void;
-    readonly __wasm_bindgen_func_elem_27549: (a: number, b: number, c: number, d: number) => void;
-    readonly __wasm_bindgen_func_elem_6430: (a: number, b: number, c: number) => void;
-    readonly __wasm_bindgen_func_elem_6431: (a: number, b: number, c: number) => void;
-    readonly __wasm_bindgen_func_elem_6432: (a: number, b: number, c: number) => void;
-    readonly __wasm_bindgen_func_elem_6428: (a: number, b: number, c: number) => void;
-    readonly __wasm_bindgen_func_elem_19529: (a: number, b: number, c: number) => void;
-    readonly __wasm_bindgen_func_elem_20072: (a: number, b: number, c: number) => void;
-    readonly __wasm_bindgen_func_elem_20113: (a: number, b: number, c: number) => void;
-    readonly __wasm_bindgen_func_elem_17084: (a: number, b: number) => number;
-    readonly __wasm_bindgen_func_elem_20071: (a: number, b: number) => void;
+    readonly __wasm_bindgen_func_elem_17003: (a: number, b: number) => void;
+    readonly __wasm_bindgen_func_elem_17713: (a: number, b: number) => void;
+    readonly __wasm_bindgen_func_elem_18571: (a: number, b: number) => void;
+    readonly __wasm_bindgen_func_elem_3989: (a: number, b: number) => void;
+    readonly __wasm_bindgen_func_elem_23208: (a: number, b: number) => void;
+    readonly __wasm_bindgen_func_elem_31328: (a: number, b: number, c: number, d: number) => void;
+    readonly __wasm_bindgen_func_elem_17122: (a: number, b: number, c: number) => void;
+    readonly __wasm_bindgen_func_elem_17718: (a: number, b: number, c: number) => void;
+    readonly __wasm_bindgen_func_elem_6981: (a: number, b: number, c: number) => void;
+    readonly __wasm_bindgen_func_elem_6982: (a: number, b: number, c: number) => void;
+    readonly __wasm_bindgen_func_elem_6983: (a: number, b: number, c: number) => void;
+    readonly __wasm_bindgen_func_elem_6979: (a: number, b: number, c: number) => void;
+    readonly __wasm_bindgen_func_elem_23225: (a: number, b: number, c: number) => void;
+    readonly __wasm_bindgen_func_elem_19569: (a: number, b: number) => number;
+    readonly __wasm_bindgen_func_elem_17717: (a: number, b: number) => void;
     readonly __wbindgen_export: (a: number, b: number) => number;
     readonly __wbindgen_export2: (a: number, b: number, c: number, d: number) => number;
     readonly __wbindgen_export3: (a: number) => void;