@cratis/pi 2.22.0 → 2.23.1

package/package/corpus/skills/cratis-arc-command-execution/SKILL.md

@@ -15,8 +15,10 @@ dispatch.
 
 | Package | Version | Purpose |
 | --- | --- | --- |
-| `Cratis.Arc.Core` | `22.10.4` | `Cratis.Arc.Commands.ICommandPipeline`, `CommandResult`, `ValidationResultSeverity` |
-| `Cratis.Arc.Chronicle` | `22.10.4` | analyzer `ARCCHR0006` for reactor replay |
+| `Cratis.Arc.Core` | `22.16.0` | `Cratis.Arc.Commands.ICommandPipeline`, `CommandResult`, `ValidationResultSeverity` |
+| `Cratis.Arc.Chronicle` | `22.16.0` | analyzer `ARCCHR0006` for reactor replay |
+
+> Re-verified at the versions above by **symbol and signature**: every type, attribute and member this skill names exists at that tag, and the public surface it describes is unchanged since the previous verification (Chronicle 16.45.x / Arc 22.10.4 — the Chronicle 16→18 client diff is converters, options and doc comments; no type was removed or renamed). Behavior claims were verified at the earlier tag unless a section says otherwise.
 
 Reverify before claiming support for another version.
 
@@ -29,6 +31,14 @@ inject `IEventLog` (`ARCCHR0007`).
 
 ## Inject and execute
 
