@praxisui/list 9.0.14 → 9.0.16

package/README.md

@@ -86,24 +86,6 @@ Data mode resolution is deterministic:
 
 In remote mode, search, sort and export share a collection toolbar above the items; pagination remains attached to the collection footer. A configured `resourcePath` does not activate remote controls when local `data` is also present. The runtime uses `/filter` through `GenericCrudService.filter(query, pageable)`. Synchronous changes projected from one `queryContext` are coalesced into a single request. If that endpoint fails with an empty query, the compatibility path may fall back to `getAll()`. With active criteria, the list fails closed, preserves the filter context and exposes a read-only, retryable error stream instead of displaying unfiltered records.
 
-## Enterprise Collection Controls
-
-Treat the list as one collection surface with distinct control responsibilities:
-
-| Layer | Responsibility | Placement |
-| --- | --- | --- |
-| Structured filters | `praxis-filter` composes the existing inline controls from `@praxisui/dynamic-fields` and projects the resulting filter DTO into the list `queryContext`. | Before the list toolbar, in the same collection region. |
-| Collection toolbar | Quick search, authored sort choices and collection commands such as export. | Above the items. Search leads; sort and commands form the trailing command group. |
-| Item actions | Commands whose target is one record. | Inside the corresponding item action slot. |
-| Selection actions | Commands whose availability depends on `selectionChange`. | In a composed toolbar/action rail near the collection header, never inside the paginator. |
-| Pagination | Page size, range and page navigation only. | Attached to the collection footer. |
-
-Sorting is optional. Enable it when changing order helps users compare or prioritize a non-tabular collection; omit it when order is fixed by the workflow or only one meaningful order exists. Publish concise, business-readable `sortOptions` labels instead of exposing raw `field,direction` values. The Material select label is always “Sort by”/“Ordenar por”, so the control describes its purpose even before a value is chosen.
-
-Do not build a second filter library inside `@praxisui/list`. Structured filtering remains a composition of the canonical Praxis Filter container and Dynamic Fields inline controls. The list consumes the governed result through `queryContext`; it does not duplicate field discovery, draft/apply semantics or backend filter metadata.
-
-Local collections intentionally omit remote search and sort controls. Official local showcases therefore keep `ui.showSearch` and `ui.showSort` disabled and demonstrate the remote configuration separately.
-
 ## Main Inputs And Outputs
 
 - `config: PraxisListConfig`: list/card/tile configuration.
@@ -120,12 +102,10 @@ Local collections intentionally omit remote search and sort controls. Official l
 - Layout variants: `list`, `cards`, `tiles`.
 - Runtime-active layout fields include `lines`, `dividers`, `groupBy`, `pageSize`, `density` and `model`.
 - Templating slots include `leading`, `primary`, `secondary`, `meta`, `trailing`, `features`, `sectionHeader` and `emptyState`.
-- In `layout.rowLayout`, canonical semantic slots keep the configured desktop grid and reflow into ordered, non-overlapping rows at narrow viewports; extended operational slots stack without requiring host CSS.
 - Template expressions use `${item.field}`. Currency/date/number templates can use config i18n defaults.
 - Selection supports `none`, `single` and `multiple`, with return modes `value`, `item` or `id`.
 - Item actions can emit local events or delegate to `GlobalActionService`; collection export uses the shared `@praxisui/core` contract for `csv`, `json`, `excel`, `pdf` and `print`.
-- In `cards` and `tiles`, item activation and secondary item actions are separate keyboard targets. Hosts should preserve this composite interaction model instead of nesting action buttons inside the item activation surface.
-- A governed `actions[].recordOpen` resolves the identity declared by the backend against the current-principal resource and contextual surface catalogs before executing `surface.open`; it never derives the target from the displayed label or from `item.id`. This path requires the host's canonical `API_URL` configuration, resolved only when the action runs; local lists do not acquire a backend dependency merely by rendering the component.
+- A governed `actions[].recordOpen` resolves the identity declared by the backend against the current-principal resource and contextual surface catalogs before executing `surface.open`; it never derives the target from the displayed label or from `item.id`.
 
 ## Known Runtime Boundaries
 

package/ai/component-registry.json

@@ -1,8 +1,8 @@
 {
   "schemaVersion": "1.0.0",
-  "generatedAt": "2026-08-21T20:28:09.765Z",
+  "generatedAt": "2026-08-24T11:25:54.540Z",
   "packageName": "@praxisui/list",
-  "packageVersion": "9.0.14",
+  "packageVersion": "9.0.16",
   "sourceRegistry": "praxis-component-registry-ingestion",
   "sourceRegistryVersion": "1.0.0",
   "componentCount": 1,

package/docs/2026-08-collection-toolbar-runtime-note.md

@@ -17,16 +17,6 @@ This beta migration aligns the collection toolbar with the canonical data-mode p
 
 Search, sort and export share the upper collection surface. At narrow widths, sort occupies a full row and command controls wrap without overflowing the collection. Pagination remains a separate footer responsibility.
 
-## Collection anatomy
-
-- Structured filters remain upstream composition: `praxis-filter` hosts the existing Dynamic Fields inline controls and projects its DTO into `queryContext`.
-- Quick search, authored sort choices and export belong to the list-owned upper toolbar.
-- Item actions remain attached to their item. Selection-dependent bulk actions belong to a composed action rail near the collection header.
-- The paginator owns only page size, range and navigation; it does not host sort, filters or business actions.
-- Sort is optional and should be authored only when users benefit from changing the collection order. Labels must express business meaning instead of exposing raw transport syntax.
-
-This is an adoption clarification, not a new filter contract or package. The existing Praxis Filter and Dynamic Fields owners remain canonical for structured filtering and inline control behavior.
-
 ## Migration note
 
 Consumers that previously called `ListDataService.error$.next(...)` must stop mutating internal runtime state. Subscribe to `error$` and invoke `refresh()` for user-initiated recovery.