@praxisui/table 9.0.0-beta.9 → 9.0.0-beta.90

package/docs/column-resize-reorder-implementation-plan.md

@@ -7,7 +7,7 @@ Allow users to resize and move columns in `praxis-table` without conflicting wit
 ## Guiding Principles
 
 - `sort` belongs to a dedicated sortable label/container, not to the entire `th`
-- `reorder` belongs to a dedicated drag handle
+- `reorder` belongs to the draggable header cell, without a permanent move icon
 - `resize` belongs to a dedicated handle on the right edge of the header cell
 - runtime mutations should reuse the existing persistence pipeline through a shared column-mutation coordinator
 - width persistence should normalize to `px`
@@ -33,15 +33,17 @@ This is the main reason resize must not be introduced as another gesture on the
 
 Additional constraints from the current implementation:
 
-- reorder keyboard parity is attached to the `th`, not to a standalone handle
-- reorder aria-label and tooltip are currently attached to the `th`
+- reorder keyboard parity is attached to the dedicated header sort trigger through Ctrl/Alt + arrows
+- runtime reorder does not render a visible move icon/handle, matching SAP Fiori and MUI Data Grid patterns
 - persistence currently saves the full `config` snapshot for each runtime mutation
 - width styling may already come from `column.width`, `headerStyle`, or `style`
 
 Current reorder affordance note:
 
-- the drag handle is rendered before the header text in draggable headers so the grip appears first visually without changing the current `cdkDrag` root on the `th`
-- this is a visual/layout choice only in the current implementation slice; the handle is still non-interactive and the full draggable header remains the active drag target
+- reorder is implicit on the draggable header cell, matching enterprise grids such as SAP Fiori and MUI Data Grid
+- the current `cdkDrag` root remains on the `th` so preview, placeholder sizing, and index semantics stay stable
+- `mat-sort-header` is mounted on `.praxis-header-sort-trigger`, not on the full `th`, so sort remains a focused label interaction while header drag remains available
+- keyboard reorder belongs to the focused header sort trigger via Ctrl/Alt + arrow keys
 
 The plan must explicitly unwind those couplings instead of treating them as incidental details.
 
@@ -52,37 +54,32 @@ The plan must explicitly unwind those couplings instead of treating them as inci
 Refactor the header so each interaction has an explicit zone:
 
 - sortable label container: sort
-- drag icon/handle: reorder
+- draggable header cell: reorder, with no permanent move icon
 - right-edge handle: resize
 
 Changes in `praxis-table.html`:
 
 - keep `.praxis-header-label-text`
-- keep the drag handle rendered before the label text while the current reorder UX still relies on the full `th` as drag root
-- add a sortable wrapper such as `.praxis-header-sort-trigger`
-- keep `.praxis-column-drag-handle`
-- add `.praxis-column-resize-handle`
+- add a sortable wrapper `.praxis-header-sort-trigger`
 - keep `cdkDrag` on the `th`
-- add `cdkDragHandle` to the reorder handle so the existing drag root, preview, placeholder sizing, and index semantics stay intact
-- move reorder `aria-label`, tooltip, and keyboard listeners from the `th` to the reorder handle
-- ensure the resize handle and reorder handle both stop `click`, `pointerdown`, and keyboard bubbling into the sort trigger
+- do not render a visible reorder icon/handle in the runtime header
+- add `.praxis-column-resize-handle`
+- keep keyboard reorder on the header sort trigger without blocking sort Enter/Space behavior
+- ensure the resize handle stops `click`, `pointerdown`, and keyboard bubbling into the sort trigger
 
 Changes in `praxis-table.scss`:
 
 - make the sortable label container the only area that shows sort cursor/hover treatment
-- keep drag handle aligned next to the label text
 - add resize handle positioned at the far right edge
-- use `cursor: grab` for reorder
 - use `cursor: col-resize` for resize
 - use a hit area around `8px` to `12px` for resize
-- remove `pointer-events: none` from the drag handle and make it a real interactive control
 
 Sorting strategy:
 
 - do not keep the full `th` as the primary sort interaction target
 - move the sort trigger to the label/container inside the header cell
 - preserve keyboard sort semantics on that dedicated sort target
-- treat suppression of `click` on reorder/resize handles as a hard requirement, not a best-effort safeguard
+- treat suppression of `click` on resize handles as a hard requirement, not a best-effort safeguard
 
 ### Phase 2: Add Runtime Resize State
 
@@ -125,7 +122,7 @@ On resize start:
 
 Behavioral rule:
 
-- dragging only starts from the reorder handle
+- dragging starts from the header cell, except the resize handle and sortable label interactions
 - sorting only starts from the dedicated sortable label/container
 - resizing only starts from the right-edge resize handle
 
