@praxisui/table 8.0.0-beta.33 → 8.0.0-beta.34

package/README.md

@@ -170,6 +170,7 @@ Filtro runtime:
 - The table session identity follows `table:{routeKey}:{componentInstanceId || tableId}` so multiple tables on the same page can preserve separate assistant sessions.
 - 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.
 - 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

package/docs/dynamic-filter-payload-contract.md

@@ -295,6 +295,7 @@ Diretriz de compatibilidade:
 - `filterCriteria` continua válido em componentes que ainda publicam esse contrato
 - para novo authoring, recipes e bindings, prefira `queryContext`
 - a semântica mínima garantida hoje é `queryContext.filters`; `sort`, `limit` e `page` devem ser consumidos apenas por widgets que já declararam suporte a esses campos
+- `queryContext.filters` continua sendo um DTO plano com semântica de conjunção simples; filtros compostos com OR ou grupos aninhados devem evoluir pelo contrato canônico proposto em `projects/praxis-core/docs/rfc-query-context-filter-expression.md`, não por aliases ou payloads ad hoc do frontend
 
 ## Payloads que devem ser evitados