@cratis/pi 2.22.0 → 2.23.0

package/package/corpus/skills/cratis-chronicle-reactor/SKILL.md

@@ -24,8 +24,8 @@ This skill is verified against these exact sources:
 
 | Package | Version | Purpose |
 | --- | --- | --- |
-| `Cratis.Chronicle` | `16.45.2` | `Cratis.Chronicle.Reactors`, `Cratis.Chronicle.Reactors.SideEffects`, `Cratis.Chronicle.EventSequences`, `Cratis.Chronicle.Events` |
-| `Cratis.Chronicle.CodeAnalysis` | `16.45.2` | `CHR0004`, `CHR0005`, `CHR0008`, `CHR0013`, `CHR0022`, `CHR0031`, `CHR0032` |
+| `Cratis.Chronicle` | `18.3.0` | `Cratis.Chronicle.Reactors`, `Cratis.Chronicle.Reactors.SideEffects`, `Cratis.Chronicle.EventSequences`, `Cratis.Chronicle.Events` |
+| `Cratis.Chronicle.CodeAnalysis` | `18.3.0` | `CHR0004`, `CHR0005`, `CHR0008`, `CHR0013`, `CHR0022`, `CHR0031`, `CHR0032` |
 
 Reverify product sources before claiming support for another version.
 
@@ -280,19 +280,33 @@ selection, a reactor or a reducer is where it happens.
 ## Translation via a command
 
 A translation that adapts one area's events into another's intent runs a command
-rather than appending directly. `ICommandPipeline` is an **Arc** type
-(`Cratis.Arc.Commands`), not a Chronicle one:
+rather than appending directly. With the Arc Chronicle integration the handler
+**returns** the command — the same shape as returning an event — and Arc executes
+it through validation and authorization; a denied, invalid or throwing result is a
+side-effect failure that fails the partition rather than being dropped:
 
 ```csharp
-using Cratis.Arc.Commands;
+using Cratis.Arc.Chronicle.Reactors;
 
-public class <ReactorName>(ICommandPipeline commandPipeline) : IReactor
+[ExecuteCommandsAsSystem("<role the command requires>")]   // only when the command is [Roles]/[Authorize]-gated
+public class <ReactorName> : IReactor
 {
-    public async Task <MethodName>(<EventName> @event, EventContext context) =>
-        await commandPipeline.Execute(new <CommandName>(@event.<Property>));
+    [OnceOnly]
+    public Task<<CommandName>> <MethodName>(<EventName> @event, EventContext context) =>
+        Task.FromResult(new <CommandName>(@event.<Property>));
 }
 ```
 
+A reactor runs with **no principal**; `[ExecuteCommandsAsSystem]` (class-level,
+`Cratis.Arc.Chronicle.Reactors`) supplies one for the **returned** commands only.
+A collection return is executed as commands when every element is a command.
+
+The imperative form — inject `ICommandPipeline` (`Cratis.Arc.Commands`) and call
+`Execute(command)` — is still supported and is the subject of the
+**cratis-arc-command-execution** skill. It needs `[OnceOnly]` as well (`ARCCHR0006`
+warns), the `CommandResult` must be inspected, and `[ExecuteCommandsAsSystem]`
+does not cover it.
+
 ## Failure behavior
 
 If a handler throws, or a returned side-effect event fails to append — a

package/package/corpus/skills/cratis-chronicle-read-model/SKILL.md

@@ -23,7 +23,7 @@ This skill is verified against these exact sources:
 
 | Package | Version | Purpose |
 | --- | --- | --- |
-| `Cratis.Chronicle` | `16.45.2` | `Cratis.Chronicle.Events`, `Cratis.Chronicle.Keys`, `Cratis.Chronicle.ReadModels` |
+| `Cratis.Chronicle` | `18.3.0` | `Cratis.Chronicle.Events`, `Cratis.Chronicle.Keys`, `Cratis.Chronicle.ReadModels` |
 | `Cratis.Arc.Core` | current | `Cratis.Arc.Queries.ModelBound.ReadModelAttribute` and `PathAttribute` |
 | `Cratis.Arc.MongoDB` | current | the `Observe` family of `IMongoCollection<T>` extensions |
 

package/package/corpus/skills/cratis-chronicle-read-model/references/queries.md

@@ -1,7 +1,7 @@
 # Read-model queries
 
 Verified against `Cratis.Arc.Core` and `Cratis.Arc.MongoDB` as checked out