@@ -151,6 +148,12 @@ Width rules:
 - if `column.width` is already in `px`, use it directly
 - if width is `%`, `auto`, or empty, measure the current header width at first resize and convert to `px`
 - persist resized widths as `px`
+- resizing changes the internal table content width, not the host/card/viewport width
+- when the summed column widths exceed the viewport, the scroll container owns horizontal overflow
+- when the summed column widths are smaller than the viewport, empty space may remain after the last column instead of redistributing widths implicitly
+- do not resize neighboring columns in `px` mode; the resized column changes and following columns move accordingly
+- when resize is enabled, persisted `px` widths below the effective readable minimum are normalized back into `config.columns[]`, not only corrected during rendering
+- the effective readable minimum includes the column header text, the resize separator gutter, and the sort gutter only when that concrete column is sortable
 - explicitly define precedence when `headerStyle` or `style` also carry width declarations
 - document that first user resize converts responsive width intent into fixed runtime width intent
 - validate width behavior under sticky start/end columns and horizontal scroll mode
@@ -186,9 +189,10 @@ Resize persistence policy:
 
 - persist on commit only, not continuously during pointer move
 - commit point is `pointerup` for pointer interactions
-- keyboard resize is not part of the first delivery slice
-- when keyboard resize is added later, commit semantics must be explicit (`Enter`, `blur`, or stepwise save), not implied
+- keyboard resize commits stepwise on each handled key event
+- keyboard resize uses `ArrowLeft`, `ArrowRight`, `Shift + Arrow`, `Home`, and `End`
 - define stale-callback protection for resize and reorder through the same shared coordinator
+- derived table width used during/after resize must be cleared when the visible column contract changes externally
 - do not add undo in the first slice unless a concrete UX requirement appears, but keep the runtime contract compatible with future undo support
 
 Emit a resize event after persistence:
@@ -240,16 +244,18 @@ Resize handle:
 
 Keyboard behavior for resize handle:
 
-- defer keyboard resize to a follow-up slice after pointer behavior and persistence are stable
-- when implemented, define `ArrowLeft`, `ArrowRight`, `Shift + Arrow`, `Home`, `End`, and `Escape`
-- define exactly when the resize is committed and when it is cancelled
+- `ArrowLeft` and `ArrowRight` resize by the default step
+- `Shift + ArrowLeft` and `Shift + ArrowRight` resize by the larger step
+- `Home` applies the configured minimum width
+- `End` applies the configured maximum width when one is configured
+- `Escape` cancels an active pointer resize before commit
+- keyboard resize commits stepwise on each handled key event
 
-Reorder handle:
+Reorder accessibility:
 
-- make the reorder handle a real focusable control
-- move existing Alt/Ctrl+Arrow reorder behavior onto the handle
-- move existing reorder aria-label and tooltip onto the handle
-- preserve visible focus styling and screen-reader parity after removing those affordances from the `th`
+- keep keyboard reorder on the focused header sort trigger with Alt/Ctrl + arrow keys
+- do not add a permanent focusable move icon unless a future accessibility review proves the header-trigger model insufficient
+- preserve visible focus styling and screen-reader parity on the header label/sort trigger
 
 ### Phase 8: Testing
 
@@ -260,7 +266,7 @@ Add focused tests for interaction conflicts:
 - resize handle click does not bubble into sort click
 - reorder does not alter width
 - clicking the sortable label still sorts
-- reorder still works through the dedicated `cdkDragHandle`
+- reorder still works through the draggable header cell
 - keyboard reorder still works after moving intent to the handle
 - sort keyboard interaction still works after sort leaves the `th`
 
@@ -300,18 +306,18 @@ Add visual/e2e coverage later:
 ## Recommended Delivery Sequence
 
 1. Refactor header structure so sort is isolated to a dedicated sortable label/container
-2. Move reorder affordance, keyboard handling, aria-label, and tooltip to a real drag handle
-3. Add resize handle with runtime-only pointer support and explicit cancel paths
-4. Validate sticky and horizontal-scroll behavior in the same slice
+2. Keep reorder implicit on the header and remove stale move-icon guidance from docs/editor copy
+3. Add resize handle with pointer support, keyboard support, and explicit cancel paths
+4. Validate sticky and horizontal-scroll behavior in a follow-up hardening slice
 5. Introduce shared column runtime mutation coordination for reorder + resize persistence
 6. Persist column width on commit only
 7. Add focused conflict and persistence tests
-8. Add keyboard resize and final resize a11y semantics in a follow-up slice
+8. Add broader sticky, horizontal-scroll, and non-data-column E2E coverage
 9. Enable only through config/feature flag
 
 ## Definition of Done
 