+> **Reactors have a declarative alternative.** With the Arc Chronicle integration a
+> reactor handler can **return** the `[Command]` (or a collection of commands) and
+> Arc executes it; a denied or invalid result fails the partition instead of being
+> discarded, and `[ExecuteCommandsAsSystem]` on the reactor class supplies a
+> principal for those returned commands. That attribute does **not** cover manual
+> `Execute` calls — the form below needs its own execution context. See the
+> **cratis-chronicle-reactor** skill.
+
 ```csharp
 public class <Name>Reactor(ICommandPipeline pipeline) : IReactor
 {

package/package/corpus/skills/cratis-arc-command-validation/SKILL.md

@@ -23,11 +23,13 @@ rejection on it.)
 
 | Package | Version | Purpose |
 | --- | --- | --- |
-| `Cratis.Arc.Core` | `22.10.4` | `CommandValidator<T>`, `ConceptValidator<T>`, `ValidationResult`, `CommandResult`, the command pipeline, `ARC0004`–`ARC0013` |
-| `Cratis.Fundamentals` | `7.18.2` | `Cratis.Monads.Result<TResult, TError>` |
-| `Cratis.Chronicle` | `16.45.2` | Read-model resolution for command-side injection |
+| `Cratis.Arc.Core` | `22.16.0` | `CommandValidator<T>`, `ConceptValidator<T>`, `ValidationResult`, `CommandResult`, the command pipeline, `ARC0004`–`ARC0013` |
+| `Cratis.Fundamentals` | `7.19.2` | `Cratis.Monads.Result<TResult, TError>` |
+| `Cratis.Chronicle` | `18.3.0` | Read-model resolution for command-side injection |
 | `FluentValidation` | `12.1.1` | `RuleFor(...)`, `.WithMessage(...)` |
 
+> Re-verified at the versions above by **symbol and signature**: every type, attribute and member this skill names exists at that tag, and the public surface it describes is unchanged since the previous verification (Chronicle 16.45.x / Arc 22.10.4 — the Chronicle 16→18 client diff is converters, options and doc comments; no type was removed or renamed). Behavior claims were verified at the earlier tag unless a section says otherwise.
+
 Reverify against the owning product repository before claiming support for
 another version.
 

package/package/corpus/skills/cratis-arc-ef-core-migration/SKILL.md

@@ -15,10 +15,12 @@ Everything else is ordinary EF Core.
 
 | Package | Version | Purpose |
 | --- | --- | --- |
-| `Cratis.Arc.EntityFrameworkCore` | `22.10.4` | `BaseDbContext`, `ReadOnlyDbContext`, `WithEntityFrameworkCore`, column helpers, `EntityFrameworkReadModelForCommandResolver` |
-| `Cratis.Arc.Core` | `22.10.4` | `Cratis.Arc.Queries.ModelBound.ReadModelAttribute`, `ICanResolveReadModelForCommand` |
+| `Cratis.Arc.EntityFrameworkCore` | `22.16.0` | `BaseDbContext`, `ReadOnlyDbContext`, `WithEntityFrameworkCore`, column helpers, `EntityFrameworkReadModelForCommandResolver` |
+| `Cratis.Arc.Core` | `22.16.0` | `Cratis.Arc.Queries.ModelBound.ReadModelAttribute`, `ICanResolveReadModelForCommand` |
 | `Microsoft.EntityFrameworkCore` | `10.0.11` | EF Core itself, including all migration tooling |
 
+> Re-verified at the versions above by **symbol and signature**: every type, attribute and member this skill names exists at that tag, and the public surface it describes is unchanged since the previous verification (Chronicle 16.45.x / Arc 22.10.4 — the Chronicle 16→18 client diff is converters, options and doc comments; no type was removed or renamed). Behavior claims were verified at the earlier tag unless a section says otherwise.
+
 Reverify before claiming support for another version.
 
 ⚠️ **Arc ships no migration tooling of its own.** There is no design-time
@@ -148,8 +150,9 @@ migrationBuilder.CreateTable(
 `StringColumn`, `NumberColumn<T>`, `BoolColumn`, `AutoIncrementColumn`,
 `GuidColumn` and `DateTimeOffsetColumn` all take the `MigrationBuilder` as their
 first argument — that is how they learn which database they are generating for.
-All of them default `nullable` to **`true`**, so a required column has to say
-`nullable: false` explicitly.
+All of them except `AutoIncrementColumn` default `nullable` to **`true`**, so a
+required column has to say `nullable: false` explicitly; `AutoIncrementColumn`
+has no `nullable` parameter and is always `NOT NULL`.
 
 On `MigrationBuilder`, for an existing table:
 

package/package/corpus/skills/cratis-arc-observable-query-http/SKILL.md

@@ -13,7 +13,9 @@ request is made. Choose the transport first, then the command.
 
 | Package | Version | Purpose |
 | --- | --- | --- |
-| `Cratis.Arc.Core` | `22.10.4` | `ObservableQueryHttp`, `ObservableQueryHandler`, the demultiplexer routes |
+| `Cratis.Arc.Core` | `22.16.0` | `ObservableQueryHttp`, `ObservableQueryHandler`, the demultiplexer routes |
+
+> Re-verified at the versions above by **symbol and signature**: every type, attribute and member this skill names exists at that tag, and the public surface it describes is unchanged since the previous verification (Chronicle 16.45.x / Arc 22.10.4 — the Chronicle 16→18 client diff is converters, options and doc comments; no type was removed or renamed). Behavior claims were verified at the earlier tag unless a section says otherwise.
 
 Reverify before claiming support for another version. This skill is read-only
 inspection of an endpoint the user already has; it neither implements the query
@@ -29,7 +31,12 @@ handler decides in this order:
    (case-insensitive);
 3. **plain HTTP** — everything else, answered once and closed.
 
-A plain `curl` sends neither, so it always lands on the third case.
+A plain `curl` sends neither, so it always lands on the third case — and there
+the two result shapes part ways: an **`ISubject<T>`** query answers with one
+`QueryResult` as described below, while an **`IAsyncEnumerable<T>`** query
+answers **HTTP 400** with `{ "message": "AsyncEnumerable queries require WebSocket connection" }`
+and never a `QueryResult`. Everything that follows on this page is about
+`ISubject<T>`; inspect an `IAsyncEnumerable<T>` query over WebSocket.
 
 ## Snapshot: the current value, once
 
@@ -37,7 +44,7 @@ A plain `curl` sends neither, so it always lands on the third case.
 curl "https://<host>/<api-prefix>/<route>"
 ```
 
-The response is one JSON `QueryResult`.
+The response is one JSON `QueryResult` (for an `ISubject<T>` query — see above).
 
 ⚠️ **When the observable has not produced its first value yet, this returns HTTP
 202 Accepted with a not-ready result** — no exception, no data. That is a normal

package/package/corpus/skills/cratis-arc-query-paging/SKILL.md

@@ -13,10 +13,12 @@ the query string — you choose a **return shape** that the framework can narrow
 
 | Package | Version | Purpose |
 | --- | --- | --- |
-| `Cratis.Arc.Core` | `22.10.4` | `QueryableQueryRenderer`, `Paging`, `Sorting`, `PagingInfo` |
-| `Cratis.Arc.MongoDB` | `22.10.4` | `Observe` helpers that page at the source |
-| `Cratis.Arc.EntityFrameworkCore` | `22.10.4` | `DbSet<T>` observe helpers that page at the source |
-| `@cratis/arc.react` | `22.10.4` | `useWithPaging`, `useSuspenseWithPaging` |
+| `Cratis.Arc.Core` | `22.16.0` | `QueryableQueryRenderer`, `Paging`, `Sorting`, `PagingInfo` |
+| `Cratis.Arc.MongoDB` | `22.16.0` | `Observe` helpers that page at the source |
+| `Cratis.Arc.EntityFrameworkCore` | `22.16.0` | `DbSet<T>` observe helpers that page at the source |
+| `@cratis/arc.react` | `22.16.0` | `useWithPaging`, `useSuspenseWithPaging` |
+
+> Re-verified at the versions above by **symbol and signature**: every type, attribute and member this skill names exists at that tag, and the public surface it describes is unchanged since the previous verification (Chronicle 16.45.x / Arc 22.10.4 — the Chronicle 16→18 client diff is converters, options and doc comments; no type was removed or renamed). Behavior claims were verified at the earlier tag unless a section says otherwise.
 
 Reverify before claiming support for another version. A small, bounded result
 set does not need any of this — `IEnumerable<T>` is fine.