-alongside `Cratis.Chronicle` `16.45.2`. Confirm the exact Arc package version in
+alongside `Cratis.Chronicle` `18.3.0`. Confirm the exact Arc package version in
 the consuming project before citing one.
 
 ## Where the pieces live

package/package/corpus/skills/cratis-chronicle-read-model-specifications/SKILL.md

@@ -17,9 +17,11 @@ separate `When`: seeding the events is what makes the projection run.
 
 | Package | Version | Purpose |
 | --- | --- | --- |
-| `Cratis.Chronicle.Testing` | `16.45.2` | `ReadModelScenario<TReadModel>` and its `Given` builder |
+| `Cratis.Chronicle.Testing` | `18.3.0` | `ReadModelScenario<TReadModel>` and its `Given` builder |
 | `Cratis.Specifications.XUnit` | `4.x` | The `Specification` base and the `ShouldXxx` assertions |
 
+> 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.
+
 ```bash
 dotnet add package Cratis.Chronicle.Testing
 ```

package/package/corpus/skills/cratis-chronicle-reducer/SKILL.md

@@ -17,7 +17,7 @@ This skill is verified against this exact source:
 
 | Package | Version | Purpose |
 | --- | --- | --- |
-| `Cratis.Chronicle` | `16.45.2` | `Cratis.Chronicle.Reducers`, `Cratis.Chronicle.ReadModels`, `Cratis.Chronicle.Events` |
+| `Cratis.Chronicle` | `18.3.0` | `Cratis.Chronicle.Reducers`, `Cratis.Chronicle.ReadModels`, `Cratis.Chronicle.Events` |
 
 Reverify product sources before claiming support for another version.
 

package/package/corpus/skills/cratis-chronicle-web-workbench/SKILL.md

@@ -22,7 +22,7 @@ This skill is verified against this exact source:
 
 | Package | Version | Purpose |
 | --- | --- | --- |
-| `Cratis.Chronicle` | `16.45.2` | the Workbench application, its hosting, screens, and commands |
+| `Cratis.Chronicle` | `18.3.0` | the Workbench application, its hosting, screens, and commands |
 
 Reverify before claiming a screen, route, command, or configuration key for
 another version.
@@ -72,7 +72,9 @@ Read these before putting a Workbench on any reachable network.
 - The server is designed to sit behind a proxy and trusts the immediate proxy's
   forwarded headers unconditionally. That is only safe when the proxy is the
   only route in.
-- The health endpoint and the connection-count endpoints answer anonymously.
+- The health endpoint, the antiforgery probe, the gRPC descriptor-set and
+  compatibility calls, the initial-admin-password endpoints, and the gRPC
+  `ResetKernelState` call answer anonymously (`[AllowAnonymous]`).
 
 ## The screens
 
@@ -80,16 +82,18 @@ Routes are grouped by scope. Event-store-scoped screens apply to the whole
 store; namespace-scoped screens apply to one tenant namespace.
 
 **Namespace-scoped:** Recommendations (the landing screen) · Jobs · Sequences ·
-Pivot (experimental) · Behavior patterns · Pattern heatmap · Observers · Failed
-partitions · Read Models · Identities · Seed Data.
+Pivot · Patterns · Pattern heatmap · Observers · Failed partitions · Read Models ·
+Identities · Seed Data.
 
 **Event-store-scoped:** Event Types · Read Model Types · Webhooks · External
-Services · Captures · Projections · Namespaces · Seed Data.
+Services · Captures · Projections (namespace-routed) · Namespaces · Seed Data.
 
-**System:** Users · Applications · Connected Clients · Development Tools.
+**System:** Users · Applications · Connected Clients · Servers · Development
+Tools (offered only when the server reports them available).
 
-Reducers, Reactors, and Sinks have routes but no menu entry. A Dashboard exists
-in the source but is fully disabled — it is not a shipping screen.
+Reducers, Reactors, Sinks and a store-wide Sequences view have routes but no menu
+entry (their menu lines are commented out in `EventStore.tsx`). There is no
+Dashboard screen; only a `Card`/`Chart` component pair written for one remains.
 
 ## What each screen can change
 
@@ -125,9 +129,13 @@ partition, stop/resume/delete job, and perform recommendation all fire on the
 first click. Decide before clicking, not after.
 
 **Reset kernel state is the most destructive operation in the product.** It is
