@perspective-dev/viewer 5.0.0 → 5.2.0

package/src/ts/ts-rs/PanelViewerConfig.ts

@@ -5,6 +5,8 @@ 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";
 
 /**
@@ -12,4 +14,49 @@ import type { JsonValue } from "./serde_json/JsonValue.js";
  * element-level `settings` flag. This is the `panels` entry type of the
  * whole-element config format.
  */
-export type PanelViewerConfig<V = string> = { version: V, columns_config: { [key in string]?: { [key in string]?: JsonValue } }, plugin: string, plugin_config: { [key in string]?: JsonValue }, table: string | null, theme: string | null, title: string | null, group_by: Array<string>, split_by: Array<string>, sort: Array<Sort>, filter: Array<Filter>, group_rollup_mode: GroupRollupMode, filter_op?: FilterReducer, expressions: Expressions, columns: Array<string | null>, aggregates: { [key in string]?: Aggregate }, group_by_depth?: number | null, };
+export type PanelViewerConfig<V = string> = { 
+/**
+ * The `@perspective-dev/viewer` version that wrote this config,
+ * stamped on save and used to migrate older tokens. Callers do not
+ * set it.
+ */
+version: V, 
+/**
+ * Per-column styling, keyed by column name. The viewer treats the
+ * values as opaque — their shape is defined by the ACTIVE plugin,
+ * so a config written for one plugin may carry keys another
+ * ignores. Query the live shape with the `get_style_schema` agent
+ * tool, or the plugin's `column_config_schema()`.
+ */
+columns_config: { [key in string]?: { [key in string]?: JsonValue } }, 
+/**
+ * Name of the visualization plugin, from the set registered on the
+ * page (the `list_plugins` agent tool, or the plugin picker). This
+ * also decides what the view fields MEAN visually: `columns` is
+ * positional and each plugin reads the positions differently, and
+ * `group_by`/`split_by` draw different things per plugin.
+ */
+plugin: string, 
+/**
+ * Plugin-wide settings (as opposed to the per-column
+ * [`Self::columns_config`]). Opaque to the viewer and defined by
+ * the active plugin; see `get_style_schema`.
+ */
+plugin_config: { [key in string]?: JsonValue }, 
+/**
+ * Name of the `Table` this panel renders, as hosted on the panel's
+ * `Client`. Every placed panel has a table binding (creation
+ * requires one by type — [`ViewerConfigInitial`]), so the saved
+ * config carries it unconditionally.
+ */
+table: string, 
+/**
+ * Selected theme NAME (e.g. `"Pro Dark"`) — not a CSS value. Valid
+ * names are the Perspective themes loaded on the page, which
+ * `resetThemes()` re-scans. `None` selects the first available.
+ */
+theme: string | null, 
+/**
+ * Panel title, shown in its tab. `None` renders the default title.
+ */
+title: string | null, group_by: Array<string>, split_by: Array<string>, sort: Array<Sort>, filter: Array<Filter>, group_rollup_mode: GroupRollupMode, split_rollup_mode: SplitRollupMode, filter_op?: FilterReducer, expressions: Expressions, windows?: Windows, columns: Array<string | null>, aggregates: { [key in string]?: Aggregate }, group_by_depth?: number | null, };

package/src/ts/ts-rs/PluginStaticConfig.ts

@@ -1,6 +1,7 @@
 // This file was generated by [ts-rs](https://github.com/Aleph-Alpha/ts-rs). Do not edit this file manually.
 import type { ColumnSelectMode } from "./ColumnSelectMode.js";
 import type { GroupRollupMode } from "./GroupRollupMode.js";
+import type { SplitRollupMode } from "./SplitRollupMode.js";
 
 /**
  * Static, immutable configuration for a plugin.
@@ -62,6 +63,11 @@ config_column_names?: Array<string>,
  * The first entry that matches a feature flag becomes the default.
  */
 group_rollup_modes?: Array<GroupRollupMode> | null, 
