# @object-ui/types ## 14.0.0 ### Minor Changes - 86c69c3: ADR-0089: read the canonical `visibleWhen` conditional-visibility predicate in the form + page renderers. `@objectstack/spec` now unifies conditional visibility under a single canonical key, `visibleWhen`, and folds the deprecated `visibleOn` (view form) / `visibility` (page component) aliases into it at parse. This updates ObjectUI to read the canonical key: - **Page renderer** (`SchemaRenderer`) — evaluates `visibleWhen` first (show-when-truthy), then the deprecated `visibleOn` / `visibility` as a defensive read for raw / un-normalized metadata. `visibleWhen` is stripped from DOM props. - **Spec→node bridges** — the page bridge maps a component's `visibleWhen ?? visibility` onto the node's canonical `visibleWhen`; the form-view bridge maps a field's `visibleWhen ?? visibleOn` onto the ObjectForm view-level predicate slot. - **Form renderers** — the `@object-ui/react` `FormRenderer` prefers `visibleWhen` over the `visibleOn` alias. (`ObjectForm`/`form.tsx` already evaluated `visibleWhen`.) - **Types** — the component base schema (`BaseSchema` / `base.zod`) gains the canonical `visibleWhen`; `visibleOn` is marked `@deprecated`. Fully back-compat: existing `visibleOn` / `visibility` metadata keeps working through the alias reads. - 6a74160: Sharing-rule form: pick, don't type. Three new widget-hint field components make the generic object form render pickers where an admin previously had to type machine data (driven by the framework `widget` hints on `sys_sharing_rule`; generalizes the `capability-multiselect` pattern). All degrade to the underlying `type` renderer when a widget is unregistered. - **`object-ref`** — choose a registered object by name (searchable `Combobox`), backed by the new `DataSource.getObjects()` (`ObjectStackAdapter` lists code- and DB-defined objects via `/api/v1/meta/object`), falling back to a `sys_metadata` query. Stores the object's `name`. - **`filter-condition`** — a visual criteria builder (`FilterBuilder`) scoped to the fields of the object chosen in a sibling field (via `getObjectSchema`), round-tripping the stored **MongoDB-style** FilterCondition JSON. Criteria the builder can't represent (or invalid JSON) fall back to a raw-JSON editor, with an always-available "Edit as JSON" toggle — nothing is hidden or lost. - **`recipient-picker`** — a record picker whose target object follows a sibling `recipient_type` (`user`→sys_user, `team`→sys_team, `business_unit`/ `unit_and_subordinates`→sys_business_unit, `position`→sys_position), storing the value the evaluator matches on (a record id, or the position **name**). Resets the stored id when the type changes. Wiring: the three keys join `DATA_SOURCE_FIELD_TYPES` (form.tsx) so the form threads `dataSource` + `dependentValues` to them, and `INLINE_EXCLUDED_FIELD_TYPES` (they're authored in the record form, not a grid cell). `DataSource.getObjects()` is optional on the interface; the ObjectStack adapter implements it. ## 13.2.0 ## 13.1.0 ## 13.0.0 ### Patch Changes - 619097e: Adopt `@objectstack/spec` 13 (ADR-0090 Permission Model v2) across the workspace. Every workspace package now depends on `@objectstack/spec` ^13.0.0 — the v2 major that renames role → position (D3), removes the profile concept (D2), makes OWD default to `private` when unset (D1), and drops the legacy `read`/`read_write`/`full` sharing aliases (D4). UI fallout fixed in the same sweep: - **clientValidation**: the `role` draft-schema loader is now `position` → `PositionSchema` (fixes the `RoleSchema does not exist` build break, #2365); the dead `profile` loader is removed (D2). - **Studio previews**: `RolePreview` → `PositionPreview` (flat — positions carry no hierarchy; the old parent-chain breadcrumb and "assign to a Profile" copy are gone). Legacy `role`/`profile` preview keys stay registered for pre-v2 backends. - **OWD control** (`ObjectSettingsPanel`): removed the now-dead alias normalization (spec 13 rejects the aliases at authoring time) and the amber "fully public" warning — an unset sharing model now defaults to Private (D1), and the copy says so in both locales. - **Fallback schemas / anchors / samples**: `position` replaces the hierarchical `role` fallback schema; `isProfile` dropped from the permission create-anchor and previews samples; permission-set viewer no longer renders a profile badge; console System hub counts `sys_position` instead of the removed `sys_role`. - **Studio i18n**: type labels `Role/角色` → `Position/岗位`, `profile` label removed, Access-pillar heading and sharing copy rewritten to the v2 vocabulary. - `@object-ui/types` now exports `SubmitBehavior` (was defined but missing from the public surface, breaking `@object-ui/plugin-form`'s re-export under a clean build). - **External OWD dial (D11)**: the object Settings sharing card gains an `externalSharingModel` select (portal/partner baseline) with an inline wider-than-internal warning mirroring the publish-time lint. - **Permission matrix OWD badges**: every object row now shows its record-level baseline (`OWD Public read`, `Ext Private`, or `OWD Private (default)` for the D1 fail-closed unset case) so grant edits carry their record-reach context. The flow designer's approval assignee `role` kind is intentionally unchanged — spec 13 keeps it as the sole D3 exception (better-auth `sys_member.role` org-membership tier). ## 12.1.0 ### Minor Changes - c31874d: Record-header actions honour `Action.order`, so approval decisions no longer get buried in the `⋯` overflow menu (objectui#2339 / framework#2670). The `action:bar` renderer now stable-sorts its actions by an explicit **`order`** field (lower = higher / more prominent, default `0`) before the inline/overflow split. The sort is stable and treats unset `order` as `0`, so action groups where nobody sets `order` keep their exact registration order — existing toolbars are unaffected. `order` is added to `ActionSchema` in `@object-ui/types`, mirroring `Action.order` in `@objectstack/spec`. `RecordDetailView` now assigns the injected **Approve / Reject** decision buttons a strongly-negative `order` (and gives Approve the highlighted `primary` variant), so on a pending-approval record the approver's decision takes the primary-button slot and app `record_header` actions follow it — instead of the app having to hide its own actions to surface the decision. ## 12.0.0 ### Minor Changes - 226fde9: Cascading & role-gated `select` options (#2284). `select` options now accept a per-option `visibleWhen` CEL predicate — the option is offered only when it evaluates TRUE against the live record **plus `current_user`** (same engine/env as a field-level `visibleWhen`). Combined with a field-level `dependsOn`, this drives dependent selects (country → province → city) and role/context gating with no bespoke matrix — the same primitives dependent lookups (#2215) already use. - `@object-ui/core` exposes `resolveVisibleOptions` / `isOptionGroupGated` / `resolveDependsOnFields` / `isValueStillOffered` (evaluator), reusing the canonical `evalFieldPredicate`. - The form renderer narrows a dependent select's option list, gates the control with a "Select {parent} first" hint while a `dependsOn` field is empty, and clears a now-invalid value when the parent changes. - The standalone `SelectField` widget applies the same resolution via `dependentValues` + the global predicate scope. Client-side hiding is UX, not authorization: gate authorization-sensitive option values on the server too. Aligns with `@objectstack/spec` `SelectOption.visibleWhen`. - e4de456: Fix form section grouping inconsistencies found in a UX review of grouped forms: - **Unified section visual language.** `FormSection`'s Card-wrapped path (used by Modal/Split/Tabbed/Wizard forms) previously rendered as a nearly-invisible white-on-white card (same `bg-card` as the page background, distinguished only by a barely-visible shadow) with a duplicated, inconsistent header (different title size, and a collapse chevron positioned differently) versus the flat `SectionDivider` path used by simple/drawer forms. Both now share the same header treatment (`text-sm font-semibold`, inline-left chevron, bottom border), and the Card path gets a soft `bg-muted/40` tint so grouped sections are visually distinguishable without relying on shadow alone. - **`readonly` no longer renders as `disabled`.** A field marked `readonly` (statically or via `readonlyWhen`) was being folded into the `disabled` prop before reaching field widgets, so widgets with a dedicated readonly display (e.g. `EmailField`'s mailto link, `TextField`'s plain-text view) never received it — every readonly field just looked permanently disabled. `readonly` is now forwarded as its own prop; generic `input`/`textarea` fields get a distinct readonly style (`bg-muted/40`, no `cursor-not-allowed`) instead of the disabled look. - **Section `className`/`gridClassName` now flow through JSON schemas.** `ObjectFormSection` and the per-form-variant section configs (`ModalFormSectionConfig`, `SplitFormSectionConfig`, `FormSectionConfig`, `DrawerFormSectionConfig`) accept `className` (and `gridClassName` where applicable), wired through `ObjectForm`'s form-type dispatch into `FormSection`/`SectionDivider` — closing a gap where section wrappers couldn't be customized from schema despite `FormSection` itself already supporting it. ## 11.5.0 ### Minor Changes - 1072701: Import wizard: use registered server-side import mappings (framework #2611). When an object has `mapping` metadata artifacts targeting it, the wizard shows a "Saved mapping" selector; picking one hands rename + transforms + write semantics to the server (the artifact is authoritative), replaces the manual column table with a read-only summary of the mapping, and submits `mappingName` over source-header rows (mutually exclusive with the inline column rename). `ImportRequestOptions` gains `mappingName`; the objectstack adapter gains `listImportMappings(objectName)` (feature-detected — the selector simply doesn't appear when unsupported). New `grid.import.*` strings added across all locales. ### Patch Changes - 9255686: Record detail tabs are URL-addressable (`?tab=`) and survive subtree remounts (objectui#2257, ADR-0054 C3). - `buildDefaultTabs` emits STABLE semantic tab values (`details` / `related:` / `related` / `activity` / `history`) instead of leaving the renderer to synthesize index-derived ones. - `PageTabsRenderer` honors `item.value`, a host-provided `schema.defaultTab` (validated against actual tabs) and `schema.onTabChange`; index fallback kept for authored schemas without values. - app-shell `RecordDetailView` restores the active tab from `?tab=` and writes it back with `replace` (tab switches never stack history), via the pure `withPageTabsUrlSync` page-tree injector (never mutates authored/memoized page schemas). Legacy `DetailView.autoTabs` wired to the same contract (`defaultTab`/`onTabChange`). - Fixes the tab strip resetting to Details after save-refresh remounts (`refreshKey`-style) and dev-StrictMode URL churn; enables `?tab=` deep links; invalid values fall back to Details. ## 11.4.0 ### Minor Changes - 8bf6295: feat: adaptive record surface + semantic field span + responsive columns (framework#2578) Field-heavy objects (all metadata is AI-authored) now present themselves without any authored presentation config: - **Adaptive surface** — a record's create/edit/detail opens as a full page when the object is field-heavy, or a drawer when it is light. Derived from field count (`deriveRecordSurface`), not authored; mobile always pages. Wired into the app-shell ObjectView detail navigation (an authored view/object `navigation` still wins). - **Semantic field span** — `FormField.span` (`auto`/`full`) is a width primitive decoupled from the (per-surface derived) column count; legacy `colSpan` is clamped so it never overflows. `ObjectForm` now honours per-section `columns` and carries `span`/`colSpan` from section defs — fixes the bug where `type:'simple'` ignored `section.columns` and grouped fields rendered single column. - **Responsive columns** — `inferColumns` scales the column CAP with field count (≤3→1, ≤8→2, ≤15→3, 16+→4); the ACTUAL column count follows the form's real width via CSS container queries, so the same form goes 1→2→3→4 columns as a drawer widens or becomes a page. - **Runtime overlay width** — `NavigationConfig.size` bucket is resolved to a viewport-clamped width at runtime (`overlayWidthFor`); a pixel width is never authored (the author cannot know the client viewport). ### Patch Changes - 1948c5b: fix(plugin-grid): keep the grid's row selection in sync when a bulk-action dialog closes Closing a bulk-action result dialog (e.g. 派工 / 下推) on **Done** cleared ObjectGrid's `selectedRows` — which drives the selection toolbar — but never touched the DataTable's internal checkbox state. Two visible problems: - **Desync on success.** The toolbar disappeared while every row stayed visibly ticked, because the checkboxes are table-internal state the grid couldn't reach. - **Lost selection on total failure.** When the run failed for _every_ row (0 succeeded — a precondition error, say), the toolbar still vanished, stranding the user with no way to retry the exact rows they'd picked. The dialog-close handler now gates the reset on `result.succeeded > 0`: a total failure keeps both the selection _and_ the toolbar (and skips the phantom refetch) so the user can fix the cause and retry. When it does reset, a new `selectionResetKey` prop on DataTable clears the internal checkbox selection in lockstep with the toolbar, so the two never drift apart. - c38d107: Fix view-level `FormField.visibleOn` (CEL) never taking effect (#2212). The spec ships `visibleOn` as an Expression object `{ dialect: 'cel', source }` (what the `P` template emits) or a bare string, but the whole chain dropped it: - `sectionFields.ts` / `ObjectForm.tsx` only accepted the bare-string shape and attached a dead `visible()` closure no renderer ever called — the Expression object shape was silently discarded. - The form renderer destructured `visibleOn` out of the field config and never evaluated it. - `RecordFormPage` dropped a `simple` form view's `sections` entirely, so page-mode create/edit fell back to the raw schema (every field, no authored selection/grouping) while the modal path honored the same view. - `ObjectForm`'s grouped-sections path matched section fields by name only, dropping per-field `visibleOn` overrides. `visibleOn` now flows through normalization verbatim (both wire shapes) and is evaluated reactively by the form renderer with the canonical expression engine (`evalFieldPredicate` — same engine, record scope, and fail-open semantics as field-level `visibleWhen`; both predicates must allow a field for it to show). Sectioned/flat normalization also copies field-level `visibleWhen` / `readonlyWhen` / `requiredWhen` rules it previously lost. ## 11.3.0 ## 11.2.0 ## 11.1.0 ## 7.3.0 ## 7.2.0 ### Minor Changes - d23db5c: feat(detail): related-list add-by-picker (generic m2m/junction) + a generic "Assigned Users" management UI on permission sets (assign ai_seat and any role with zero bespoke CRUD; server-side cap errors surface inline). ## 7.1.0 ### Minor Changes - 677f7ed: feat(charts,dashboard): data-screen customization primitives - object-metric `variant:'bare'` — big tinted number + label, no card chrome (data-screen KPIs that stay data-bound). - object-chart `colors` prop overrides the theme `--chart-1..n` palette so a page/dashboard can brand its charts; compact metric formatting (`'0.0a'` → "1.1M"). - ObjectChartSchema.chartType widened to donut/horizontal-bar/column. - a71be60: chore: drop the unrendered `blank` / `record_review` page types and their config The `blank` and `record_review` page types have no renderer and were removed from `@objectstack/spec`'s `PageTypeSchema` (framework#2265, enforce-or-remove). This drops their now-dead references in objectui so the upstream spec can hard- remove `BlankPageLayoutSchema` / `RecordReviewConfigSchema`: - `PageType` union: removed `dashboard` / `form` / `record_detail` / `record_review` / `overview` / `blank` (grid/gallery/kanban/calendar/timeline remain — those are list _visualizations_, a separate cleanup). - Removed `blankLayout` from `PageLayout` and the `blankLayout` / `recordReview` handling in the spec→SDUI page bridge. - Removed the redundant `BlankPageLayout{,Schema,Item,ItemSchema}` re-import from `@objectstack/spec/ui` (it was never used). ### Patch Changes - cb03bc3: feat(types): type `object-chart` `colors` as a palette OR a value→color map `ObjectChartSchema.colors` now accepts either a positional palette (`string[]`) or an explicit value→color map (`Record`, kanban-style). This matches the chart renderer, which resolves a select/lookup dimension's option colors per category and lets them (and any explicit map) win over the positional palette — so health green/red/yellow paints semantically. ## 7.0.0 ### Major Changes - 858ad94: **Breaking:** remove `@object-ui/plugin-workflow` and its schema types. The package's designers (`WorkflowDesigner`, `FlowDesigner`, `AutomationBuilder`, `ApprovalProcess`, `AutomationRunHistory`) authored BPMN-style / standalone-workflow shapes the ObjectStack automation engine does not execute (ADR-0020, ADR-0031), and nothing in the console, runner, or examples consumed them. Removed from `@object-ui/types`: `WorkflowSchema`, `WorkflowDesignerSchema`, `ApprovalProcessSchema`, `WorkflowInstanceSchema`, `FlowDesignerSchema` and the related `Workflow*` / `Flow*` helper types (formerly `./workflow`). **Migration:** author flows in the Studio's metadata-admin flow designer (`@object-ui/app-shell` → `FlowCanvas`), whose node palette is driven by the engine's published action registry (`GET /api/v1/automation/actions`). Run history is available in the same view via the Runs panel; approval UI ships with the framework's `plugin-approvals`. ### Minor Changes - ddbe4a2: B2 step 3: client-side field-level conditional rules (`visibleWhen` / `readonlyWhen` / `requiredWhen`). The form renderer now evaluates these CEL predicates reactively against the live record and gates each field's visibility, read-only state, and required-ness accordingly. Evaluation delegates to the canonical `@objectstack/formula` `ExpressionEngine` — the _same_ dialect the server enforces (`requiredWhen` in the rule-validator, `readonlyWhen` in `stripReadonlyWhenFields`) — so the UX and the persisted verdict always agree. New core helpers `evalFieldPredicate` / `resolveFieldRuleState` (zero-React, fail-open). `FormField` gains `visibleWhen` / `readonlyWhen` / `requiredWhen` (+ deprecated `conditionalRequired` alias), and `ObjectForm` carries them through from object metadata. - 9049bbe: Add end-user friendly agent process summaries for chatbot tool calls, with a debug mode for raw reasoning and tool details. Console chat surfaces now keep a sanitized browser-side display cache so refreshes can restore user/assistant text plus grouped tool states when the backend returns no message rows. - d16566f: Atomic master-detail create via the cross-object transactional batch endpoint (ObjectStack #1604). When the server exposes the transactional batch endpoint, a NEW parent record and its child line items are now persisted in ONE server transaction — commit all or roll back all — instead of the previous client-orchestrated "create parent → create children → best-effort cleanup on failure" sequence. **`@object-ui/data-objectstack` — `ObjectStackAdapter.batchTransaction(operations)`** - New method posting `{ operations }` to `POST /api/v1/batch`. Operations run in one server transaction. A field value of `{ $ref: }` resolves to that op's generated id, so a child can reference its parent created earlier in the same batch (master-detail FK). Throws `ObjectStackError('BATCH_ERROR')` on a non-2xx response. **`@object-ui/plugin-form`** - `MasterDetailForm` now detects `dataSource.batchTransaction` and, on a NEW parent, builds one atomic batch (parent at index 0, each child FK set to `{ $ref: 0 }`) via the new pure helper `buildMasterDetailBatch`. Client-side total rollups are merged into the parent payload before the batch. Edit mode and adapters without `batchTransaction` keep the existing client-orchestrated path. - `ObjectForm` gained a `submitHandler` hook: when supplied, the form validates and hands the collected values to the host instead of calling `dataSource.create` / `dataSource.update`. `MasterDetailForm` uses it to own the atomic parent+children write while the parent fields are still rendered by `ObjectForm`. **`@object-ui/types`** - `ObjectFormSchema.submitHandler?: (values) => any | Promise` — typed override for host-owned persistence. Pairs with the framework-side ambient-transaction fix (ObjectQL `AsyncLocalStorage` transaction propagation) and the `/api/v1/batch` endpoint added in `@objectstack/rest`. - 300d755: feat(form): inline master-detail in a plain ObjectForm via `subforms` `ObjectFormSchema` gains a `subforms` array. When set, a regular `object-form` renders as a master-detail form — the object's own fields on top, an editable grid per child collection below, persisted together in one atomic transaction — without a bespoke `object-master-detail-form` page. ```ts { type: 'object-form', objectName: 'expense_claim', subforms: [{ childObject: 'expense_line' }] } // FK + columns auto-derived ``` Each subform needs only `childObject` (relationship FK and columns are derived from the child object's metadata; override with `relationshipField`/`columns`). This is the config-driven, page-less way to express master-detail entry — a form view can declare its child collections directly. - 4eb9cb6: feat(plugin-tree): add a `tree` / tree-grid object view type Renders a self-referencing object as an indented, expand/collapse tree-grid — the right view for arbitrary-depth hierarchies (business unit / org chart, category trees, BOMs, nested comments) that fixed-depth grouping can't express. New `@object-ui/plugin-tree` package (`object-tree`/`tree`), `tree` added to the `ViewType` union, and dispatch wired through plugin-list `ListView` + app-shell `ObjectView` (the console path). ### Patch Changes - cb2fdb1: feat(dashboard): expand drill-in — table/list row→record + scatter/treemap/sankey drill-through Drill-in now covers the widgets that were missing it, and formalizes the two interaction semantics mainstream BI/low-code platforms separate. `DrillDownConfig` gains a `mode` discriminator: `'filter'` (drill-through: aggregate bucket → filtered record list) and `'record'` (drill-to-record: a table/list row → that record's detail). - Scatter, treemap and sankey charts now wire click → the existing filtered-record drill drawer (radar excluded — no single clickable category point). The Recharts-payload → drill-event mapping is extracted to pure, tested functions. - Object-backed table/list widgets drill to the clicked record in a read-only detail drawer (Sheet/Dialog), on by default (`drillDown:{enabled:false}` opts out). Field labels and value formatting (incl. tenant-default currency) are shared with the table cells so a value reads identically in both. An author-supplied `onRowClick` still wins. - The chart/KPI drill-through record lists now drill into a record too, completing the segment → list → record chain. - 6cfa330: feat(dashboard): drill "Open in list" escape hatch + unify report drill Adopts the mainstream BI peek-then-escalate drill model. Drill-through opens an in-place drawer (keep context) and offers an "Open in list →" affordance to escalate to the object's full list page (sort / bulk-select / export / shareable URL) — the Looker / Power BI "see records → open in page" pattern. - New `DrillNavigationContext` (`@object-ui/react`): the app shell provides `openRecordList`; the renderer stays decoupled from console routing. - The drill drawers (pivot / dataset / chart / KPI) render the escape hatch when a host navigation handler is present, and hide it otherwise (self-contained peek). `DashboardView` provides the handler via `useOpenRecordList`. - `DrillDownConfig.target` gains `'navigate'` — skip the drawer and open the list directly; degrades to `'drawer'` when no host handler is available. - `ReportView` drill-through now opens the same in-place drawer (peek records → click a row to open a record) instead of navigating away; the escape hatch preserves the previous navigate-to-list behavior. Dashboard and report drill are now unified. - i18n: `dashboard.openInList` (en / zh). - ad8ade6: feat(components): metadata-derived field locators on generated forms (ADR-0054 Phase 4) The form renderer now emits a stable `data-testid="field:{objectName}.{field}"` (plus `data-field`) on every field wrapper, derived from the form's `objectName` and each field's name — closing the locator gap at the source so every generated form (`ObjectForm`/`ModalForm`/`DrawerForm`/`SplitForm`/`WizardForm`) inherits testable fields with zero per-app work (ADR-0054 C4). `FormSchema` gains an optional `objectName`; the object prefix is omitted (`field:{field}`) when a form has none. `FormItem` now accepts `data-*` attributes. - 3870c20: feat(forms): declarative `navigateOnSuccess` + `resetOnSuccess` on object-form Rounds out declarative success behavior for metadata-only forms (which can't pass an `onSuccess` function), complementing `successMessage`: - **`navigateOnSuccess`** — after a successful create/update, navigate here. Supports `{id}`/`{recordId}` interpolation from the saved record and is same-origin-guarded; takes precedence over the toast (landing on the record is the confirmation). - **`resetOnSuccess`** — after a successful create, reset the form for another entry (the wizard returns to a cleared step 1). Ignored when navigating. Wired in both ObjectForm and WizardForm via a small shared `successBehavior` helper (kept dependency-free to avoid an EmbeddableForm import cycle). - b88c560: feat(forms): declarative `successMessage` on object-form Metadata-only forms (a wizard/object-form authored as JSON) cannot pass an `onSuccess` function, so the post-create/update feedback was a fixed "Created"/"Saved" toast. `ObjectFormSchema` now accepts `successMessage`, which ObjectForm and WizardForm use for the default success toast when no `onSuccess` handler is supplied. Falls back to "Created"/"Saved". ## 6.2.3 ## 6.2.2 ## 6.2.1 ## 6.2.0 ## 6.1.0 ### Minor Changes - 991b62d: Add `compareTo` field to dashboard widgets for period-over-period comparison. Supports `'previousPeriod'`, `'previousYear'`, and `{ offset: '7d' | '4w' | '1M' | '1y' }`. - **Metric / gauge widgets** now compute a delta percentage when `compareTo` is set and surface it as a derived `trend` (auto-labelled via `dashboard.trend.vsLast*` i18n keys sniffed from the filter macros). - **Chart widgets** (line / area / bar / horizontal-bar / scatter / combo) overlay a muted comparison-period series (dashed line, lower fill opacity). Pie / donut / funnel ignore `compareTo`. - New core utilities: `shiftFilterByCompareTo`, `compareToTrendLabelKey`, `computeMetricDelta`, and `CompareToConfig` type. - `ChartSeries` now accepts `variant: 'comparison'`, `dashArray`, and `opacity` overrides for visual treatment. See `packages/plugin-dashboard/SKILL.md` for usage examples. ## 6.0.4 ## 6.0.3 ## 6.0.2 ## 6.0.1 ## 6.0.0 ## 5.4.2 ## 5.4.1 ## 5.4.0 ### Minor Changes - 3a8c754: Rebuilt the chatbot UI on top of **Vercel AI Elements** (MIT) and wired in the v1 capabilities exposed by `@objectstack/service-ai` (tracing, `generateObject`, `query_data` tool, `ModelRegistry`). - **What's new** - `ChatbotEnhanced` is now composed from `Conversation`, `Message`, `PromptInput`, `Suggestion`, `Tool`, `Reasoning`, `Sources`, and friends. Sticky-to-bottom scrolling, keyboard-aware textarea, file pill chips, copy/retry actions, and the streaming/error banners now match the shadcn-style AI surface used across the ecosystem. - **Tool / reasoning / sources rendering**: assistant messages with `toolInvocations`, `reasoning`, or `sources` automatically render the collapsible tool panels, the chain-of-thought block, and the citation pill. `useObjectChat` parses these directly from `vercel/ai`'s `UIMessage.parts` stream — no extra wiring needed at the call site. - **Model picker**: optional `models` + `selectedModelId` + `onModelChange` props render an inline `