-gated three ways — the endpoint exists only in development builds, the screen
-reports itself unavailable when the server says so, and a confirmation dialog
-guards the button. Never run it against a store whose data anyone still needs.
+gated three ways — the *operation* is compiled in only for development builds
+(`KernelStateResetter.IsAvailable`; in any other build the gRPC call still exists,
+answers anonymously, and is a no-op), the screen reports itself unavailable when
+the server says so, and a confirmation dialog guards the button. Never run it
+against a store whose data anyone still needs, and never assume a production
+build is protected by authentication here — it is protected by the operation
+not being there.
 
 ## Redaction and revision
 

package/package/corpus/skills/cratis-cli-terminal-workbench/SKILL.md

@@ -24,7 +24,9 @@ This skill is verified against this exact source:
 
 | Package | Version | Purpose |
 | --- | --- | --- |
-| `Cratis.Cli` | `2.4.0` | `cratis chronicle workbench`, its views, keys, and actions |
+| `Cratis.Cli` | `3.2.0` | `cratis chronicle workbench`, its views, keys, and actions |
+
+> Re-verified at `Cratis/cli` **v3.2.0**: the fifteen navigation views and every key binding below exist in `Source/Cli/Commands/Chronicle/Workbench` at that tag.
 
 Reverify before claiming a view, key binding, or action for another version.
 `cratis chronicle workbench --help` and `cratis llm-context` are the authority
@@ -61,9 +63,11 @@ The navigation pane groups fifteen views into five sections:
 | Projections | Projections · Read Models |
 | Server | Event Stores · Namespaces · Applications · Users · Identities · Subscriptions |
 
-Six further detail views — observer, failed partition, event, event type,
-projection, and read model — open from a row and never appear in the navigation
-pane.
+Every table view renders a detail for its selected row — `RenderDetail` is
+abstract on the shared `FilterableTableView`, so activating a row always
+surfaces its full detail in the detail pane or a centered overlay; the event
+and read-model views open richer overlays of their own. Detail views never
+appear in the navigation pane.
 
 Each refresh fetches one consistent snapshot of the store: version info, event
 stores, namespaces, observers, failed partitions, jobs, recommendations, event
@@ -127,8 +131,9 @@ Several views bind a key to an operation that changes the running server:
 Each has a bulk form that applies to every checked row.
 
 Every one of these opens a centered confirmation modal that states the action
-cannot be undone, confirmed with `Enter` or `Y` and cancelled with `Escape` or
-`N`. **That modal is not authorization.** A request to inspect a live store does
+cannot be undone. **Only an explicit `Y` (or the Confirm button) confirms;
+`Enter`, `Escape` and `N` all cancel** — the modal is cancel-focused on purpose,
+so a reflexive Enter never runs a destructive action. **That modal is not authorization.** A request to inspect a live store does
 not authorize replay, retry, stop, resume, perform, or ignore. Before pressing
 one of those keys:
 

package/package/corpus/skills/cratis-code-review/SKILL.md

@@ -18,9 +18,11 @@ change did not touch is a note, never a blocker.
 
 | Package | Version | Purpose |
 | --- | --- | --- |
-| `Cratis.Arc.Core` | `22.10.4` | Command, query, validation and analyzer surface (`ARC0001`–`ARC0015`) |
-| `Cratis.Chronicle` | `16.45.2` | Event, projection, read-model and constraint surface |
-| `Cratis.Fundamentals` | `7.18.2` | `ConceptAs<T>`, `IInstancesOf<T>`, the DI conventions |
+| `Cratis.Arc.Core` | `22.16.0` | Command, query, validation and analyzer surface (`ARC0001`–`ARC0015` in `DiagnosticDescriptors`, plus `ARC0016`–`ARC0018` from the command-operation analyzer) |
+| `Cratis.Chronicle` | `18.3.0` | Event, projection, read-model and constraint surface |
+| `Cratis.Fundamentals` | `7.19.2` | `ConceptAs<T>`, `IInstancesOf<T>`, the DI conventions |
+
+> 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 asserting a framework
 contract this file does not already state.
@@ -97,9 +99,9 @@ there is nothing to review under a red build.
 - No `@ts-ignore` or `@ts-expect-error` without a comment saying why.
 - Full descriptive names — never `e`, `idx`, `prev`, `dir`, `pos`.
 - `CommandDialog` from `@cratis/components/CommandDialog` for command dialogs;