-- users can reorder only from the drag handle
+- users can reorder from the header without a permanent move icon
 - users can resize only from the right-edge handle
 - clicking the sortable label still sorts
 - reorder, resize, and sort do not interfere with each other
@@ -326,6 +332,8 @@ Add visual/e2e coverage later:
 - first resize may intentionally convert responsive width behavior into fixed pixel width behavior
 - sticky start/end columns and horizontal scroll are immediate implementation concerns
 - resize and reorder mutations need a shared commit/stale-callback policy, not parallel ad hoc logic
+- table-level width is runtime-derived state; it must not outlive the column contract that produced it
+- the canonical enterprise default follows the SAP/MUI model for fixed-width columns: resize the column and the internal content width, keep the outer viewport stable, and use horizontal overflow when needed
 
 ## Suggested Follow-Up
 

package/docs/local-data-support-implementation-plan.md

@@ -466,24 +466,24 @@ Todos os itens abaixo devem estar `true`:
 14. Revalidacao complementar do wrapper CRUD apos o hardening:
    - `ng test praxis-crud --watch=false --browsers=ChromeHeadless --polyfills=zone.js --polyfills=zone.js/testing`;
    - `TOTAL: 30 SUCCESS`.
-15. Validacao da lane dedicada no WSL:
+15. Validacao da lane dedicada:
    - `bash ./scripts/test-table-preimpl-lane.sh`: bloqueada por infraestrutura (`No usable Chromium binary found for headless capture`).
    - fallback operacional via Windows Chrome com os mesmos includes da lane:
      `ng test praxis-table --watch=false --browsers=ChromeHeadless --polyfills=zone.js --polyfills=zone.js/testing --include ...`;
    - resultado do fallback: `TOTAL: 48 SUCCESS`.
-16. Mitigacao operacional no WSL validada sem alterar o script da lane:
+16. Mitigacao operacional validada sem alterar o script da lane:
    - wrapper: `tools/karma/chromium-bin-wrapper.sh` (contorna apenas probe `--dump-dom`);
    - execucao:
      `CHROMIUM_REAL_BIN=<puppeteer-executablePath> CHROMIUM_BIN=tools/karma/chromium-bin-wrapper.sh CHROME_BIN=tools/karma/chromium-bin-wrapper.sh bash ./scripts/test-table-preimpl-lane.sh`;
    - resultado: `TOTAL: 48 SUCCESS`.
-17. Revalidacao integrada do gate seguro apos mitigacao WSL:
-   - `CHROMIUM_REAL_BIN=<puppeteer-executablePath> CHROMIUM_BIN=tools/karma/chromium-bin-wrapper.sh CHROME_BIN=tools/karma/chromium-bin-wrapper.sh bash tools/karma/run-safe-gate.sh`;
+17. Revalidacao integrada do gate seguro apos mitigacao:
+   - gate legado removido; usar `npm run test:table` e, quando aplicavel, `bash tools/karma/run-table-dsl-compat-gate.sh`;
    - `praxis-table lane`: `PASS` (`TOTAL: 48 SUCCESS`);
    - `praxis-crud full`: `PASS` (`TOTAL: 30 SUCCESS`).
-18. Automacao do gate seguro no WSL concluida:
-   - `tools/karma/run-safe-gate.sh` agora auto-configura `chromium-bin-wrapper.sh` + Puppeteer Chromium quando `CHROMIUM_BIN/CHROME_BIN` nao sao informados;
+18. Automacao do gate seguro concluida:
+   - runner legado removido; `tools/karma/karma.headless.conf.cjs` agora centraliza a configuracao headless;
    - revalidacao sem env manual:
-     `env -u CHROMIUM_BIN -u CHROME_BIN -u CHROMIUM_REAL_BIN bash tools/karma/run-safe-gate.sh`;
+    `npm run test:table`;
    - resultado: `praxis-table lane PASS (48 SUCCESS)` e `praxis-crud full PASS (30 SUCCESS)`.
 19. Cobertura adicional no wrapper `praxis-crud` para precedencia remoto > local concluida:
    - novo teste para `metadata.table.resourcePath` prevalecer sobre `metadata.data`;
@@ -492,9 +492,9 @@ Todos os itens abaixo devem estar `true`:
    - validacao dirigida executada com tsconfig temporario isolado (evitando erro externo de compilacao em `praxis-dynamic-fields`):
      `ng test praxis-crud --watch=false --browsers=ChromeHeadless --polyfills=zone.js --polyfills=zone.js/testing --ts-config .tmp-preimpl-lane/tsconfig.crud-isolated.json --include projects/praxis-crud/src/lib/praxis-crud.component.spec.ts`;
    - resultado: `TOTAL: 11 SUCCESS`.
