@praxisui/table 8.0.0-beta.99 → 9.0.0-beta.1

package/README.md

@@ -171,6 +171,8 @@ Filtro runtime:
 - Minimizing the table shell keeps the governed session in `PraxisAssistantSessionRegistryService` with `presence: 'origin-anchor'`; the visual affordance returns to the table assistant trigger, which changes to the minimized state and reopens the preserved session. The App Shell does not interpret or execute table semantics.
 - The table snapshot stores only safe context: table identity, target, context chips, manifest reference, resource path, schema field names, data/runtime digests, capability refs and governance hints.
 - When rows are selected, the assistant context includes a governed `table-row-selection` digest with selected count, id field, selected ids and a small sanitized row sample. The runtime never uses selected row text to decide primary intent; the LLM/backend receives the digest only as grounding after the assistant turn has the table component scope.
+- The table also registers a runtime observation provider through `PraxisRuntimeComponentObservationRegistryService`. Runtime observations publish redacted component evidence only: identity, resource refs, `runtimeSurfaceInstanceRef`, lifecycle, selection and data-profile digests, schema field refs, declared record surfaces and declared table actions.
+- Runtime observations must not include raw rows, full cell values, hidden fields, secrets or intent decisions. Surface and action refs are derived from declared contracts such as `aiContext.recordSurfaces`, table capabilities and adapter context; undeclared navigation or inferred intents stay out of the observation envelope.
 - Prompts that indicate shared business decisions, such as rules, policies, compliance, LGPD, approval, eligibility or access control, must be routed to governed `domain-rules` handoff instead of local table config patches.
 
 ### Consultative answers vs governed edits
@@ -555,12 +557,12 @@ O manifesto (v2.0.0) é exportado como `PRAXIS_TABLE_AUTHORING_MANIFEST` e proje
 ## 🚀 Instalação
 
 ```bash
-npm install @praxisui/ai @praxisui/core @praxisui/table
+npm install @praxisui/ai@latest @praxisui/core@latest @praxisui/table@latest
 ```
 
 Peers necessários (instale no app host):
 - `@angular/core` `^20.0.0`, `@angular/common` `^20.0.0`
-- `@praxisui/ai` `^8.0.0-beta.0`
+- `@praxisui/ai` `^9.0.0-beta.1`
 - `@praxisui/core` `^0.0.1`
 - `@praxisui/dynamic-fields` `^0.0.1` (quando usar editores/inputs dinâmicos)
 - `@praxisui/dynamic-form` `^0.0.1` (quando integrar com formulários dinâmicos)

package/docs/dynamic-filter-host-integration-guide.md

@@ -118,6 +118,13 @@ Essas chaves são as mais importantes na prática:
 - `allowSaveTags`: habilita tags persistidas/visíveis;
 - `changeDebounceMs`: regula a cadência de emissão de `change` e `submit`.
 
+`selectedFieldIds` é a parte gerenciável da toolbar de filtros. O seletor de
+campos deve permitir adicionar e remover esses filtros exibidos; ao remover um
+campo com valor ativo, o runtime limpa também o critério correspondente no DTO
+e emite o novo payload para evitar filtro invisível. Use `alwaysVisibleFields`
+apenas para campos realmente fixos, porque eles não entram nessa remoção rápida
+do usuário.
+
 #### Padronizar `materialDesign` dos campos de filtro
 
 O `praxis-filter` normaliza a metadata efetiva de filtros com uma politica