@@ -25,7 +27,7 @@ set does not need any of this — `IEnumerable<T>` is fine.
 
 | Query-string key | Effect |
 | --- | --- |
-| `pageSize` | **Required to page at all.** Must be greater than 0 |
+| `pageSize` | **Required to page at all** on the query string; any parseable integer is accepted (`0` yields an empty page, negatives are clamped by `Skip`) — the JSON body reader, by contrast, treats `pageSize <= 0` as not paged |
 | `page` | Zero-based. Defaults to `0` when `pageSize` is present |
 | `sortby` | Field name; PascalCased before use, so `?sortby=name` sorts on `Name` |
 | `sortDirection` | `desc` (case-insensitive) sorts descending; **anything else, including a missing value, is ascending** |
@@ -36,9 +38,12 @@ Two consequences that surprise people:
 - **Sorting needs both keys.** `sortby` without `sortDirection` is ignored
   entirely.
 
-Paging is validated before the query runs: `page` must be `>= 0` and `pageSize`
-must be `> 0`, and a violation comes back as a validation failure rather than a
-crash.
+Paging is **not** validated on the request path at 22.16.0: `PageNumber`/`PageSize`
+concept validators exist (`page >= 0`, `pageSize > 0`) but nothing feeds the
+query-string paging into them, so an out-of-range value produces an empty or
+clamped page rather than a validation failure. Validate paging arguments in the
+frontend, or expose them as explicit query arguments if the rule must be
+enforced.
 
 ## Which return shapes page
 

package/package/corpus/skills/cratis-arc-react-page/SKILL.md

@@ -15,21 +15,20 @@ This skill is verified against these exact package contracts:
 
 | Package | Version | Verified from |
 | --- | --- | --- |
-| `@cratis/components` | `3.0.0` | its package manifest and component sources |
-| `@cratis/arc` | `>=20.3.1 <23` | peer range declared by `@cratis/components@3.0.0` |
-| `@cratis/arc.react` | `>=20.3.1 <23` | peer range declared by `@cratis/components@3.0.0` |
-| `primereact` | `^11.0.0` | peer of `@cratis/components@3.0.0` |
-| `primeicons` | `^8.0.0` | peer of `@cratis/components@3.0.0` |
-| `react` | `^19.0.0` | peer of `@cratis/components@3.0.0` |
+| `@cratis/components` | `4.6.0` | its package manifest (`exports`, peers), `Source/DataPage/*`, `Source/DataTables/*`, `Source/Dialogs/*`, `Source/CommandDialog/*`, `Source/MIGRATION.md` |
+| `@cratis/arc` | `>=20.3.1 <23` | peer range declared by `@cratis/components@4.6.0` |
+| `@cratis/arc.react` | `>=20.3.1 <23` | peer range declared by `@cratis/components@4.6.0` |
+| `react` | `^19.0.0` | peer of `@cratis/components@4.6.0` |
 
 `@cratis/arc.react.mvvm` ships with `@cratis/arc.react` and is an explicit
 application dependency. Reverify before claiming another version.
 
 ## Import from subpaths, never the root barrel
 
-The root `@cratis/components` entry exports **namespaces**, not components —
-`import { DataPage } from '@cratis/components'` yields a namespace object whose
-component is `DataPage.DataPage`. Always import from the subpath:
+The root `@cratis/components` entry is **setup-only** — `CratisComponentsProvider`
+and its configuration types. `import { DataPage } from '@cratis/components'` is a
+compile error; the Components 3 root namespaces are gone. Always import from the
+subpath:
 
 ```tsx
 import { DataPage, MenuItem, Column } from '@cratis/components/DataPage';
@@ -45,18 +44,21 @@ import { DialogProps, DialogResult, useDialog } from '@cratis/arc.react/dialogs'
   regenerated the TypeScript proxies. Generated proxies carry a
   `**DO NOT EDIT** - This file is an automatically generated file.` header —
   fix the C# source and rebuild instead of editing one.
-- The app must mount `CratisComponentsProvider` (from
-  `@cratis/components/Common`) above every Cratis component. PrimeReact 11
-  resolves its configuration from a provider, so components fail without one.
-- The app must import the stylesheets explicitly; components no longer import
+- The app must mount `CratisComponentsProvider` (from the package root,
+  `@cratis/components`) above every Cratis component — it carries the locale,
+  the Components-owned labels and the toast region (`toaster`).
+- The app must import the stylesheets explicitly; components do not import
   their own CSS:
 
   ```ts