-20. Revalidacao do `safe-gate` apos ampliar cobertura do CRUD:
-   - comando: `bash tools/karma/run-safe-gate.sh`;
-   - tentativa WSL da lane `praxis-table` permaneceu bloqueada por deteccao de Chromium (`No usable Chromium binary found for headless capture`);
+20. Revalidacao do gate apos ampliar cobertura do CRUD:
+   - comando atual: `npm run test:table`;
+   - tentativa legada da lane `praxis-table` permaneceu bloqueada por deteccao de Chromium (`No usable Chromium binary found for headless capture`);
    - fallback automatico via `cmd.exe + ChromeHeadless` executou com sucesso;
    - resultado final:
      - `praxis-table lane`: `PASS` (`TOTAL: 48 SUCCESS`);
@@ -502,23 +502,23 @@ Todos os itens abaixo devem estar `true`:
 21. Revalidacao full da `praxis-table` apos a ampliacao de cobertura no CRUD:
    - comando: `ng test praxis-table --watch=false --browsers=ChromeHeadless --polyfills=zone.js --polyfills=zone.js/testing`;
    - resultado: `TOTAL: 372 SUCCESS`.
-22. Hardening da lane WSL no script dedicado concluido:
-   - `scripts/test-table-preimpl-lane.sh` agora aplica automaticamente `tools/karma/chromium-bin-wrapper.sh` quando o probe direto de Chromium falha no WSL;
+22. Hardening da lane no script dedicado concluido:
+   - `scripts/test-table-preimpl-lane.sh` agora aplica automaticamente `tools/karma/chromium-bin-wrapper.sh` quando o probe direto de Chromium falha;
    - revalidacao direta da lane, sem env manual:
      `bash ./scripts/test-table-preimpl-lane.sh`;
    - resultado: `TOTAL: 48 SUCCESS`.
    - revalidacao adicional com ambiente limpo de browser vars:
      `env -u CHROMIUM_BIN -u CHROME_BIN -u CHROMIUM_REAL_BIN bash ./scripts/test-table-preimpl-lane.sh`;
    - resultado: `TOTAL: 48 SUCCESS`.
-23. Revalidacao do gate seguro apos hardening da lane WSL:
-   - comando: `bash tools/karma/run-safe-gate.sh`;
+23. Revalidacao do gate seguro apos hardening da lane:
+   - comando atual: `npm run test:table`;
    - resultado final: `praxis-table lane PASS (48 SUCCESS)` e `praxis-crud full PASS (32 SUCCESS)`;
-   - nesta execucao, a lane WSL concluiu na trilha primaria (sem fallback para `cmd.exe`).
+   - nesta execucao, a lane concluiu na trilha primaria.
 24. Revalidacao completa do gate seguro em modo estrito + full suite:
    - comando:
-     `SAFE_GATE_STRICT_WSL_PRIMARY=true SAFE_GATE_INCLUDE_TABLE_FULL=true bash tools/karma/run-safe-gate.sh`;
+    `npm run test:table`;
    - resultado final:
      - `praxis-table lane`: `PASS` (`TOTAL: 48 SUCCESS`);
-     - `praxis-table lane path`: `wsl-primary`;
+    - `praxis-table lane path`: `headless`;
      - `praxis-crud full`: `PASS` (`TOTAL: 32 SUCCESS`);
      - `praxis-table full`: `PASS` (`TOTAL: 372 SUCCESS`).

package/docs/local-data-support-pr-package.md

@@ -1,13 +1,13 @@
 # Pacote de PR - Local Data Support + Gate Karma
 
 ## Objetivo do pacote
-Consolidar o estado pronto para PR da trilha de suporte local/remote da `praxis-table`, com evidencias de validacao e operacao de testes no WSL/Windows.
+Consolidar o estado pronto para PR da trilha de suporte local/remote da `praxis-table`, com evidencias de validacao e operacao de testes locais.
 
 ## Escopo consolidado
 1. `praxis-crud` com suporte a `metadata.data` sem `resource.path`, preservando precedencia remoto > local.
-2. Hardening da lane isolada da `praxis-table` no WSL (wrapper/probe Chromium).
-3. Runner de gate seguro (`tools/karma/run-safe-gate.sh`) com modo estrito WSL e opcao de suite full da `praxis-table`.
-4. Revalidacao final do gate com trilha primaria WSL e suites completas verdes.
+2. Hardening da lane isolada da `praxis-table`.
+3. Runner de gate seguro legado substituido pelos comandos canônicos atuais.
+4. Revalidacao final do gate com suites completas verdes.
 
 ## Commits da etapa
 1. `7855fb9` feat(praxis-crud): suportar modo local via metadata.data sem resource.path