+/**
+ * Split-rollup modes the plugin accepts, in preference order.
+ * The first entry that matches a feature flag becomes the default.
+ */
+split_rollup_modes?: Array<SplitRollupMode> | null, 
 /**
  * Plugin load priority. Higher numbers win; ties resolve in
  * registration order. The highest-priority plugin is loaded by
@@ -75,4 +81,33 @@ priority?: number | null,
  * the per-column field set. When `false` or omitted, no StyleTab
  * is shown.
  */
-can_render_column_styles?: boolean, };
+can_render_column_styles?: boolean, 
+/**
+ * What `group_by` MEANS visually for this plugin, e.g. `"X Axis"`
+ * for the Y-series charts or `"Hierarchy"` for treemap/sunburst.
+ * `None` where the field has no visual role of its own and is a
+ * plain aggregation key (the X/Y charts, whose axes both come from
+ * `columns`).
+ *
+ * This is the `group_by` counterpart of [`Self::config_column_names`]:
+ * the same declaration that names the positional `columns` slots
+ * should say what the other view fields draw, so that consumers —
+ * the settings UI's field labels, and the agent's `list_plugins`
+ * contract — read one source instead of restating the mapping.
+ */
+group_by_role?: string | null, 
+/**
+ * What `split_by` MEANS visually for this plugin, e.g. `"Series"`.
+ * See [`Self::group_by_role`].
+ */
+split_by_role?: string | null, 
+/**
+ * `true` when this plugin CONNECTS its points in row order, so the
+ * `View`'s row order is visible in the drawing: an unsorted config
+ * renders the table's natural order, which reads as a tangle unless
+ * the rows already arrive ordered along the axis. Declared rather
+ * than inferred, because "unsorted" is not itself a mistake — a
+ * pre-ordered table needs no `sort`, and the point plugins
+ * (scatter, density) do not care at all.
+ */
+connects_row_order?: boolean, };

package/src/ts/ts-rs/RestoreOptions.ts

@@ -0,0 +1,20 @@
+// This file was generated by [ts-rs](https://github.com/Aleph-Alpha/ts-rs). Do not edit this file manually.
+
+/**
+ * Options for the `restore()` method.
+ */
+export type RestoreOptions = { 
+/**
+ * The target panel; the active panel when omitted.
+ */
+panel?: string, 
+/**
+ * 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 for subsequent calls. For programmatic
+ * callers (e.g. the LLM agent's `set_view_config` tool) for whom a
+ * failed config patch is feedback rather than a user-facing fault.
+ * The config may be partially applied on failure; restore a
+ * known-good config to recover exactly.
+ */
+suppress_errors?: boolean, };

package/src/ts/ts-rs/RoundingMode.ts

@@ -0,0 +1,3 @@
+// This file was generated by [ts-rs](https://github.com/Aleph-Alpha/ts-rs). Do not edit this file manually.
+
+export type RoundingMode = "ceil" | "floor" | "expand" | "trunc" | "halfCeil" | "halfFloor" | "halfExpand" | "halfTrunc" | "halfEven";

package/src/ts/ts-rs/RoundingPriority.ts

@@ -0,0 +1,3 @@
+// This file was generated by [ts-rs](https://github.com/Aleph-Alpha/ts-rs). Do not edit this file manually.
+
+export type RoundingPriority = "auto" | "morePrecision" | "lessPrecision";

package/src/ts/ts-rs/SignDisplay.ts

@@ -0,0 +1,3 @@
+// This file was generated by [ts-rs](https://github.com/Aleph-Alpha/ts-rs). Do not edit this file manually.
+
+export type SignDisplay = "auto" | "always" | "exceptZero" | "negative" | "never";

package/src/ts/ts-rs/SimpleDatetimeFormat.ts

@@ -0,0 +1,3 @@
+// This file was generated by [ts-rs](https://github.com/Aleph-Alpha/ts-rs). Do not edit this file manually.
+
+export type SimpleDatetimeFormat = "full" | "long" | "medium" | "short" | "disabled";

package/src/ts/ts-rs/SimpleDatetimeStyleConfig.ts