-  import '@cratis/components/tokens';   // the --cratis-* token layer
-  import '@cratis/components/styles';   // every component stylesheet
-  import '@cratis/components/theme';    // optional license-free baseline look
+  import '@cratis/components/tokens';   // the --cratis-* token seam
+  import '@cratis/components/styles';   // structural rules for every component
+  import '@cratis/components/theme';    // optional: the maintained baseline look
   ```
 
+  Components has no vendor UI dependency — do not install PrimeReact or an icon
+  font for it. Menu icons are React component types (`react-icons` works).
+
   See the **cratis-components-styling** skill for the full theming contract.
 
 ## Step 2 — The DataPage shell
@@ -81,9 +83,9 @@ export const AccountsPage = () => (
 );
 ```
 
-Only `DataPage.Columns` and `DataPage.MenuItems` exist as compound members.
-`MenuItem` and `Column` are **named exports** — there is no `DataPage.MenuItem`
-and no `DataPage.Column`. Pass `dataKey` whenever the read model has an
+`DataPage.Columns`, `DataPage.MenuItems` and `DataPage.MenuItem` are the
+compound members; `MenuItem` and `Column` are also **named exports** of the
+subpath (there is no `DataPage.Column`). Pass `dataKey` whenever the read model has an
 identity.
 
 See [data-page.md](references/data-page.md) for every prop, and
@@ -97,6 +99,7 @@ Menu items go in `<DataPage.MenuItems>`. `MenuItem` takes `command`, not
 string. `disableOnUnselected` greys the item out until a row is selected.
 
 ```tsx
+import { FaPencil, FaPlus } from 'react-icons/fa6';
 import { DataPage, MenuItem } from '@cratis/components/DataPage';
 import { useDialog } from '@cratis/arc.react/dialogs';
 import { CreateAccountDialog } from './CreateAccountDialog';
@@ -105,8 +108,8 @@ const [CreateAccountWrapper, showCreateAccount] = useDialog(CreateAccountDialog)
 
 <DataPage title='Accounts' query={AllAccounts} emptyMessage='No accounts yet.'>
     <DataPage.MenuItems>
-        <MenuItem label='Add account' icon={() => <i className='pi pi-plus' />} command={() => showCreateAccount()} />
-        <MenuItem label='Edit account' icon={() => <i className='pi pi-pencil' />} command={() => showEditAccount()} disableOnUnselected />
+        <MenuItem label='Add account' icon={FaPlus} command={() => showCreateAccount()} />
+        <MenuItem label='Edit account' icon={FaPencil} command={() => showEditAccount()} disableOnUnselected />
     </DataPage.MenuItems>
     <DataPage.Columns>
         <Column field='name' header='Name' />
@@ -146,9 +149,9 @@ export const CreateAccountDialog = () => {
 };
 ```
 
-Never put a raw PrimeReact control inside a command dialog for a command value —
-it bypasses the field wrapper, so validation never re-runs and the submit button
-stays disabled. Seed values that must be present for validity with
+Never put a raw control (a `Common` `TextInput`, a native `<input>`) inside a
+command dialog for a command value — it is not bound to the command, so
+validation never re-runs and the submit button stays disabled. Seed values that must be present for validity with
 `initialValues`, not `onBeforeExecute`.
 
 ## Step 5 — Confirming, and showing that work is in progress

package/package/corpus/skills/cratis-arc-react-page/references/data-page.md

@@ -5,19 +5,21 @@ optional details pane in one component. Import from
 `@cratis/components/DataPage`.
 
 ```tsx
+import { FaPlus } from 'react-icons/fa6';
 import { Column, DataPage, MenuItem } from '@cratis/components/DataPage';
 import type { IDetailsComponentProps } from '@cratis/components/DataPage';
 ```
 
 ## Compound members
 
-Exactly two static members exist:
+Three static members exist:
 
 - `DataPage.Columns` — wraps the `Column` elements.
 - `DataPage.MenuItems` — wraps the `MenuItem` elements.
+- `DataPage.MenuItem` — the same component as the named `MenuItem` export.
 
 `Column` and `MenuItem` are named exports of the same subpath. There is no
-`DataPage.Column` and no `DataPage.MenuItem`.
+`DataPage.Column`.
 
 ## `DataPageProps`
 