@@ -19,24 +19,24 @@ Consolidar o estado pronto para PR da trilha de suporte local/remote da `praxis-
 7. `0086e4c` test(praxis-table): estabiliza specs pendentes e fecha suíte
 8. `4e95076` test(praxis-table): expand shared TestBed provider coverage
 9. `e545355` docs(praxis-table): atualizar status de validacao pos-hardening
-10. `186e367` chore(karma): add WSL chromium probe wrapper for preimpl lane
+10. `186e367` chore(karma): add chromium probe wrapper for preimpl lane
 11. `3951fab` docs(praxis-table): registrar revalidacao do safe gate
-12. `73e7160` chore(karma): auto-configure WSL chromium wrapper in safe gate
+12. `73e7160` chore(karma): auto-configure chromium wrapper in safe gate
 13. `7a8e0d4` test(praxis-crud): cobrir precedencia de resourcePath fallback
 14. `d84c49d` docs(praxis-table): registrar safe-gate com crud 32 success
 15. `5d0a335` docs(praxis-table): registrar full suite 372 success apos safe-gate
 16. `0c0f55a` chore(karma): auto-fallback to chromium wrapper in preimpl lane
 17. `f7fe073` chore(karma): log resolved real chromium in preimpl lane
 18. `1857a87` docs(praxis-table): registrar gate estrito com full suite verde
-19. `b7d6782` docs(karma): document strict WSL safe-gate modes
+19. `b7d6782` docs(karma): document strict safe-gate modes
 
 ## Validacoes executadas (gate operacional)
 1. `bash ./scripts/test-table-preimpl-lane.sh`
    - Resultado: `TOTAL: 48 SUCCESS`.
-2. `bash tools/karma/run-safe-gate.sh`
-   - Resultado: `praxis-table lane PASS (48 SUCCESS)` e `praxis-crud full PASS (32 SUCCESS)`.
-3. `SAFE_GATE_STRICT_WSL_PRIMARY=true SAFE_GATE_INCLUDE_TABLE_FULL=true bash tools/karma/run-safe-gate.sh`
-   - Resultado: `praxis-table lane PASS (48 SUCCESS)`, `praxis-table lane path: wsl-primary`, `praxis-crud full PASS (32 SUCCESS)`, `praxis-table full PASS (372 SUCCESS)`.
+2. Gate canônico atual: `npm run test:table`
+   - Substitui o runner legado removido.
+3. Gate ordenado de compatibilidade DSL quando a mudanca tocar contratos da tabela: `bash tools/karma/run-table-dsl-compat-gate.sh`
+   - Usar junto com build/test focal conforme o `AGENTS.md` da subarea.
 
 ## Cobertura critica confirmada
 1. Preservacao de `pageSize` local (override do usuario)
@@ -57,7 +57,7 @@ Consolidar o estado pronto para PR da trilha de suporte local/remote da `praxis-
    - manter validacao focada e reproduzivel via `ng test` com `--include` por suite/arquivo;
    - preferir setup de testes centralizado e reutilizavel (consolidacao de providers compartilhados no hardening dos integration tests);
    - manter contratos e comportamento com regressao protegida por specs dedicadas (precedencia `resourcePath > data`, transicoes local/remote/empty);
-   - executar gate com comandos explicitos e deterministicos (modo estrito WSL + suite full opcional).
+   - executar gate com comandos explicitos e deterministicos.
 3. Referencias oficiais retornadas por `search_documentation`:
    - https://angular.dev/cli/test#options
    - https://angular.dev/guide/testing/utility-apis

package/docs/release-notes-p1-hardening.md

@@ -11,9 +11,7 @@ Nota historica: esta baseline e anterior a canonicalizacao de Json Logic. As ref
   - Helpers anteriores mantidos (`jsonGet/jsonEq/jsonIn`, `isBlank`, `today/now`, `len*`, etc.).
   - Normalização legada preservada para expressões antigas.
   - Limitação documentada: parser atual não suporta comparação direta de retorno de função (`fn(...) == valor`).
-- `toolbar.actions.visibleWhen` com politica por ambiente:
-  - `prod/qa`: fail-closed.
-  - `dev/hml`: fail-open para diagnostico.
+- `toolbar.actions.visibleWhen` hoje falha fechado em todos os ambientes quando a condicao nao e Json Logic valida. A baseline historica de `2026-02-26` registrava comportamento diagnostico legado, mas esse comportamento foi removido na canonicalizacao.
 - `shortcutScope` canonico com validacao (`toolbar|global`) e fallback seguro.
 - Guards schema-only para:
   - `behavior.sorting.multiSort`