@@ -0,0 +1,25 @@
+// This file was generated by [ts-rs](https://github.com/Aleph-Alpha/ts-rs). Do not edit this file manually.
+import type { SimpleDatetimeFormat } from "./SimpleDatetimeFormat.js";
+
+/**
+ * A datetime column's `date_format` in its `Simple` preset form:
+ * `Intl.DateTimeFormatOptions`' `dateStyle`/`timeStyle` presets. This is
+ * the default form (no `format` key); setting `format: "custom"` selects
+ * the per-part `CustomDatetimeStyleConfig` instead.
+ */
+export type SimpleDatetimeStyleConfig = { 
+/**
+ * An IANA time zone name (e.g. `"America/New_York"`); defaults to the
+ * browser's local time zone.
+ */
+timeZone?: string | null, 
+/**
+ * Date preset breadth, or `"disabled"` to omit the date entirely;
+ * defaults to `"short"`.
+ */
+dateStyle?: SimpleDatetimeFormat, 
+/**
+ * Time preset breadth, or `"disabled"` to omit the time entirely;
+ * defaults to `"medium"`.
+ */
+timeStyle?: SimpleDatetimeFormat, };

package/src/ts/ts-rs/SplitRollupMode.ts

@@ -0,0 +1,11 @@
+// This file was generated by [ts-rs](https://github.com/Aleph-Alpha/ts-rs). Do not edit this file manually.
+
+/**
+ * The `split_by` corollary to [`GroupRollupMode`]. `Flat` (the default,
+ * matching this crate's historical behavior) emits only full-depth split
+ * combinations as columns; `Rollup` additionally emits grand-total and
+ * subtotal column groups in "totals before" order. There is no `Total`
+ * variant - an empty `split_by` already expresses a single grand-total
+ * column group.
+ */
+export type SplitRollupMode = "flat" | "rollup";

package/src/ts/ts-rs/StringColorMode.ts

@@ -0,0 +1,3 @@
+// This file was generated by [ts-rs](https://github.com/Aleph-Alpha/ts-rs). Do not edit this file manually.
+
+export type StringColorMode = "none" | "foreground" | "background" | "series";

package/src/ts/ts-rs/TrailingZeroDisplay.ts

@@ -0,0 +1,3 @@
+// This file was generated by [ts-rs](https://github.com/Aleph-Alpha/ts-rs). Do not edit this file manually.
+
+export type TrailingZeroDisplay = "auto" | "stripIfInteger";

package/src/ts/ts-rs/Unit.ts

@@ -0,0 +1,3 @@
+// This file was generated by [ts-rs](https://github.com/Aleph-Alpha/ts-rs). Do not edit this file manually.
+
+export type Unit = "acre" | "bit" | "byte" | "celsius" | "centimeter" | "day" | "degree" | "fahrenheit" | "fluid-ounce" | "foot" | "gallob" | "gigabit" | "gigabyte" | "gram" | "hectare" | "hour" | "inch" | "kilobit" | "kilobyte" | "kilogram" | "kilometer" | "liter" | "megabit" | "megabyte" | "meter" | "microsecond" | "mile" | "mile-scandinavian" | "milliliter" | "millimeter" | "millisecond" | "minute" | "month" | "nanosecond" | "ounce" | "percent" | "petabyte" | "pound" | "second" | "stone" | "terabit" | "terabyte" | "week" | "yard" | "year";

package/src/ts/ts-rs/UnitDisplay.ts

@@ -0,0 +1,3 @@
+// This file was generated by [ts-rs](https://github.com/Aleph-Alpha/ts-rs). Do not edit this file manually.
+
+export type UnitDisplay = "short" | "narrow" | "long";

package/src/ts/ts-rs/UnitNumberFormatStyle.ts

@@ -0,0 +1,5 @@
+// This file was generated by [ts-rs](https://github.com/Aleph-Alpha/ts-rs). Do not edit this file manually.
+import type { Unit } from "./Unit.js";
+import type { UnitDisplay } from "./UnitDisplay.js";
+
+export type UnitNumberFormatStyle = { unit: Unit, unitDisplay: UnitDisplay | null, };