@@ -37,9 +39,10 @@ Exactly two static members exist:
 | `onRefresh` | `() => void` | invoked to re-fetch a snapshot query |
 | `actionsAriaLabel` | `string` | accessible name of the actions menubar, default `'Actions'` |
 | `tableClassName` | `string` | class on the inner table |
-| `tablePt` / `tablePtOptions` / `tableUnstyled` | PrimeReact pass-through | target the inner data table |
+| `tablePt` | `DataTableParts` | per-part attributes on the inner data table (`tablePtOptions`/`tableUnstyled` are accepted no-ops) |
 | `menubarClassName` | `string` | class on the action menubar |
-| `menubarPt` / `menubarPtOptions` / `menubarUnstyled` | PrimeReact pass-through | target the action buttons |
+| `menubarPt` | `ButtonParts` | per-part attributes on the action buttons (`menubarPtOptions`/`menubarUnstyled` are accepted no-ops) |
+| `paginatorPt` | `TablePaginatorParts` | per-part attributes on the paginator |
 | `clientFiltering` | `boolean` | **deprecated and a no-op** — do not use in new code |
 
 ## Snapshot versus observable
@@ -64,7 +67,7 @@ after a command succeeds.
 reads. Icons are usually a small inline component:
 
 ```tsx
-<MenuItem label='Add account' icon={() => <i className='pi pi-plus' />} command={() => showCreate()} />
+<MenuItem label='Add account' icon={FaPlus} command={() => showCreate()} />
 ```
 
 ## `IDetailsComponentProps<TDataType>`
@@ -99,7 +102,8 @@ declaration the table reads.
 | `showFilterMatchModes` | `boolean` |
 | `filterElement` | `(options: ColumnFilterElementOptions) => ReactNode` |
 | `filterLabels` | `Partial<ColumnFilterMenuLabels>` |
-| `selectionMode` | `'single' \| 'multiple'` |
+| `filterPt` | `ColumnFilterMenuParts` — parts of the filter popup |
+| `selectionMode` | `'single'` — the only implemented value; there is no checkbox multi-selection |
 | `style` / `className` | `React.CSSProperties` / `string` |
 | `headerStyle` / `headerClassName` | `React.CSSProperties` / `string` |
 | `bodyStyle` / `bodyClassName` | `React.CSSProperties` / `string` |
@@ -112,11 +116,11 @@ Use `body` for a computed or formatted cell:
 
 ## Type name caution
 
-`@cratis/components/DataPage` exports two different things called
-`ColumnProps` — the props of the `DataPage.Columns` wrapper and the re-exported
-column declaration props. Import `ColumnProps` from
-`@cratis/components/DataTables` when you need the column type, so the reference
-is unambiguous.
+`ColumnProps` from `@cratis/components/DataPage` is the **column declaration**
+type re-exported from `DataTables` (the explicit named re-export shadows the
+`DataPage.Columns` wrapper's own `ColumnProps`, which is not reachable from the
+subpath). Import it from `@cratis/components/DataTables` when you want the
+reference to say so.
 
 ## Layout
 

package/package/corpus/skills/cratis-arc-react-page/references/data-tables.md

@@ -40,7 +40,8 @@ Both components take the same prop names:
 | `globalFilterFields` | `string[] \| undefined` | enables the search box |
 | `defaultFilters` | `DataTableFilterMeta` | initial filter state |
 | `className` | `string` | |
-| `pt` / `ptOptions` / `unstyled` | PrimeReact pass-through | |
+| `pt` | `DataTableParts` | per-part attributes (`ptOptions`/`unstyled` are accepted no-ops) |
+| `paginatorPt` | `TablePaginatorParts` | per-part attributes on the paginator |
 | `paginatorClassName` | `string` | |
 | `paginatorAriaLabels` | paginator label overrides | localize the paginator |
 | `clientFiltering` | `boolean` | **deprecated and a no-op** |