package/docs/resource-events.md

@@ -0,0 +1,36 @@
+# Praxis Table Resource Events
+
+`PraxisTable` emits `resourceEvent` in parallel with its existing public outputs. The envelope is intended for enterprise hosts that need one governed stream for audit, analytics, shell orchestration, and related-resource surfaces.
+
+## Event Mapping
+
+| Table interaction | `kind` | `sourceOutput` | `phase` |
+| --- | --- | --- | --- |
+| Row click | `row-click` | `rowClick` | `notification` |
+| Row double click | `row-double-click` | `rowDoubleClick` | `notification` |
+| Selection change | `selection-change` | `selectionChange` | `notification` |
+| Row action | `row-action` | `rowAction` | `notification` |
+| Toolbar action | `toolbar-action` | `toolbarAction` | `notification` |
+| Bulk action | `bulk-action` | `bulkAction` | `notification` |
+| Export action | `export-action` | `exportAction` | `success` or `error` |
+| Dynamic record surface fallback | `surface-open` | `recordSurfaceOpen` | `request` |
+| Catalog-backed record surface | `surface-open` | `recordSurfaceOpen` | `request`, then `success` or `error` |
+| Catalog-backed collection surface | `surface-open` | `toolbarAction` | `request`, then `success` or `error` |
+
+`notification` events preserve the old output semantics and should not be interpreted as business completion. Host-mediated operations such as `surface.open` emit `request` before invoking `GlobalActionService` and then emit `success` or `error` after the result is known.
+
+`selectionChange` can also be emitted with `trigger: "data-reconcile"` when a data update removes identities from the effective selection. Rehydrating the same selected identities does not emit a new selection event. With `persistSelection`, identities may remain selected outside the current page; `persistOnDataUpdate` only reconciles selection against the current visible dataset.
+
+Record-oriented events may carry `resourceIdentity`. Resolution prefers a valid
+explicit `x-ui.resource.identity`, then a key-only fallback from a valid
+`x-ui.resource.idField`, then the effective host `idField` when that field is
+present in the filtered response schema. Fallback identities expose `source`
+and structured `diagnostics`; they never infer a title from property names. If
+the configured field has no displayable row value, the event carries
+`resourceIdentity: null` and the runtime emits a deduplicated diagnostic.
+
+## Surface Rules
+
+For catalog-backed surfaces, `resourceEvent.surface` carries the canonical `ResourceSurfaceCatalogItem`, including `relatedResource` when the backend publishes it. For fallback dynamic-page requests, the payload still carries the requested surface context, but `surface` may be `null` because no full catalog item is available.
+
+Consumers must keep legacy outputs wired where they already depend on them. `resourceEvent` is the canonical cross-component event stream, not a breaking replacement for existing outputs.

package/fesm2022/{praxisui-table-filter-form-dialog-host.component-DbwGIMjF.mjs → praxisui-table-filter-form-dialog-host.component-CMUCxwyL.mjs}

@@ -4,13 +4,14 @@ import * as i1 from '@angular/material/dialog';
 import { MAT_DIALOG_DATA, MatDialogModule } from '@angular/material/dialog';
 import * as i3 from '@angular/material/button';
 import { MatButtonModule } from '@angular/material/button';
-import * as i14 from '@angular/material/progress-bar';
+import * as i13 from '@angular/material/progress-bar';
 import { MatProgressBarModule } from '@angular/material/progress-bar';
-import * as i4 from '@angular/material/icon';
+import * as i7 from '@angular/material/icon';
 import { MatIconModule } from '@angular/material/icon';
-import * as i10 from '@angular/material/tooltip';
+import * as i14 from '@angular/material/tooltip';
 import { MatTooltipModule } from '@angular/material/tooltip';
 import { PraxisFilterForm } from '@praxisui/dynamic-form';