-  `Dialog` from `@cratis/components/Dialogs` for data-only dialogs. **Never**
-  `Dialog` from `primereact/dialog`.
-- No hard-coded hex or rgb colors — PrimeReact CSS variables only. No
+  `Dialog` from `@cratis/components/Dialogs` for data-only dialogs. **Never** a
+  vendor or hand-rolled modal.
+- No hard-coded hex or rgb colors — `--cratis-*` tokens only. No
   `!important` without a justifying comment.
 - Components live in the slice folder. No barrel `index.ts` that re-exports one
   component, and no technical `hooks/` / `utils/` / `types/` grouping at feature

package/package/corpus/skills/cratis-components-accessibility/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cratis-components-accessibility
-description: Apply the accessibility conventions Cratis Components actually implements — dialog initial-focus discipline and the armed-Enter hazard, supplying every accessible name as a localizable prop, putting the accessible name on the focusable element rather than the wrapper, and using the PrimeReact pass-through prop to strip invalid ARIA. Use when building or reviewing a dialog, a form control, a data table, a toast, or any component whose accessible name is currently a hard-coded English string. Do not use as a general WCAG conformance guide.
+description: Apply the accessibility conventions Cratis Components 4 actually implements — dialog initial-focus discipline and the armed-Enter hazard, supplying every accessible name as a localizable prop or provider message, putting the accessible name on the focusable element rather than the wrapper, keeping decorative icons hidden, and customizing through parts without fighting the component's own ARIA. Use when building or reviewing a dialog, a form control, a data table, a toast, or any component whose accessible name is currently a hard-coded English string. Do not use as a general WCAG conformance guide.
 license: MIT
 ---
 
@@ -17,8 +17,11 @@ what is written here.
 
 | Package | Version | Verified from |
 | --- | --- | --- |
-| `@cratis/components` | `3.0.0` | its component sources and specifications |
-| `primereact` | `^11.0.0` | peer of `@cratis/components@3.0.0` |
+| `@cratis/components` | `4.6.0` | `Source/Dialogs/*` (`DialogInitialFocus`, `DialogImplementation`), `Source/CommandForm/fields/fieldAccessibility.tsx`, `Source/for_accessibility/*`, `Source/SchemaEditor/*`, `Source/ObjectNavigationalBar/*`, `Source/MIGRATION.md`, `Documentation/Styling/pass-through.md`, `Documentation/Common/cratis-components-provider.md`, `Documentation/renderers/index.md` |
+
+Focus, overlay and collection behavior come from React Aria **internally** — the
+dialog is a React Aria `Modal` inside a `ModalOverlay`; you never import React
+Aria yourself, and its class names are not a styling or testing hook.
 
 ## 1. Dialog focus discipline
 
@@ -58,119 +61,146 @@ read anything.
 `Cancel` degrades to `Content` automatically when the chosen button set has
 nothing to dismiss with, so it is always safe to ask for.
 
-`DialogInitialFocus` imports from `@cratis/components/Dialogs`.
+`DialogInitialFocus` imports from `@cratis/components/Dialogs`. While `isBusy`
+is set the dialog marks its content `inert` and disables every dismissal path,
+so a user cannot interact with a half-committed form.
 
-## 2. Every accessible name is a prop — and never a baked-in English string
+## 2. Every accessible name is a prop or a provider message — never a baked-in English string
 
 This is the library's strongest and most consistent convention: any string a
