@praxisui/core 10.0.0-rc.25 → 10.0.0-rc.27

package/README.md

@@ -57,9 +57,10 @@ const preview = await firstValueFrom(bulkClient.readProposalResults(contract, pr
 await session.confirm(idempotencyKeyForThisIntent);
 // On an uncertain HTTP failure, retain this session and retry with the same key.
 // The host schedules further authorized readbacks for an accepted nonterminal execution.
-if (!session.isTerminal()) await session.refreshExecution();
+const reads = new AbortController(); // This view owns GET lifetime, not confirmation custody.
+if (!session.isTerminal()) await session.refreshExecution(reads.signal);
 if (session.isTerminal()) {
-  const results = await session.readResults();
+  const results = await session.readResults(200, undefined, reads.signal);
 }
 ```
 
@@ -69,6 +70,24 @@ the descriptor. The caller controls when to read status again and presents each
 authorized page of results. This example is a service integration sketch, not a
 ready visual workflow or a deployment claim.
 
+`refreshExecution(signal?)` and `readResults(size?, after?, signal?)` retain their
+Promise API and optionally accept a standard `AbortSignal`. An already aborted
+signal dispatches no GET; abort unsubscribes the actual HTTP request, releases the
+read slot, and prevents a late Promise continuation from updating the session.
+Abort listeners are removed on success, failure and cancellation. A cancelled GET
+keeps the original proposal, confirmation key and accepted execution; it does not
+mark that execution terminal or prove rollback. A new authorized read may observe
+the same execution. Overlapping execution refreshes remain rejected, while an
+aborted generation cannot release the slot of its successor.
+
+The caller owns GET cancellation and its observation budget; the Core session does
+not invent a global read timeout. Use a fresh read lifetime for a fresh consultation
+and abort reads when the owning view closes. Do not race a Promise with a timer:
+connect the signal to the read itself so the HTTP subscription is torn down.
+`evaluate` and `confirm` do not accept this signal: a dispatched POST and its original
+key stay in intent custody across view teardown. GET failure/cancellation must never
+start a new evaluation or confirmation automatically.
+
 The backend is the authority on proposal expiry. A client clock hint must not
 block a same-key replay after an uncertain confirmation; the backend may return
 409 or 410 and the host must explain that state without inventing a new intent.
@@ -87,6 +106,27 @@ surface does not advertise them. Query selection, ASYNC jobs and ATOMIC mode are
 outside this Angular slice. This is not a claim that the reference host or full
 backend B7 acceptance is complete.
 
+## Published asynchronous execution tracking
+
+`PraxisBulkClientService.waitForExecution` is separate from the BASIC client
+above. Use its published execution operation only when that operation actually
+supports the asynchronous profile; an enum member does not enable a backend
+profile. The Observable emits one canonical terminal snapshot, preserving
+`COMPLETED`, `COMPLETED_WITH_ERRORS`, `CANCELLED`, `STOPPED` and
+`RECONCILIATION_REQUIRED`. `CANCEL_REQUESTED` remains pending.
+
+Each subscription starts its own strict overall deadline. At most one GET is in
+flight: interval ticks do not abort a useful slow read or queue overlapping reads.
+Pending responses do not renew the deadline, which also bounds a GET that never
+responds. Terminal completion, transport error, deadline and unsubscribe release
+the active read and polling timers; a late response cannot revive an expired
+subscription. Stopping a GET does not reverse server effects or cancel a POST.
+
+A read failure means the outcome is unknown. Explicitly resume reads for the same
+execution and preserve the original proposal and confirmation key; do not confirm
+or evaluate again to restore progress. This transport does not provide custody
+across closing/reopening a dialog, reload recovery or operational ASYNC acceptance.
+
 ## Governed color palettes
 
 `materializeGovernedPaletteEntries(palette, purposes)` returns `MaterializedGovernedColorToken[]`, pairing each original `entry` with its resolved `color`. It preserves distinct token IDs even when CSS references/colors match, applies purpose filtering, and resolves fallback dependencies against the complete palette. Use this projection for identified swatches; do not zip color arrays to entries or infer identity from color equality. `materializeGovernedPaletteColors` remains the string-only projection of the same resolver.
@@ -831,7 +871,9 @@ Action-bearing components must use the semantic `--praxis-action-control-*` vari
 
 ### Catálogo no quick connect e isolamento do editor de página
 
-`ResourceQuickConnectComponent` apresenta recursos publicados em `/schemas/catalog` usando o seletor `pdx-material-select` registrado em `ComponentMetadataRegistry`. O host deve registrar os descritores oficiais de DynamicFields. O controle é inicializado pelo protocolo `setInputMetadata` e ControlValueAccessor; Core não importa a biblioteca de campos. A conexão avançada por rota continua disponível.
+`ResourceQuickConnectComponent` apresenta recursos publicados em `/schemas/catalog` usando o seletor `pdx-material-select` registrado em `ComponentMetadataRegistry`. O host deve registrar os descritores oficiais de DynamicFields. O controle é inicializado pelo protocolo `setInputMetadata` e `ControlValueAccessor`; Core não importa a biblioteca de campos. A conexão avançada por rota continua disponível (com `<datalist>` de sugestões do catálogo e abertura automática da seção avançada quando o seletor dinâmico não está disponível ou quando o recurso atual é uma rota customizada fora do catálogo).
+
+O componente expõe `[resourcePath]`, `(resourcePathChange)`, `[endpointKey]`, `[apiUrlEntry]`, `ControlValueAccessor` (`ngModel` / `formControl`) e os hooks `reset()` / `acceptAppliedValue()` de `SettingsValueProvider`. A projeção e reconciliação de opções do catálogo são centralizadas em `ResourceDiscoveryService.getDiscoveredResources()`, `loadDiscoveredResources()`, `projectSchemaCatalogResources()` e `resolveCatalogResourceOptionValue()`, deduplicando chamadas concorrentes a `/schemas/catalog` por URL e reconciliando caminhos relativos com ou sem prefixo `/api`. `ResourceDiscoveryService` reutiliza a instância do injetor ancestral quando um componente standalone cria injetor filho sem override local de `API_URL`.
 
 O editor de configurações da página recebe uma cópia da definição autoral. Dados carregados e entradas transitórias dos widgets não devem virar configuração ao alterar o layout.
 

package/ai/component-registry.json

@@ -1,8 +1,8 @@
 {
   "schemaVersion": "1.0.0",
-  "generatedAt": "2026-10-15T15:10:58.041Z",
+  "generatedAt": "2026-10-15T22:42:56.841Z",
   "packageName": "@praxisui/core",
-  "packageVersion": "10.0.0-rc.25",
+  "packageVersion": "10.0.0-rc.27",
   "sourceRegistry": "praxis-component-registry-ingestion",
   "sourceRegistryVersion": "1.0.0",
   "componentCount": 4,