+import { PraxisIconButtonComponent } from '@praxisui/core';
 
 class FilterFormDialogHostComponent {
     data;
@@ -109,10 +110,8 @@ class FilterFormDialogHostComponent {
         <mat-icon>tune</mat-icon>
         <span>{{ data.title || 'Filtro avançado' }}</span>
       </div>
-      <button mat-icon-button type="button" class="pfx-dialog-close" (click)="close()"
-        [attr.aria-label]="data.i18n?.cancel || 'Fechar'">
-        <mat-icon>close</mat-icon>
-      </button>
+      <button praxisIconButton="close" size="compact" type="button" class="pfx-dialog-close" (click)="close()"
+        [attr.aria-label]="data.i18n?.cancel || 'Fechar'"></button>
     </div>
     <mat-dialog-content class="pfx-filter-dialog-content" aria-labelledby="filterDialogTitle">
       @if (data?.schemaLoading) {
@@ -161,20 +160,18 @@ class FilterFormDialogHostComponent {
         {{ data.i18n?.apply || 'Aplicar' }}
       </button>
     </mat-dialog-actions>
-    `, isInline: true, styles: [".pfx-dialog-title{display:flex;align-items:center;justify-content:space-between;gap:12px;padding-right:8px}.pfx-dialog-title-text{display:inline-flex;align-items:center;gap:8px;font-weight:600;color:var(--mdc-dialog-subhead-color, var(--md-sys-color-on-surface))}.pfx-dialog-close{margin-left:auto}.pfx-filter-dialog-content{display:flex;flex-direction:column;gap:12px;padding-top:8px}.pfx-empty-state{margin:8px 0 0;color:var(--mdc-dialog-supporting-text-color, var(--md-sys-color-on-surface-variant))}.pfx-dialog-loading{display:flex;flex-direction:column;gap:10px;min-height:128px;justify-content:center;color:var(--mdc-dialog-supporting-text-color, var(--md-sys-color-on-surface-variant));font-size:.875rem}.pfx-form-pending{height:0;overflow:hidden;visibility:hidden;pointer-events:none}.pfx-dialog-actions{padding:var(--pdx-dialog-actions-padding, 12px 24px 16px);border-top:1px solid var(--md-sys-color-outline-variant);background:transparent;display:flex;align-items:center;gap:8px}.pfx-save-shortcut-button{margin-right:auto}.pfx-save-shortcut-button mat-icon{margin-right:6px;width:18px;height:18px;font-size:18px}\n"], dependencies: [{ kind: "ngmodule", type: MatDialogModule }, { kind: "directive", type: i1.MatDialogTitle, selector: "[mat-dialog-title], [matDialogTitle]", inputs: ["id"], exportAs: ["matDialogTitle"] }, { kind: "directive", type: i1.MatDialogActions, selector: "[mat-dialog-actions], mat-dialog-actions, [matDialogActions]", inputs: ["align"] }, { kind: "directive", type: i1.MatDialogContent, selector: "[mat-dialog-content], mat-dialog-content, [matDialogContent]" }, { kind: "ngmodule", type: MatButtonModule }, { kind: "component", type: i3.MatButton, selector: "    button[matButton], a[matButton], button[mat-button], button[mat-raised-button],    button[mat-flat-button], button[mat-stroked-button], a[mat-button], a[mat-raised-button],    a[mat-flat-button], a[mat-stroked-button]  ", inputs: ["matButton"], exportAs: ["matButton", "matAnchor"] }, { kind: "component", type: i3.MatIconButton, selector: "button[mat-icon-button], a[mat-icon-button], button[matIconButton], a[matIconButton]", exportAs: ["matButton", "matAnchor"] }, { kind: "ngmodule", type: MatProgressBarModule }, { kind: "component", type: i14.MatProgressBar, selector: "mat-progress-bar", inputs: ["color", "value", "bufferValue", "mode"], outputs: ["animationEnd"], exportAs: ["matProgressBar"] }, { kind: "ngmodule", type: MatIconModule }, { kind: "component", type: i4.MatIcon, selector: "mat-icon", inputs: ["color", "inline", "svgIcon", "fontSet", "fontIcon"], exportAs: ["matIcon"] }, { kind: "ngmodule", type: MatTooltipModule }, { kind: "directive", type: i10.MatTooltip, selector: "[matTooltip]", inputs: ["matTooltipPosition", "matTooltipPositionAtOrigin", "matTooltipDisabled", "matTooltipShowDelay", "matTooltipHideDelay", "matTooltipTouchGestures", "matTooltip", "matTooltipClass"], exportAs: ["matTooltip"] }, { kind: "component", type: PraxisFilterForm, selector: "praxis-filter-form", inputs: ["config", "formId", "resourcePath", "mode"], outputs: ["formReady", "valueChange", "submit", "requestSearch", "validityChange"] }] });
+    `, isInline: true, styles: [".pfx-dialog-title{display:flex;align-items:center;justify-content:space-between;gap:12px;padding-right:8px}.pfx-dialog-title-text{display:inline-flex;align-items:center;gap:8px;font-weight:600;color:var(--mdc-dialog-subhead-color, var(--md-sys-color-on-surface))}.pfx-dialog-close{margin-left:auto}.pfx-filter-dialog-content{display:flex;flex-direction:column;gap:12px;padding-top:8px}.pfx-empty-state{margin:8px 0 0;color:var(--mdc-dialog-supporting-text-color, var(--md-sys-color-on-surface-variant))}.pfx-dialog-loading{display:flex;flex-direction:column;gap:10px;min-height:128px;justify-content:center;color:var(--mdc-dialog-supporting-text-color, var(--md-sys-color-on-surface-variant));font-size:.875rem}.pfx-form-pending{height:0;overflow:hidden;visibility:hidden;pointer-events:none}.pfx-dialog-actions{padding:var(--pdx-dialog-actions-padding, 12px 24px 16px);border-top:1px solid var(--md-sys-color-outline-variant);background:transparent;display:flex;align-items:center;gap:8px}.pfx-save-shortcut-button{margin-right:auto}.pfx-save-shortcut-button mat-icon{margin-right:6px;width:18px;height:18px;font-size:18px}\n"], dependencies: [{ kind: "ngmodule", type: MatDialogModule }, { kind: "directive", type: i1.MatDialogTitle, selector: "[mat-dialog-title], [matDialogTitle]", inputs: ["id"], exportAs: ["matDialogTitle"] }, { kind: "directive", type: i1.MatDialogActions, selector: "[mat-dialog-actions], mat-dialog-actions, [matDialogActions]", inputs: ["align"] }, { kind: "directive", type: i1.MatDialogContent, selector: "[mat-dialog-content], mat-dialog-content, [matDialogContent]" }, { kind: "ngmodule", type: MatButtonModule }, { kind: "component", type: i3.MatButton, selector: "    button[matButton], a[matButton], button[mat-button], button[mat-raised-button],    button[mat-flat-button], button[mat-stroked-button], a[mat-button], a[mat-raised-button],    a[mat-flat-button], a[mat-stroked-button]  ", inputs: ["matButton"], exportAs: ["matButton", "matAnchor"] }, { kind: "ngmodule", type: MatProgressBarModule }, { kind: "component", type: i13.MatProgressBar, selector: "mat-progress-bar", inputs: ["color", "value", "bufferValue", "mode"], outputs: ["animationEnd"], exportAs: ["matProgressBar"] }, { kind: "ngmodule", type: MatIconModule }, { kind: "component", type: i7.MatIcon, selector: "mat-icon", inputs: ["color", "inline", "svgIcon", "fontSet", "fontIcon"], exportAs: ["matIcon"] }, { kind: "ngmodule", type: MatTooltipModule }, { kind: "directive", type: i14.MatTooltip, selector: "[matTooltip]", inputs: ["matTooltipPosition", "matTooltipPositionAtOrigin", "matTooltipDisabled", "matTooltipShowDelay", "matTooltipHideDelay", "matTooltipTouchGestures", "matTooltip", "matTooltipClass"], exportAs: ["matTooltip"] }, { kind: "component", type: PraxisFilterForm, selector: "praxis-filter-form", inputs: ["config", "formId", "resourcePath", "mode"], outputs: ["formReady", "valueChange", "submit", "requestSearch", "validityChange"] }, { kind: "component", type: PraxisIconButtonComponent, selector: "button[praxisIconButton]", inputs: ["praxisIconButton", "size", "appearance", "presentation", "pressed", "busy"] }] });
 }
 i0.ɵɵngDeclareClassMetadata({ minVersion: "12.0.0", version: "21.2.14", ngImport: i0, type: FilterFormDialogHostComponent, decorators: [{
             type: Component,
-            args: [{ selector: 'praxis-filter-form-dialog-host', standalone: true, imports: [MatDialogModule, MatButtonModule, MatProgressBarModule, MatIconModule, MatTooltipModule, PraxisFilterForm], template: `
+            args: [{ selector: 'praxis-filter-form-dialog-host', standalone: true, imports: [MatDialogModule, MatButtonModule, MatProgressBarModule, MatIconModule, MatTooltipModule, PraxisFilterForm, PraxisIconButtonComponent], template: `
     <div mat-dialog-title class="pfx-dialog-title" id="filterDialogTitle">
       <div class="pfx-dialog-title-text">
         <mat-icon>tune</mat-icon>
         <span>{{ data.title || 'Filtro avançado' }}</span>
       </div>
-      <button mat-icon-button type="button" class="pfx-dialog-close" (click)="close()"
-        [attr.aria-label]="data.i18n?.cancel || 'Fechar'">
-        <mat-icon>close</mat-icon>
-      </button>
+      <button praxisIconButton="close" size="compact" type="button" class="pfx-dialog-close" (click)="close()"
+        [attr.aria-label]="data.i18n?.cancel || 'Fechar'"></button>
     </div>
     <mat-dialog-content class="pfx-filter-dialog-content" aria-labelledby="filterDialogTitle">
       @if (data?.schemaLoading) {