-screen reader will read is exposed as an overridable, localizable prop. Set it.
-
-| Component | Prop |
-| --- | --- |
-| `Dialog` (and `CommandDialog`) | `closeAriaLabel` — default `'Close'` |
-| `DataPage` | `actionsAriaLabel` — default `'Actions'` |
-| `DataTableForQuery` / `DataTableForObservableQuery` | `paginatorAriaLabels` |
-| `Column` (filter menu) | `filterLabels` — trigger name, clear, apply, true, false |
-| `Toaster` | `dismissAriaLabel` — default `'Dismiss'` |
-| `Dropdown` | `aria-label`, `aria-labelledby`, `aria-describedby` |
-| `SchemaEditor` | `labels` — ten strings, five of them accessible names |
-| `ObjectNavigationalBar` | `backLabel` — tooltip **and** accessible name |
-| `ToolbarButton` | `title` — required; the accessible name and the tooltip |
-| `ToolbarFanOutItem` | `tooltip` — required |
-| `RatingField` | `starAriaLabel` |
-| `ChipsField` | `removeAriaLabel` |
-
-Where the library can resolve a name from a locale it does — the table
-paginator reads its navigation labels from the PrimeReact locale rather than
-hard-coding them, and the busy-indicator dialog names its progress indicator
-from the consumer-supplied, already-localized message. Follow that pattern:
-**never bake an English accessible name into application code.**
+screen reader will read is exposed as an overridable, localizable prop, and the
+library-wide ones also come from `CratisComponentsProvider`'s `messages`. The
+precedence is always the same: **a named component prop wins, then the matching
+provider message, then the English default.** Set the provider messages once for
+the application's locale, and the per-instance props where one control needs a
+different name.
+
+| Component | Prop | Provider message |
+| --- | --- | --- |
+| `Dialog` / `CommandDialog` / `StepperCommandDialog` | `closeAriaLabel`; `okLabel`, `cancelLabel`, `yesLabel`, `noLabel` | `messages.dialog` (`ok`, `cancel`, `yes`, `no`, `close`) |
+| `CommandStepper` / `StepperCommandDialog` | `nextLabel`, `previousLabel` | `messages.stepper` (`next`, `previous`, `submit`) |
+| `DataPage` | `actionsAriaLabel`, `globalSearchAriaLabel`, `paginatorAriaLabels` | `messages.dataTable`, `messages.paginator` |
+| `DataTableForQuery` / `DataTableForObservableQuery` | `paginatorAriaLabels` | `messages.paginator` (`navigation`, `first`, `previous`, `next`, `last`) |
+| `Column` (filter menu) | `filterLabels` — match mode, clear, apply, true, false | `messages.columnFilter` |
+| `Toaster` | `dismissAriaLabel` | `messages.notifications` (`dismiss`, `region`) |
+| `Dropdown` | `aria-label`, `aria-labelledby`, `aria-describedby` | `messages.dropdown` (`showOptions`, `clearSelection`) |
+| `DatePickerInput` / `CalendarField` | `aria-label` / `aria-labelledby` for the segmented **group**; `todayLabel`, `clearLabel` | `messages.datePicker` (`today`, `clear`, `openCalendar`, `previousMonth`, `nextMonth`, `label`) |
+| Every CommandForm field | `aria-label` (falls back to the field `title`), `aria-describedby`, `id` | — |
+| `SchemaEditor` | `labels` | — |
+| `ObjectNavigationalBar` | `backLabel` — tooltip **and** accessible name | — |
+| `ToolbarButton` | `title` — required; the accessible name and the tooltip | — |
+| `Toolbar` | `aria-label` | `messages.toolbar` (`label`, default `'Tools'`) |
+| `ToolbarFanOutItem` / `ToolbarFolder` | `tooltip` / `title` — required | — |
+| `RatingField` | `starAriaLabel` | — |
+| `ChipsField` | `removeAriaLabel` | — |
 
 In a localized application, treat any component whose accessible name you have
-not supplied as a defect.
+not supplied — and any provider message group left at its English default — as
+a defect.
 
 ## 3. Put the name on the focusable element, not the wrapper
 
 An accessible name has to land on the element that actually receives focus and
-carries the role. `Dropdown` demonstrates the rule: `id`, `tabIndex`, and all
-three ARIA attributes route to the combobox trigger, not to the layout wrapper,
-and the control id is deliberately not duplicated onto the wrapper so an
-external `<label htmlFor>` associates correctly.
+carries the role. `Dropdown` demonstrates the rule: `id` and the `aria-*`
+attributes route to the **trigger** (`data-cratis-part='trigger'`), not to the
+layout wrapper, and the control id is deliberately not duplicated onto the
+wrapper so an external `<label htmlFor>` associates correctly. A single select
+follows the button/listbox pattern and a filtered one is a combobox — so in a
+test, query the trigger by its accessible name or its part, **not** by
+`role="combobox"`.
 
 ```tsx
 <label htmlFor='role'>Advisory role</label>
 <Dropdown id='role' value={role} options={roles} aria-describedby='role-help' />
 ```
 