package/src/ts/ts-rs/UseGrouping.ts

@@ -0,0 +1,3 @@
+// This file was generated by [ts-rs](https://github.com/Aleph-Alpha/ts-rs). Do not edit this file manually.
+
+export type UseGrouping = "always" | "auto" | "min2" | boolean;

package/src/ts/ts-rs/ViewerConfig.ts

@@ -5,6 +5,8 @@ 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";
 
 /**
@@ -15,4 +17,49 @@ import type { JsonValue } from "./serde_json/JsonValue.js";
  * state there, carried by the top-level `active` field instead), while the
  * single-panel format flattens back to the legacy shape.
  */
-export type ViewerConfig<V = string> = { settings: boolean, version: V, columns_config: { [key in string]?: { [key in string]?: JsonValue } }, plugin: string, plugin_config: { [key in string]?: JsonValue }, table: string | null, theme: string | null, title: string | null, group_by: Array<string>, split_by: Array<string>, sort: Array<Sort>, filter: Array<Filter>, group_rollup_mode: GroupRollupMode, filter_op?: FilterReducer, expressions: Expressions, columns: Array<string | null>, aggregates: { [key in string]?: Aggregate }, group_by_depth?: number | null, };
+export type ViewerConfig<V = string> = { settings: boolean, 
+/**
+ * The `@perspective-dev/viewer` version that wrote this config,
+ * stamped on save and used to migrate older tokens. Callers do not
+ * set it.
+ */
+version: V, 
+/**
+ * Per-column styling, keyed by column name. The viewer treats the
+ * values as opaque — their shape is defined by the ACTIVE plugin,
+ * so a config written for one plugin may carry keys another
+ * ignores. Query the live shape with the `get_style_schema` agent
+ * tool, or the plugin's `column_config_schema()`.
+ */
+columns_config: { [key in string]?: { [key in string]?: JsonValue } }, 
+/**
+ * Name of the visualization plugin, from the set registered on the
+ * page (the `list_plugins` agent tool, or the plugin picker). This
+ * also decides what the view fields MEAN visually: `columns` is
+ * positional and each plugin reads the positions differently, and
+ * `group_by`/`split_by` draw different things per plugin.
+ */
+plugin: string, 
+/**
+ * Plugin-wide settings (as opposed to the per-column
+ * [`Self::columns_config`]). Opaque to the viewer and defined by
+ * the active plugin; see `get_style_schema`.
+ */
+plugin_config: { [key in string]?: JsonValue }, 
+/**
+ * Name of the `Table` this panel renders, as hosted on the panel's
+ * `Client`. Every placed panel has a table binding (creation
+ * requires one by type — [`ViewerConfigInitial`]), so the saved
+ * config carries it unconditionally.
+ */
+table: string, 
+/**
+ * Selected theme NAME (e.g. `"Pro Dark"`) — not a CSS value. Valid
+ * names are the Perspective themes loaded on the page, which
+ * `resetThemes()` re-scans. `None` selects the first available.
+ */
+theme: string | null, 
+/**
+ * Panel title, shown in its tab. `None` renders the default title.
+ */
+title: string | null, group_by: Array<string>, split_by: Array<string>, sort: Array<Sort>, filter: Array<Filter>, group_rollup_mode: GroupRollupMode, split_rollup_mode: SplitRollupMode, filter_op?: FilterReducer, expressions: Expressions, windows?: Windows, columns: Array<string | null>, aggregates: { [key in string]?: Aggregate }, group_by_depth?: number | null, };

package/src/ts/ts-rs/ViewerConfigInitial.ts

@@ -0,0 +1,164 @@
+// This file was generated by [ts-rs](https://github.com/Aleph-Alpha/ts-rs). Do not edit this file manually.
+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/src/ts/ts-rs/ViewerConfigUpdate.ts