@@ -58,7 +59,13 @@ Both components take the same prop names:
 </DataTableForQuery>
 ```
 
-## Paging
+## Paging, sorting and filtering scope
+
+Column sorting and filtering — and the search box — apply to the **currently
+loaded page**, not the complete result. Complete-result filtering and sorting
+belong in the query's arguments and in the server-side query, before paging;
+`clientFiltering` does not change this and is a deprecated no-op. Server totals
+remain authoritative for the paginator.
 
 Both tables page server-side through the Arc paging hooks with a fixed page
 size of 20 rows starting at page 0. The paginator renders only when the result

package/package/corpus/skills/cratis-arc-react-page/references/dialogs.md

@@ -1,7 +1,7 @@
 # Dialogs reference
 
 The Cratis dialog wrappers own command execution, validation timing, busy
-state, and footer buttons. Never import `Dialog` from `primereact/dialog`.
+state, and footer buttons. Never use a vendor or hand-rolled modal — dialogs are Components-owned.
 
 The **components** live in `@cratis/components`; the **hooks, enums, and
 context** live in `@cratis/arc.react/dialogs`. `@cratis/components` exports no
@@ -41,10 +41,11 @@ first two is the normal case. `showDialog(input?)` resolves to
 `[DialogResult, TResponse?]` when the dialog closes.
 
 Inside the dialog, prefer plain typed props for input and take `closeDialog`
-from `useDialogContext<TResponse>()`:
+from `useDialogContext<TRequest, TResponse>()` — the **first** type parameter is
+the request the dialog was shown with, the second the response it closes with:
 
 ```tsx