+`DatePickerInput` is a segmented field: its `id` identifies the **focus group**,
+not a native text input, so name it with `aria-label`/`aria-labelledby` on the
+group. `Tooltip` enhances exactly one real focusable child so focus, hover and
+`aria-describedby` stay together — wrap text, fragments or several siblings in
+one native control first. Several `RadioButtonField`s bound to one property need
+the same explicit `name` for native arrow-key group navigation.
+
 Apply the same rule to your own wrapper components: forward `id`, `tabIndex`,
 and `aria-*` down to the focusable child rather than putting them on a
 container.
 
-## 4. Decorative icons are hidden
-
-Icons and loading spinners inside a labelled control are marked
-`aria-hidden='true'` so a button's accessible name is exactly its label and not
-"pi pi-plus Add account". Do the same in application components: an icon that
-sits beside a text label carries no information of its own.
+## 4. Field errors are announced — do not duplicate them
 
-## 5. Use pass-through to strip invalid ARIA
+Every CommandForm field runs its title and validation messages through one
+helper: the control's accessible name falls back to the field `title`, and when
+the field has errors a visually hidden `<span id="…-errors">` is rendered and
+linked from the control's `aria-describedby` (merged with any `aria-describedby`
+you pass). Arc renders the visible error text; the hidden span exists only for
+assistive technology. Do **not** render a second announcement or wire your own
+`aria-describedby` to the visible error — you would announce it twice.
 
-Setting a pass-through value to `undefined` **removes** that attribute. Cratis
-Components uses this deliberately where PrimeReact 11 emits ARIA that is invalid
-or points at ids it never renders — for example removing `aria-sort` from a sort
-control that carries `role="button"`, and removing `role` and `aria-controls`
-from stepper headers whose referenced panels have no matching ids.
+## 5. Decorative icons are hidden
 
-```tsx
-pt={{ root: { role: undefined, 'aria-controls': undefined } }}
-```
+Icons and loading spinners inside a labelled control are marked
+`aria-hidden='true'` so a button's accessible name is exactly its label and not
+the icon's text. Do the same in application components: an icon that sits beside
+a text label carries no information of its own (`<FaPlus aria-hidden='true' />`).
 
-Reach for this when an upstream primitive emits an attribute that is wrong for
-the element it lands on. Removing a broken role usually leaves a natively
-keyboard-accessible element behind, which is better than a role that lies.
+## 6. Customize through parts without fighting the component's ARIA
 
-## 6. Prefer an invalid state over an invalid attribute
+Parts (`pt` and `data-cratis-part`) are for **presentation**. The component owns
+the role, the name and the state attributes on its elements: *named behavior
+props override conflicting part attributes*, so a `role` or `aria-*` value you
+push through `pt` onto a part the component already labels is either overridden
+or produces two competing semantics. Put identity and ARIA on the documented
+behavior props (§2, §3) and keep `pt` to `className`, `style` and data
+attributes. State is expressed through valid ARIA plus a data attribute
+(`aria-invalid` + `data-invalid`, `data-disabled`, `data-selected`) — express your
+own component state the same way, never through made-up attributes.
 
-Where a control needs to express invalidity, the library translates it to
-`aria-invalid` plus a data attribute rather than forwarding an attribute the DOM
-would reject. Follow that: express state through valid ARIA, not through
-made-up attributes.
+One focus lifecycle per interactive surface: never nest a second modal or focus
+trap inside a Components dialog to borrow another look, and never combine two
+keyboard-selection owners for one control. A presentation adapter must preserve
+the Components contract without adding a second semantic control.
 
-## What Cratis Components does **not** give you
+## What Cratis Components does — and does not — give you
 
 Be accurate about this — over-promising accessibility is worse than saying
 nothing.
 