@@ -6,9 +6,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 = { version?: OptionalUpdate<string>, plugin?: OptionalUpdate<string>, title?: OptionalUpdate<string>, table?: OptionalUpdate<string>, theme?: OptionalUpdate<string>, settings?: OptionalUpdate<boolean>, plugin_config?: OptionalUpdate<{ [key in string]?: JsonValue }>, columns_config?: OptionalUpdate<{ [key in string]?: { [key in string]?: JsonValue } }>, 
+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 } }>, 
 /**
  * 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.
@@ -64,6 +122,12 @@ filter?: Array<Filter>,
  * 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>, 
 /**
@@ -74,6 +138,14 @@ sort?: Array<Sort>,
  * 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
@@ -86,5 +158,12 @@ expressions?: Expressions,
  * 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, };
+aggregates?: { [key in string]?: Aggregate }, group_by_depth?: number, filter_op?: FilterReducer, group_rollup_mode?: GroupRollupMode, split_rollup_mode?: SplitRollupMode, };

package/src/ts/ts-rs/WindowSort.ts

@@ -0,0 +1,9 @@
+// This file was generated by [ts-rs](https://github.com/Aleph-Alpha/ts-rs). Do not edit this file manually.
+import type { WindowSortDir } from "./WindowSortDir.js";
+
+/**
+ * The `Table` column which orders each partition, with its direction -
+ * serialized as a two-element array (`["ts", "desc"]`), symmetric with the
+ * `ViewConfig`'s `sort` field.
+ */
+export type WindowSort = [string, WindowSortDir];

package/src/ts/ts-rs/WindowSortDir.ts

@@ -0,0 +1,8 @@
+// This file was generated by [ts-rs](https://github.com/Aleph-Alpha/ts-rs). Do not edit this file manually.
+
+/**
+ * A window's order direction. A dedicated two-variant enum rather than
+ * [`crate::config::SortDir`] - the column-sort extras (`col asc`, `abs`,
+ * `none`) are meaningless inside a window frame and unrepresentable here.
+ */
+export type WindowSortDir = "asc" | "desc";

package/src/ts/ts-rs/WindowSpec.ts

@@ -0,0 +1,47 @@
+// This file was generated by [ts-rs](https://github.com/Aleph-Alpha/ts-rs). Do not edit this file manually.
+import type { WindowSort } from "./WindowSort.js";
+
+/**
+ * The serialized form of [`WindowSpec`].
+ */
+export type WindowSpec = { 
+/**
+ * The input column - either a real `Table` column or an expression
+ * alias from the same `ViewConfig`.
+ */
+column: string, aggregate: string, 
+/**
+ * Columns whose distinct value tuples partition the rows; empty
+ * partitions the whole `Table` as one group.
+ */
+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, 
+/**
+ * A frame of the `rows` preceding each row, plus the row itself.
+ * Mutually exclusive with `range` and `cumulative`.
+ */
+rows?: number | null, 
+/**
+ * A frame of the rows whose `order_by` value lies within `range` of
+ * each row's, requiring a numeric or temporal `order_by`. Mutually
+ * exclusive with `rows` and `cumulative`.
+ */
+range?: number | null, 
+/**
+ * `true` frames all rows from the partition start through each row.
+ * Default can be omitted.
+ */
+cumulative?: boolean | null, 
+/**
+ * Row offset for `lag`/`lead` (default 1).
+ */
+offset?: number | null, 
+/**
+ * Smoothing factor in `(0, 1]` for `ema`.
+ */
+alpha?: number | null, };

package/src/ts/ts-rs/Windows.ts

@@ -0,0 +1,10 @@
+// This file was generated by [ts-rs](https://github.com/Aleph-Alpha/ts-rs). Do not edit this file manually.
+import type { WindowSpec } from "./WindowSpec.js";
+
+/**
+ * The window columns of a `ViewConfig`, keyed by output column alias -
+ * symmetric with `expressions` (`{"name": {...spec}}`). An alias must not
+ * collide with a `Table` column, expression alias, or another window's
+ * key.
+ */
+export type Windows = { [key in string]?: WindowSpec };