-const { request, closeDialog } = useDialogContext<AccountCreated>();
+const { request, closeDialog } = useDialogContext<object, AccountCreated>();
 closeDialog(DialogResult.Ok, response);
 ```
 
@@ -86,7 +87,7 @@ The most-used props:
 | `validateOnInit` | validate on mount so pre-filled invalid values show immediately |
 | `initialFocus` | which control receives focus when the dialog opens |
 | `dismissable` | X, Escape, and backdrop dismissal |
-| `pt` / `ptOptions` / `unstyled` | PrimeReact pass-through |
+| `pt` | `DialogParts` — per-part attributes (`backdrop`, `positioner`, `root`, `header`, `title`, `close`, `content`, `footer`, `confirm`, `cancel`); `ptOptions`/`unstyled` are accepted no-ops |
 
 `CommandDialog.Column` exists for multi-column layouts:
 
@@ -132,8 +133,8 @@ wrapper close. Do not use `onConfirm` as a result handler.
 
 Every user-entered command value must be bound through a `CommandForm` field
 from `@cratis/components/CommandForm` (also published as
-`@cratis/components/CommandForm/fields`, the same module). A raw PrimeReact
-control bypasses the field wrapper, so validation never re-runs and the submit
+`@cratis/components/CommandForm/fields`, the same module). A raw control (a
+`Common` `TextInput`, a native `<input>`) is not bound to the command, so validation never re-runs and the submit
 button stays disabled.
 
 The full catalog: `InputTextField`, `PasswordField`, `NumberField`,
@@ -173,7 +174,7 @@ property descriptors, with `exclude` for the ones you do not want:
 
 ```tsx
 export const RenameDialog = () => {
-    const { closeDialog } = useDialogContext<{ name: string }>();
+    const { closeDialog } = useDialogContext<object, { name: string }>();
     const [name, setName] = useState('');
 
     return (
@@ -197,9 +198,10 @@ when omitted, `isBusy` `false`, `okLabel` `'Ok'`, `cancelLabel` `'Cancel'`,
 Two behaviors worth knowing:
 
 - `resizable` is accepted for compatibility but has **no effect** — the
-  PrimeReact 11 headless dialog has no resize.
+  Components dialog has no resize.
 - Passing a custom node to `buttons` instead of a `DialogButtons` member
-  removes the header close control, disables Escape, and means `onClose`,
+  removes the header close control and disables Escape/backdrop dismissal
+  (unless you also pass `dismissable` explicitly), and means `onClose`,
   `onCancel`, and `onConfirm` are never invoked. Close through
   `useDialogContext().closeDialog(...)`, or set `dismissable` explicitly.
 

package/package/corpus/skills/cratis-arc-react-page/references/queries-and-commands.md

@@ -48,6 +48,30 @@ Guard rendering with `hasData` rather than checking `data.length` — a
 conditional query that has not fired returns an empty result with
 `hasData: false`.
 
+### Command success is not projection convergence
+
+A successful `CommandResult` means the events were **appended**. The read model a
+query reads is built by an observer that runs *after* that, so for a moment the
+command has succeeded and the query still answers from before it. Model the
+states separately instead of collapsing them into "loaded or not":
+
+| State | Signal | Render |
+| --- | --- | --- |
+| Not asked yet | `.when(false)` / `!isReady` | nothing, or the previous content |
+| Pending | `isPerforming`, or `hasData: false` **right after a command you just issued succeeded** | a skeleton — **never** "not found" |
+| Converged, empty | `hasData` with an empty `data` and no recent command | the designed empty state |
+| Converged, populated | `hasData` with items | the content |
+| Failed | `!isSuccess` / `hasExceptions` / `!isAuthorized` | the matching error affordance |
+| Stale refresh | `isPerforming` while `data` still holds the previous result | keep the old content, indicate refresh |
+
+Two consequences. After a create command, take the **window action on the
+command's success** (close the dialog, navigate to the new id) and let the list
+catch up — do not wait for the query to show the row before closing. And for a
+detail page opened on an id you just created, `hasData: false` is *pending*, not
+*missing*: an observable query (`ISubject<T>` on the backend, `.use()` here)
+resolves it the moment the projection lands, which is why observable reads are
+the default for anything a user changes and then looks at.
+
 ### Paging
 
 ```ts
@@ -196,5 +220,5 @@ query transport. Its props include `microservice`, `origin`, `basePath`,
 `apiBasePath`, `httpHeadersCallback` (merged into every request — bearer and
 tenant headers), `detailsType`, `queryTransportMethod`, `queryConnectionCount`,
 `queryDirectMode`, `observableQueryTransferMode`, and `queryCacheRetentionMs`.
-`QueryTransportMethod` and `ObservableQueryTransferMode` import from
-`@cratis/arc`; `Arc` imports from `@cratis/arc.react`.
+`QueryTransportMethod` imports from `@cratis/arc/queries`,
+`ObservableQueryTransferMode` from `@cratis/arc`; `Arc` imports from `@cratis/arc.react`.

package/package/corpus/skills/cratis-chronicle-cli-operations/SKILL.md

@@ -16,8 +16,10 @@ This skill is verified against these exact sources:
 
 | Package | Version | Purpose |
 | --- | --- | --- |
-| `Cratis.Cli` | `2.4.0` | the `cratis` command, its contexts, output formats, and command tree |
-| `Cratis.Chronicle` | `16.45.2` | the observer, partition, sequence, and job concepts the CLI reads |
+| `Cratis.Cli` | `3.2.0` | the `cratis` command, its contexts, output formats, and command tree |
+
+> Re-verified at `Cratis/cli` **v3.2.0** (originally written against 2.4.0): every command, branch, flag and output format this skill names exists there; the 2.x→3.x change is the Chronicle 17/18 wire migration plus new branches (`ai`, `arc`, `screenplay`, `prologue`, `llm`) this skill does not cover.
+| `Cratis.Chronicle` | `18.3.0` | the observer, partition, sequence, and job concepts the CLI reads |
 
 The CLI ships a **versioned machine-readable catalog of its own surface**, and
 that catalog is the authority for exact command names on the installed version:
@@ -110,7 +112,7 @@ error.
 | Is the server healthy at all? | `cratis chronicle diagnose` (exit code 3 when unhealthy) |
 | Why has this read model stopped updating? | `chronicle failed-partitions list --observer <id>` — the error is on the partition, not in the log |
 | An observer is quarantined — why? | `chronicle failed-partitions show <observer> <partition> --detailed`, with attempt history |
-| Did this event actually get appended? | `chronicle events get --event-type <type> --event-source-id <id>`, or `chronicle events tail` |
+| Did this event actually get appended? | `chronicle events get --event-type <type> --event-source-id <id>` (`events tail` returns only the highest sequence number — not a count, not the events) |
 | What is this event's shape in the store? | `chronicle event-types list`, then `chronicle event-types show <type>` |
 | Is this projection registered? | `chronicle projections list`, then `chronicle projections show <id>` |
 | What does the read model actually hold? | `chronicle read-models get <read-model> <key>`, or `read-models instances` |
@@ -165,16 +167,20 @@ Before any of them:
 
 ### Two confirmation traps
 
-**Confirmation prompts do not fire when stdout is not a terminal.** The CLI
-treats a non-interactive session as an implicit yes, so a destructive command
-run from a script, a pipeline, or an agent harness proceeds without `-y` and
-without asking. Never rely on the prompt as the safety mechanism — the
-authorization above is the safety mechanism.
-
-**Not every mutating command prompts, even interactively.** `jobs stop` and
-`jobs resume` describe themselves as prompting for confirmation, but no prompt
-exists in the implementation. `users add`, `applications add`, and
-`subscriptions add` do not prompt either.
+**Destructive commands fail closed outside a terminal.** Every command with a
+confirmation prompt — `observers replay`, `observers replay-partition`,
+`observers retry-partition`, `observers clear-quarantine`, `jobs stop`,
+`jobs resume`, `recommendations perform`, `recommendations ignore`,
+`users remove`, `applications remove`, `subscriptions remove` — asks
+interactively, and when the session is **not** interactive (a script, a
+pipeline, an agent harness) it does *not* proceed: it writes
+"Re-run the command with --yes to confirm the operation" and exits with the
+validation error code. `--yes` is therefore the only way a non-interactive run
+performs one of these, which makes `--yes` the authorization boundary. Declining
+the interactive prompt exits successfully having done nothing.
+
+**Additive commands do not prompt.** `users add`, `applications add` and
+`subscriptions add` run without confirmation in every mode.
 
 Reaching for `--yes` to silence a prompt you have not read is how the wrong
 store gets replayed. A failed partition you have not yet explained is not a

package/package/corpus/skills/cratis-chronicle-client-dotnet/SKILL.md

@@ -17,16 +17,18 @@ There is no host requirement and no application architecture imposed.
 ## Verified product sources
 
 This skill is verified against the `Cratis/Chronicle` repository at tag
-`v17.0.1`, whose client sources are byte-identical to `16.45.2` for every public
-type cited here except the compatibility check noted below.
+`v18.3.0`. Its client sources are unchanged in public shape since `v17.0.1`
+(the 17→18 client diff is converters, options and doc comments), and `v17.0.1`
+was byte-identical to `16.45.2` for every public type cited here except the
+compatibility check noted below.
 
 | Package | Line | Purpose |
 | --- | --- | --- |
-| `Cratis.Chronicle` | `17.x` | `ChronicleClient`, `IEventStore`, `[EventType]`, observers |
-| `Cratis.Chronicle.Connections` | `17.x` | `ChronicleConnectionString`, connection lifecycle |
-| `Cratis.Chronicle.AspNetCore` | `17.x` | ASP.NET Core wiring, header/subdomain namespace resolvers |
-| `Cratis.Chronicle.Testing` | `17.x` | in-process scenarios |
-| `Cratis.Chronicle.CodeAnalysis` | `17.x` | the analyzers, a **separate opt-in** package |
+| `Cratis.Chronicle` | `18.3.0` | `ChronicleClient`, `IEventStore`, `[EventType]`, observers |
+| `Cratis.Chronicle.Connections` | `18.3.0` | `ChronicleConnectionString`, connection lifecycle |
+| `Cratis.Chronicle.AspNetCore` | `18.3.0` | ASP.NET Core wiring, header/subdomain namespace resolvers |
+| `Cratis.Chronicle.Testing` | `18.3.0` | in-process scenarios |
+| `Cratis.Chronicle.CodeAnalysis` | `18.3.0` | the analyzers, a **separate opt-in** package |
 
 Take the exact version from nuget.org. The version in source is a `1.0.0`
 placeholder injected at pack time (`Source/Directory.Build.props`), so the
@@ -182,23 +184,23 @@ and an optional `EventStoreNamespaceResolverType`.
 Since Chronicle 17 the compatibility check is a server-side RPC, and **the client
 runs it automatically inside `Connect()`** —
 `Source/Clients/Connections/ChronicleConnection.cs:310` calls
-`CheckCompatibility` (`:405`), sending the client type, client version, protocol
-version, and the descriptor set its contracts package was built with (`:411-417`).
-The rationale is at `:400-404`: Chronicle has clients in four languages and only
+`CheckCompatibility` (`:414`), sending the client type, client version, protocol
+version, and the descriptor set its contracts package was built with (`:420-426`).
+The rationale is at `:409-413`: Chronicle has clients in four languages and only
 some can build a descriptor set at runtime, so each ships the one it was built
 with and the server does the single comparison.
 
 Behavior you can rely on:
 
 - A server too old to have the RPC answers `Unimplemented`, and the client falls
-  back to the previous client-side exchange (`:419-425`) — upgrading the client
+  back to the previous client-side exchange (`:428-434`) — upgrading the client
   does not silently drop the check.
-- Any other transport error is **logged and ignored** (`:426-432`), on the stated
+- Any other transport error is **logged and ignored** (`:435-441`), on the stated
   reasoning that failing to ask says nothing about whether the two sides agree.
 - A genuine mismatch throws `IncompatibleServerException`
   (`Source/Clients/Connections/IncompatibleServerException.cs:10`) whose message
   names the server address, its version, its protocol version, and the specific
-  incompatibilities (`:436-443`).
+  incompatibilities (`:443-449`).
 
 The client identifies itself as `".NET"`
 (`Source/Clients/Connections/ChronicleClientIdentity.cs:22`) with its assembly
@@ -333,8 +335,8 @@ Read models are queried through `eventStore.ReadModels`
 Artifacts are found by **assembly scanning**, with no registration call and no DI
 container required. `DefaultClientArtifactsProvider.Default` composes the
 project-referenced and package-referenced assemblies
-(`Source/Clients/DotNET/DefaultClientArtifactsProvider.cs:35`), and the
-predicates are exactly (`:230-238`):
+(`Source/Clients/DotNET/DefaultClientArtifactsProvider.cs:37`), and the
+predicates are exactly (`:242-251`):
 
 | Kind | Predicate |
 | --- | --- |