-- **No accessibility linting or scanning is configured.** The library's ESLint
-  configuration has no `jsx-a11y` plugin, and no axe or Storybook
-  accessibility addon is installed. There is **no automated accessibility gate**
-  in the quality gates. Any accessibility claim comes from a manual audit.
-- **The schema editors, the object content editor, and the object navigational
-  bar are click-only.** Their breadcrumbs and drill-in affordances are plain
-  elements with click handlers — no role, no `tabIndex`, no key handling. Do not
-  document keyboard navigation for them.
-- **Field-level error text is not wired to its input.** A validation message
-  shown beside a field is not associated through `aria-describedby` or
-  `aria-errormessage`. If your application needs that association, add it in the
-  application component.
-- **There is no focus trap, roving tabindex, skip link, or live region** beyond
-  what the dialog and the PrimeReact primitives provide.
-- Some existing Cratis Components documentation describes keyboard shortcuts and
-  ARIA support for the schema editor and the navigational bar that the code does
-  not implement. Verify against the component source before repeating any such
-  claim.
+- **There is an automated scan, on representative surfaces.** The library runs
+  `axe-core` (WCAG 2 A and AA rules) over a set of representative foundation
+  surfaces in its own specs, and Storybook carries the accessibility addon. That
+  proves those surfaces have no *automated* violations; it is not a conformance
+  certification, it does not cover every component, and it cannot see keyboard
+  order, focus restoration, screen-reader phrasing or color relationships the
+  product introduces.
+- **Modal focus management is real**: focus moves in per §1, the backdrop and the
+  document behind are handled by the React Aria modal, Escape and backdrop
+  dismissal follow `dismissable`, and busy content is `inert`. Verify keyboard
+  order, initial focus, focus restoration and screen-reader output in the
+  application's supported browsers and assistive technologies — Components does
+  not certify them for you.
+- **Breadcrumbs and drill-ins in `SchemaEditor`, `ObjectContentEditor` and
+  `ObjectNavigationalBar` are native `<button>`s** (with `aria-current` on the
+  current crumb), so they are focusable and keyboard-activatable. Anything beyond
+  that — shortcut keys, arrow-key grid navigation — is not implemented; verify
+  against the component source before documenting it.
+- **A custom design still owns visible focus, contrast, target size, reduced
+  motion, forced colors and responsive behavior.** Components supplies semantic
+  behavior and the `--cratis-focus-ring` token; it cannot infer the product's
+  color relationships.
+- **No skip links, roving-tabindex utilities or live regions** for application
+  layouts beyond the toast region (`messages.notifications.region` names it).
 
 ## Verify
 
 - Every dialog whose confirm action is destructive or irreversible sets
   `initialFocus` to `DialogInitialFocus.Cancel` or `Content`.
-- No accessible name in application code is a hard-coded English string — each
-  comes from the component's label prop, resolved from the application's
-  locale.
+- `CratisComponentsProvider` carries the locale and every `messages` group the
+  application renders; no accessible name in application code is a hard-coded
+  English string.
 - `id`, `tabIndex`, and `aria-*` on a wrapper component reach the focusable
-  child, not the container.
+  child, not the container; a `DatePickerInput` is named on its group.
 - Icons beside a text label are `aria-hidden`.
-- Any ARIA attribute removed from an upstream primitive is removed through
-  pass-through `undefined`, with a comment saying why.
-- No claim of keyboard support, automated accessibility scanning, or WCAG
-  conformance is made that the source does not back.
+- No `role`/`aria-*` is injected through `pt`; no CSS or test targets a React Aria
+  class name.
+- Field errors are not announced twice.
+- No claim of keyboard support, automated coverage, or WCAG conformance is made
+  that the source does not back.

package/package/corpus/skills/cratis-components-schema-editor/SKILL.md

@@ -21,9 +21,8 @@ case where the shape itself is data.
 
 | Package | Version | Verified from |
 | --- | --- | --- |
-| `@cratis/components` | `3.0.0` | its package manifest and the `SchemaEditor` / `ObjectContentEditor` sources |
-| `primereact` | `^11.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 and the `SchemaEditor` / `ObjectContentEditor` sources |
+| `react` | `^19.0.0` | peer of `@cratis/components@4.6.0` |
 
 ## The schema type these editors consume
 
@@ -147,10 +146,11 @@ among its siblings. Save is disabled while any name is invalid.
 
 ### Localization
 
-`SchemaEditorLabels` has ten fields, five of them accessible names:
-`edit`, `save`, `cancel`, `addProperty`, `actions`, `navigateBack`,
-`emptyMessage`, `navigateToItemDefinition`, `navigateToProperties`,
-`deleteProperty`. Pass `labels` with the ones you want to change — they merge
+`SchemaEditorLabels` has fourteen fields, nine of them accessible names:
+menu actions `edit`, `save`, `cancel`, `addProperty`; accessible names `actions`,
+`navigateBack`, `navigateToItemDefinition`, `navigateToProperties`,
+`propertyName`, `propertyType`, `arrayItemType`, `deleteProperty`; and the
+messages `emptyMessage`, `invalidJson`. Pass `labels` with the ones you want to change — they merge
 over the English defaults. Never rely on the built-in English strings in a
 localized application.
 
@@ -218,9 +218,11 @@ name — localize it). It is click-only, like the editors' own breadcrumbs.
 
 ## Styling
 
-Both editors expose `className` only. Restyle their internals through a global
-PrimeReact pass-through preset on the provider rather than per instance — see
-the **cratis-components-styling** skill.
+Both editors expose `className` only — no `pt`. Restyle their internals with CSS
+scoped under that class, reaching the controls they render (buttons, inputs,
+the embedded `Dropdown`) through their `data-cratis-part` values and the
+`--cratis-*` tokens; there is no global provider pass-through in Components 4 —
+see the **cratis-components-styling** skill.
 
 ## Verify
 

package/package/corpus/skills/cratis-components-stepper-command-dialog/SKILL.md

@@ -14,9 +14,8 @@ field across every step is valid.
 
 | Package | Version | Verified from |
 | --- | --- | --- |
-| `@cratis/components` | `3.0.0` | its package manifest and `CommandDialog` sources |
-| `@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` |
+| `@cratis/components` | `4.6.0` | its package manifest, `Source/CommandDialog/*` (`StepperCommandDialog`, `CommandStepper`, `StepperPanel`), `Documentation/StepperCommandDialog/*`, `Documentation/CommandStepper/*` |
+| `@cratis/arc.react` | `>=20.3.1 <23` | peer range declared by `@cratis/components@4.6.0` |
 
 ## Choose it over `CommandDialog` when
 
@@ -84,7 +83,7 @@ import { useDialog } from '@cratis/arc.react/dialogs';
 
 const [CreateProjectWrapper, showCreateProject] = useDialog(CreateProjectDialog);
 
-<MenuItem label='New project' icon={() => <i className='pi pi-plus' />} command={() => showCreateProject()} />
+<MenuItem label='New project' icon={FaPlus} command={() => showCreateProject()} />   // icon is a component type, e.g. from 'react-icons/fa6'
 <CreateProjectWrapper />
 ```
 
@@ -155,8 +154,6 @@ Stepper-level props (inherited from the stepper customization surface):
 | `orientation` | `'horizontal' \| 'vertical'` | `'horizontal'` |
 | `headerPosition` | `'top' \| 'bottom'` | `'top'` |
 | `linear` | `boolean` | `true` |
-| `showNavigation` | `boolean` | `true` |
-| `showSubmit` | `boolean` | `true` |
 | `start` / `end` | `React.ReactNode` | extra content beside the step headers |
 | `onChangeStep` | `(event: { index: number }) => void` | — |
 
@@ -164,12 +161,14 @@ Command-form props (`initialValues`, `currentValues`, `validateOn`,
 `validateOnInit`, `onSuccess`, `onValidationFailure`, `onFailed`,
 `autoServerValidate`, …) all apply as well.
 
-### Two pass-through targets
+### Two part targets
 
-The inherited `pt`, `ptOptions`, and `unstyled` target the **inner stepper**.
-Use `dialogPt`, `dialogPtOptions`, `dialogUnstyled`, and `dialogClassName` to
-reach the **outer dialog**. Getting these the wrong way round is the usual cause
-of a pass-through that appears to do nothing.
+The inherited `pt` (`StepperParts`: `root`, `list`, `step`, `header`, `number`,
+`title`, `separator`, `panels`, `panel`) targets the **inner stepper**. Use
+`dialogPt` (`DialogParts`) and `dialogClassName` to reach the **outer dialog**.
+Getting these the wrong way round is the usual cause of a `pt` that appears to do
+nothing. (`ptOptions`/`unstyled` and their `dialog*` twins are accepted for
+Components 3 source compatibility and do nothing.)
 
 ## Dismissal while the command runs
 
@@ -193,7 +192,7 @@ children.
 | The same property bound on two steps | Each property appears on exactly one step |
 | A `StepperPanel` without `header` | `header` is the navigation label |
 | Several panels wrapped in one fragment | A fragment counts as **one** step — give each step its own `StepperPanel` child |
-| A raw PrimeReact control for a command value | Use a `CommandForm` field, or validation never re-runs |
+| A raw control (`TextInput`, a native `<input>`) for a command value | Use a `CommandForm` field, or the value is never bound and validation never re-runs |
 | Seeding a required value in `onBeforeExecute` | Use `initialValues` |
 | `pt` applied expecting it to reach the dialog | `pt` targets the stepper; use `dialogPt` |