--- title: "Release digest: September 21 - 28, 2026 (Week 39)" description: "Cross-repository release digest for the week of September 21 - 28, 2026, ISO week 39 of 2026." editUrl: "https://github.com/Cratis/.github/edit/main/release-digests/2026-09-21-to-2026-09-28.md" --- ## Version movement | Repository | Previous version | Current version | | --- | --- | --- | | [AI](https://github.com/Cratis/AI) | [v2.28.1](https://github.com/Cratis/AI/releases/tag/v2.28.1) | [v7.1.1](https://github.com/Cratis/AI/releases/tag/v7.1.1) | | [Ante](https://github.com/Cratis/Ante) | [v0.9.0](https://github.com/Cratis/Ante/releases/tag/v0.9.0) | [v0.13.0](https://github.com/Cratis/Ante/releases/tag/v0.13.0) | | [Arc](https://github.com/Cratis/Arc) | [v22.16.1](https://github.com/Cratis/Arc/releases/tag/v22.16.1) | [v22.31.0](https://github.com/Cratis/Arc/releases/tag/v22.31.0) | | [Arc.Kotlin](https://github.com/Cratis/Arc.Kotlin) | [v7.5.2](https://github.com/Cratis/Arc.Kotlin/releases/tag/v7.5.2) | [v7.6.0](https://github.com/Cratis/Arc.Kotlin/releases/tag/v7.6.0) | | [Arc.TypeScript](https://github.com/Cratis/Arc.TypeScript) | First release | [v0.43.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.43.0) | | [AuthProxy](https://github.com/Cratis/AuthProxy) | [v2.22.2](https://github.com/Cratis/AuthProxy/releases/tag/v2.22.2) | [v2.22.4](https://github.com/Cratis/AuthProxy/releases/tag/v2.22.4) | | [Chronicle](https://github.com/Cratis/Chronicle) | [v19.1.5](https://github.com/Cratis/Chronicle/releases/tag/v19.1.5) | [v19.15.0](https://github.com/Cratis/Chronicle/releases/tag/v19.15.0) | | [Chronicle.Elixir](https://github.com/Cratis/Chronicle.Elixir) | [v3.4.0](https://github.com/Cratis/Chronicle.Elixir/releases/tag/v3.4.0) | [v3.6.0](https://github.com/Cratis/Chronicle.Elixir/releases/tag/v3.6.0) | | [Chronicle.Kotlin](https://github.com/Cratis/Chronicle.Kotlin) | [v6.3.2](https://github.com/Cratis/Chronicle.Kotlin/releases/tag/v6.3.2) | [v6.6.0](https://github.com/Cratis/Chronicle.Kotlin/releases/tag/v6.6.0) | | [Chronicle.Mcp](https://github.com/Cratis/Chronicle.Mcp) | [v1.3.2](https://github.com/Cratis/Chronicle.Mcp/releases/tag/v1.3.2) | [v1.4.0](https://github.com/Cratis/Chronicle.Mcp/releases/tag/v1.4.0) | | [Chronicle.TypeScript](https://github.com/Cratis/Chronicle.TypeScript) | [v6.2.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.2.0) | [v6.22.1](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.22.1) | | [cli](https://github.com/Cratis/cli) | [v3.8.2](https://github.com/Cratis/cli/releases/tag/v3.8.2) | [v3.21.0](https://github.com/Cratis/cli/releases/tag/v3.21.0) | | [Components](https://github.com/Cratis/Components) | [v4.9.0](https://github.com/Cratis/Components/releases/tag/v4.9.0) | [v4.19.0](https://github.com/Cratis/Components/releases/tag/v4.19.0) | | [Fundamentals](https://github.com/Cratis/Fundamentals) | [v7.19.3](https://github.com/Cratis/Fundamentals/releases/tag/v7.19.3) | [v7.19.6](https://github.com/Cratis/Fundamentals/releases/tag/v7.19.6) | | [Orleans](https://github.com/Cratis/Orleans) | [v1.4.0](https://github.com/Cratis/Orleans/releases/tag/v1.4.0) | [v1.12.2](https://github.com/Cratis/Orleans/releases/tag/v1.12.2) | | [Prompter](https://github.com/Cratis/Prompter) | [v0.2.3](https://github.com/Cratis/Prompter/releases/tag/v0.2.3) | [v0.2.4](https://github.com/Cratis/Prompter/releases/tag/v0.2.4) | | [release-action](https://github.com/Cratis/release-action) | [v1.3.1](https://github.com/Cratis/release-action/releases/tag/v1.3.1) | [v1.4.0](https://github.com/Cratis/release-action/releases/tag/v1.4.0) | | [Scene](https://github.com/Cratis/Scene) | [v3.5.0](https://github.com/Cratis/Scene/releases/tag/v3.5.0) | [v4.2.0](https://github.com/Cratis/Scene/releases/tag/v4.2.0) | | [Screenplay](https://github.com/Cratis/Screenplay) | [v4.14.0](https://github.com/Cratis/Screenplay/releases/tag/v4.14.0) | [v4.44.0](https://github.com/Cratis/Screenplay/releases/tag/v4.44.0) | | [Stage](https://github.com/Cratis/Stage) | [v3.20.0](https://github.com/Cratis/Stage/releases/tag/v3.20.0) | [v4.21.0](https://github.com/Cratis/Stage/releases/tag/v4.21.0) | | [Templates](https://github.com/Cratis/Templates) | [v1.7.0](https://github.com/Cratis/Templates/releases/tag/v1.7.0) | [v1.7.2](https://github.com/Cratis/Templates/releases/tag/v1.7.2) | ## Added - **Components** ([Release v4.19.0](https://github.com/Cratis/Components/releases/tag/v4.19.0)): `Toolbar` and `ActionMenubar` move focus between tools with the arrow keys and Home/End, following the toolbar's orientation and reading direction. Every tool keeps its own Tab stop, so Tab works as before. Keys inside inputs, sliders, selects and other widgets in a toolbar keep their native behavior, and a handler that calls `preventDefault` still wins. The new `focusMode` prop (`ToolbarFocusMode`) is `Arrows` by default; use `None` to keep the previous behavior. A mode with a single Tab stop for the whole toolbar is planned in #353. (#328) - **Components** ([Release v4.19.0](https://github.com/Cratis/Components/releases/tag/v4.19.0)): The `PivotViewer` card viewport is a keyboard-focusable, named scroll region. Arrow and Page keys scroll overflowing cards, and Tab moves on to the next control. Use `labels.viewport` to localize its default name, “Card area.” Canvas cards themselves are still not keyboard-selectable. (#349) - **Components** ([Release v4.19.0](https://github.com/Cratis/Components/releases/tag/v4.19.0)): `CratisComponentsProvider` `messages.filter` localizes the filter panel's accessible name (`label`) and its search inputs' names (`searchAriaLabel`) for the whole application. An explicit prop still wins. For search inputs, the placeholder is used when the provider message is not set, so existing names do not change. `messages.filter.label` also names the `PivotViewer` Filters button when `labels.filters` is not set. The `CratisFilterMessages` type is exported. (#347) - **Chronicle** ([Release v19.15.0](https://github.com/Cratis/Chronicle/releases/tag/v19.15.0)): Structured named tags: an event can carry `NamedTag` values, each a `TagName` and a string value, next to its existing plain tags. Append them with `AppendWithNamedTags`, `AppendManyWithNamedTags` and `AddEventWithNamedTags` on `IEventSequence`, `ITransactionalEventSequence` and `IUnitOfWork`; they are available on `EventContext.NamedTags` (#3953) - **Chronicle** ([Release v19.15.0](https://github.com/Cratis/Chronicle/releases/tag/v19.15.0)): Query events and sequence histograms by named tags through the kernel gRPC API (`IEventSequences.QueryEventsWithNamedTags` and `SequenceHistogramWithNamedTags`). Criteria are combined with OR across criteria and AND with the other query dimensions; each criterion matches a name and value on the same tag, compares ordinally, and treats a missing value list as "any value" (#3953) - **Chronicle** ([Release v19.15.0](https://github.com/Cratis/Chronicle/releases/tag/v19.15.0)): Named tags are stored and indexed on MongoDB, SQL (SQLite, PostgreSQL and SQL Server) and in-memory storage. An exact duplicate name and value pair on one event is kept once. Named-tag batch appends keep per-event causation and migrated generations (#3953) - **Chronicle** ([Release v19.15.0](https://github.com/Cratis/Chronicle/releases/tag/v19.15.0)): Upgrade servers before clients: a new client appending named tags to an older server gets `UNIMPLEMENTED` instead of silently losing the tags. - **Chronicle** ([Release v19.15.0](https://github.com/Cratis/Chronicle/releases/tag/v19.15.0)): SQL storage reserves the per-namespace table `__cratis_named_tags`. If a table with that name already exists, event-sequence operations in that namespace fail with `NamedTagsTableCollision` until it is renamed. - **Chronicle** ([Release v19.15.0](https://github.com/Cratis/Chronicle/releases/tag/v19.15.0)): Tag names and values are stored in plaintext and indexed. Never put personal data in tags. - **Chronicle** ([Release v19.15.0](https://github.com/Cratis/Chronicle/releases/tag/v19.15.0)): The Workbench HTTP proxies for the named-tag queries are generated but cannot carry structured criteria yet; use the gRPC API (#4277). - **cli** ([Release v3.21.0](https://github.com/Cratis/cli/releases/tag/v3.21.0)): **Cratis AI update hint.** In a repository with the Cratis AI corpus installed (`.cratis/ai.json` and `.cratis/ai.manifest.json`), an interactive command may end with `↑ Cratis AI update available: 12 new commits since cc9c631 - run 'cratis ai update'`. The hint appears only when the installed commit is behind the latest commit on Cratis/AI's default branch, so a corpus installed from a local checkout or another branch never triggers it. The answer is cached per installed commit next to the CLI version check and rechecked hourly. The hint is skipped when output is redirected, in AI agent environments and completions, while running `ai install`/`ai update`/`ai uninstall`, and when `CRATIS_NO_UPDATE_CHECK` is set (#197). - **cli** ([Release v3.21.0](https://github.com/Cratis/cli/releases/tag/v3.21.0)): **`cratis render` sends Screenplay's typed-context descriptors to Stage**, so generated code can use typed contexts (#192). - **Arc** ([Release v22.31.0](https://github.com/Cratis/Arc/releases/tag/v22.31.0)): A named Arc authorization policy can opt in to being evaluated for unauthenticated callers: `AddArcAuthorizationPolicy(name, evaluatesAnonymous: true)`. The policy then receives an empty, unauthenticated principal and decides whether to allow the guest. This works the same with Arc's `[Authorize]` and ASP.NET Core's `[Authorize(Policy = ...)]`, for commands, queries and observable queries. (#2761) - **Arc** ([Release v22.31.0](https://github.com/Cratis/Arc/releases/tag/v22.31.0)): `AddArcAnonymousAspNetAuthorizationPolicy(name)` gives the same opt-in to a policy registered through ASP.NET Core. It is checked at startup: the name must resolve to exactly one ASP.NET Core policy that doesn't require an authenticated user. Otherwise startup fails with `InvalidAuthorizationConfiguration`. (#2761) - **Stage** ([Release v4.21.0](https://github.com/Cratis/Stage/releases/tag/v4.21.0)): Render Screenplay ESM v3 reducers with verified portable C# bodies as Chronicle reducers and typed context adapters. Supported deterministic, finite operations are admitted explicitly; unsupported or mismatched bodies fail with actionable diagnostics. - **Stage** ([Release v4.21.0](https://github.com/Cratis/Stage/releases/tag/v4.21.0)): Generate read-model and command specifications for reducer-backed models, including collection event expectations and deletion. The Billing payment reducer is an executable example. - **Stage** ([Release v4.21.0](https://github.com/Cratis/Stage/releases/tag/v4.21.0)): Guard every non-null reducer output so its identifier matches the event-source key; mismatches fail rather than silently routing a keyed query to unrelated state. - **Orleans** ([Release v1.12.1](https://github.com/Cratis/Orleans/releases/tag/v1.12.1)): A packed-consumer check that restores and builds `Cratis.Orleans` for .NET 8, 9 and 10 and fails when consumers would resolve mixed Orleans versions. It runs on pull requests, in the daily package update, and before a release is cut. - **Arc.TypeScript** ([v0.43.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.43.0)): `ChronicleCommandScenario` and `ChronicleQueryScenario` evaluate supported flat projections in-process through `ReadModelScenario` from `@cratis/chronicle` 6.19.0, so `given.forEventSource(...).events(...)` now populates projection-backed read models as well as reducer-backed ones. See [Test Chronicle commands and queries](https://github.com/Cratis/Arc.TypeScript/blob/v0.43.0/Documentation/testing/chronicle.md) for the boundary. - **Arc.TypeScript** ([v0.43.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.43.0)): A pinned instance wins over history, and a reducer wins over a projection. Projection seeds replay in the order they were given across event sources. - **Arc.TypeScript** ([v0.43.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.43.0)): A projection outside the supported boundary throws the SDK's `UnsupportedProjectionOperation` unchanged; test it with `ChronicleKernelScenario`. - **Chronicle.TypeScript** ([Release v6.22.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.22.0)): `ReactorScenario` in `@cratis/chronicle/testing` delivers `given` and `when` events in order using production handler dispatch and artifact activation. An `artifactActivator` receives per-event `run` metadata and `complete()` is called after delivery, including on failure. - **Chronicle.TypeScript** ([Release v6.22.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.22.0)): Inspect returned events through `produced`, `sideEffects`, `results`, `shouldHaveProduced`, and `shouldNotHaveProduced`. Handler failures reject the delivery and prevent further deliveries. - **Chronicle.TypeScript** ([Release v6.22.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.22.0)): Unsupported replay, redelivery, command recording, tag-filtered reactors, self-subscribed appends, store/read-model/event-log services, and `waitForCompletion` reject with `UnsupportedReactorOperation` or `UnsupportedEventSequenceOperation`, directing tests to a kernel-backed scenario. Unsupported calls fail delivery even when caught by a handler. - **Chronicle.TypeScript** ([Release v6.22.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.22.0)): Reactor scenario examples cover injected dependencies, services, and multiple event sources. - **Orleans** ([Release v1.12.0](https://github.com/Cratis/Orleans/releases/tag/v1.12.0)): `Cratis.Orleans.Chronicle` package with `EventSourcedStateMachine`: an Orleans state machine whose model is a Chronicle read model derived from events. It reads through `IEventStore.ReadModels`, never writes, and needs no `[StorageProvider]` (#34) - **Orleans** ([Release v1.12.0](https://github.com/Cratis/Orleans/releases/tag/v1.12.0)): `DefineProjection(IProjectionBuilderFor)` for declarative projections; model-bound projections on `TModel` also work. Projections are registered through Chronicle's explicit registration API (#34) - **Orleans** ([Release v1.12.0](https://github.com/Cratis/Orleans/releases/tag/v1.12.0)): `DefineTransitions(IStateMachineTransitions)` with `.On().TransitionTo()` and optional model guards. Definitions are inspected at startup (#34) - **Orleans** ([Release v1.12.0](https://github.com/Cratis/Orleans/releases/tag/v1.12.0)): One fluent Chronicle reactor per state machine, subscribed to the union of the projection's and the transitions' event types. Each delivered event refreshes the grain's model, calls `OnModelChanged(previous, current, context)`, then applies matching transitions (#34) - **Orleans** ([Release v1.12.0](https://github.com/Cratis/Orleans/releases/tag/v1.12.0)): Grain keys `{eventStore}/{namespace}/{eventSourceId}` isolate tenants. `IGrainFactory.GetEventSourcedStateMachine(...)` resolves a grain; `ResolveState(model)` derives the current state from the model on activation, so no state is persisted (#34) - **Orleans** ([Release v1.12.0](https://github.com/Cratis/Orleans/releases/tag/v1.12.0)): `AddEventSourcedStateMachines()` for `IServiceCollection` / `ISiloBuilder` (#34) - **Chronicle** ([Release v19.14.0](https://github.com/Cratis/Chronicle/releases/tag/v19.14.0)): `IProjections.Register(define, id)` registers a read model together with a declarative projection defined through the same `IProjectionBuilderFor` an `IProjectionFor` uses, without assembly discovery. The read model behaves like any other through `IReadModels`, including passive (on-demand) read models (#4287) - **Chronicle** ([Release v19.14.0](https://github.com/Cratis/Chronicle/releases/tag/v19.14.0)): `IProjections.Register()` registers the model-bound projection of a read model that discovery did not find (#4287) - **Chronicle** ([Release v19.14.0](https://github.com/Cratis/Chronicle/releases/tag/v19.14.0)): `IReactors.Define(id, reactor => ...)` and `IReactors.Register(id, reactor => ...)` declare reactors fluently with typed `On` handlers — `(TEvent)`, `(TEvent, EventContext)` and their `Task`-returning forms — and a catch-all `Subscribe((object, EventContext) => ...)`. `IReactorDefinition` exposes the reactor id, event types and whether it subscribes to all events (#4288) - **Chronicle** ([Release v19.14.0](https://github.com/Cratis/Chronicle/releases/tag/v19.14.0)): `ChronicleOptions.ExplicitArtifacts` registers explicit projections, read models and fluent reactors before the client connects; they are included in every registration pass, including after a reconnect (#4287, #4288) - **Orleans** ([Release v1.11.0](https://github.com/Cratis/Orleans/releases/tag/v1.11.0)): `Cratis.Orleans.StateMachines`: the generic Orleans state machine, extracted from Chronicle with the same behavior — `StateMachine`, `State`, `IState`, `IStateMachine`, `NoOpState`, `StateMachineState`, allowed transitions, `OnEnter`/`OnLeave`, and transitions scheduled while entering (#33) - **Orleans** ([Release v1.11.0](https://github.com/Cratis/Orleans/releases/tag/v1.11.0)): A protected `StateMachine(IStorage)` constructor, so a derived state machine can supply its own storage without a `[StorageProvider]` attribute (#33) - **Orleans** ([Release v1.11.0](https://github.com/Cratis/Orleans/releases/tag/v1.11.0)): `ResolveActivationState()` lets a derived state machine decide which state to enter on activation, and the protected `CanTransitionTo(Type)` / `TransitionTo(Type)` allow transitions by type while still honoring each state's rules (#33) - **Arc.TypeScript** ([v0.42.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.42.0)): The proxy generator can write proxies into the backend slice folders. When the output is the artifacts folder, one of its ancestors, or a nested folder containing backend artifacts, the `.proxy` suffix is required, no barrels are written, and watch mode regenerates on backend edits. The generator only overwrites or deletes files it generated, and never analyzes generated, `.proxy`, `.tsx` or spec files as backend artifacts. - **Arc.TypeScript** ([v0.42.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.42.0)): Runtime discovery (`builder.discover(...)`) skips co-located `*.proxy.ts`/`*.proxy.js` and `.tsx` files. - **Arc.TypeScript** ([v0.42.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.42.0)): The Library sample keeps every slice together, uses `@cratis/components` (`DataPage` for the author listing, `CommandDialog` for registration) and runs frontend specs under jsdom beside the backend specs in `yarn test`. The Tasks sample generates its proxies in place too. - **Arc.TypeScript** ([v0.42.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.42.0)): CI fails when committed proxies are stale, and when the Library web bundle contains decorator syntax a browser cannot parse. - **Chronicle.TypeScript** ([Release v6.21.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.21.0)): `EventScenario` supports both `appendMany` overloads. Batches append atomically in input order and return one result per event. The mixed-source overload uses the production client's per-entry precedence for routing, subject, and occurrence, and merges per-entry and shared tags. - **Chronicle.TypeScript** ([Release v6.21.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.21.0)): `given.forEventSource(id).events(...events)` accepts multiple setup events as sequential single appends; if any setup event is rejected, none from that call are committed. `when.forEventSource(id).events(...events)` appends one atomic batch and returns a result for each event. - **Chronicle.TypeScript** ([Release v6.21.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.21.0)): The in-process sequence supports source, event-type, and route read filters, plus append notifications for single and batch appends. Constraints remain unsupported and are rejected rather than simulated. - **Chronicle.TypeScript** ([Release v6.21.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.21.0)): Committed fixtures from the pinned Chronicle kernel verify batch ordering, metadata, causation, read filters, and rejection behavior. - **Components** ([Release v4.18.0](https://github.com/Cratis/Components/releases/tag/v4.18.0)): `--cratis-canvas-minimap-grid-color` and `--cratis-canvas-minimap-item-color` theme the Canvas minimap dot grid and items that have no `color` of their own. Both fall back to the current colors, so the minimap looks the same until you set them. - **Components** ([Release v4.17.0](https://github.com/Cratis/Components/releases/tag/v4.17.0)): `controlsIcons` on `Canvas` (`icons` on `CanvasControls`) replaces any of the minimap, zoom-out, zoom-in and help glyphs with your own icons. Unset fields keep the built-in icons, and the accessible names still come from `controlsLabels`. - **Components** ([Release v4.17.0](https://github.com/Cratis/Components/releases/tag/v4.17.0)): `controlsFollowViewportInsets` on `Canvas` (`followViewportInsets` on `CanvasControls`) turns off the offset by `--canvas-viewport-left`/`--canvas-viewport-right`, for hosts that already move the canvas by that inset. It defaults to `true`, so existing canvases are unchanged. - **Components** ([Release v4.17.0](https://github.com/Cratis/Components/releases/tag/v4.17.0)): The `--canvas-viewport-left` and `--canvas-viewport-right` custom properties the controls read are now documented. - **Screenplay** ([Release v4.43.0](https://github.com/Cratis/Screenplay/releases/tag/v4.43.0)): Publish a slim `Cratis.Screenplay.Contexts` package containing the code-body context family without compiler dependencies. `Cratis.Screenplay` references it and forwards every moved public type, preserving existing binaries. Closes #283. - **Chronicle.TypeScript** ([Release v6.20.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.20.0)): Add `EventScenario` to `@cratis/chronicle/testing` for kernel-free, scenario-local single-event appends. `given` seeds accepted events, `when` appends one event, and `results` and `appendedEvents` expose the act results and accepted history. The scenario supports global sequence allocation, `hasEventsFor`, next and tail positions, source/type reads, and inclusive reads from a sequence number within its documented input boundary. - **Chronicle.TypeScript** ([Release v6.20.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.20.0)): Check the supported append metadata, results, and reads against committed fixtures generated by the pinned Chronicle 19.8.1 kernel oracle. Add an EventScenario guide and compiled documentation snippets. - **Chronicle** ([Release v19.13.0](https://github.com/Cratis/Chronicle/releases/tag/v19.13.0)): `IUnitOfWork.HasEnrolledDecisionReads` reports whether a protected decision read was successfully enrolled, including after commit, rollback or disposal. Command owners can use it to refuse an unguarded returned-event fallback. Existing custom units of work default to `false`; no decision tokens or sequence numbers are exposed. - **Chronicle** ([Release v19.13.0](https://github.com/Cratis/Chronicle/releases/tag/v19.13.0)): Release solution build (zero warnings), all non-integration specifications, client packaging, formatting and markdown validation passed. - **Chronicle** ([Release v19.13.0](https://github.com/Cratis/Chronicle/releases/tag/v19.13.0)): Local MongoDB integration could not start: Docker Desktop LinuxKit kernel 7.0.12 is incompatible with the MongoDB image. A bounded reproduction failed before test assertions; integration CI on GitHub must pass before merge. - **Arc.TypeScript** ([v0.41.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.41.0)): Experimental `DrizzleObservation.PostgreSQLNotify` mode: `withDrizzle({ observation: { mode: DrizzleObservation.PostgreSQLNotify, listener } })` listens for PostgreSQL `NOTIFY` on the fixed `arc_changes` channel through one dedicated connection per tenant, and re-reads observed tables after each committed change. The first read of an observation happens only after `LISTEN` is acknowledged and the table's trigger is validated. - **Arc.TypeScript** ([v0.41.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.41.0)): `postgresqlChangeTrigger(table, { schema? })` returns the trigger SQL to add to a drizzle-kit migration. Arc never runs DDL at runtime; a missing, disabled or incompatible trigger fails the observation before any rows are read. - **Arc.TypeScript** ([v0.41.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.41.0)): `nodePostgresListener(...)` adapts a dedicated node-postgres `Client` as the listener connection. No `pg` runtime import is added to the package root. - **Arc.TypeScript** ([v0.41.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.41.0)): A PostgreSQL-only mode for `Source/Drizzle/run-integration.sh` and a CI job running the PostgreSQL integration specs. - **Components** ([Release v4.16.0](https://github.com/Cratis/Components/releases/tag/v4.16.0)): `confirmBeforeExecute` on `CommandDialog`, `StepperCommandDialog`, and `CommandStepper` asks a question after validation and `onBeforeExecute`, and before the command runs. Only `true` executes. Any other answer leaves the dialog or stepper open without running the command. If the command values change while the question is open, the command is not executed and you confirm again. Stepper fields are disabled until the confirmed submission settles. Without the prop, command execution is unchanged. The `ConfirmBeforeExecute` type is exported. (#317) - **Components** ([Release v4.16.0](https://github.com/Cratis/Components/releases/tag/v4.16.0)): `ChatSidebar` accepts `topicsStatus` and `messagesStatus` (the new `ChatStatus` enum), and `ChatSidebarForObservableQueries` sets them from its queries. The topic list and conversation show loading, failure, and unauthorized text from new `labels` keys, and never show server exception text. A failure keeps what is already shown and adds an alert above it. Unauthorized replaces the content and disables the composer and the New topic button. (#327) - **Components** ([Release v4.16.0](https://github.com/Cratis/Components/releases/tag/v4.16.0)): `PivotViewer` `labels` makes the toolbar text, the item count, and the filter panel's name and search placeholder localizable. The defaults are unchanged. `loadingLabel` still takes precedence over `labels.loading`. (#334) - **Components** ([Release v4.16.0](https://github.com/Cratis/Components/releases/tag/v4.16.0)): `PivotViewer` `labels.searchGroup` names the search box of each option group in the filter panel. It receives the group's label and defaults to `Search `, so each group search now has its own accessible name. (#334) - **Components** ([Release v4.16.0](https://github.com/Cratis/Components/releases/tag/v4.16.0)): FilterPanel `aria-label` and `searchAriaLabel`, `FilterDefinition` `searchAriaLabel` and `autoFocus`, and `CheckboxListFilter` `searchAriaLabel` and `autoFocusSearch`. (#328, #244) - **Components** ([Release v4.16.0](https://github.com/Cratis/Components/releases/tag/v4.16.0)): A `DatePickerInput` reference page, and Common and Dialogs landing pages that help you choose a control. (#260) - **Chronicle** ([Release v19.12.0](https://github.com/Cratis/Chronicle/releases/tag/v19.12.0)): The .NET client's generated JSON schemas give inline object types a `title` with the type name. A declaration generated from a fluent composite-key projection (for example in the Workbench) can then name the key type and recompile. The fluent `CompositeKeyBuilder` still emits untyped expressions, so older kernels are unaffected (#4253) - **Chronicle** ([Release v19.12.0](https://github.com/Cratis/Chronicle/releases/tag/v19.12.0)): The ASP.NET Core causation middleware records the matched route template in a new `routeTemplate` causation property, alongside the existing request path (#4260) - **Arc** ([Release v22.30.0](https://github.com/Cratis/Arc/releases/tag/v22.30.0)): `IFallbackAuthorizationEvaluator` supplies baseline authorization requirements for commands and queries that declare none of their own. It is consulted only when neither the method nor the type has an explicit declaration, so `[AllowAnonymous]` members are no longer ambiguous with a baseline. Commands consult only the `Type` overload. MVC controller actions, including direct HTTP and WebSocket requests to controller-based queries, stay on ASP.NET Core authorization: use `AuthorizationOptions.FallbackPolicy` there (#2751) - **Arc** ([Release v22.30.0](https://github.com/Cratis/Arc/releases/tag/v22.30.0)): `ReceivedAt` on `CommandContext`, `QueryContext` and `AuthorizationPolicyContext`, plus an injectable `IOperationContextAccessor`, expose the time Arc received the operation. It is captured with `TimeProvider` at Arc's transport dispatch, before binding, or at pipeline entry for programmatic calls, and per subscribe operation for streams. It is Arc's receipt time, not network arrival. `ReceivedAt` takes part in record equality, so contexts from different receipts compare unequal (#2767) - **Arc** ([Release v22.30.0](https://github.com/Cratis/Arc/releases/tag/v22.30.0)): Query filters can set `SubscriptionScope` on the query context. Arc snapshots it after filtering and before the query runs, and gives each emission guard an independent copy, so guards can base decisions on membership that the arguments don't carry. Only state that Arc's JSON options serialize is kept, and a scope that cannot be represented is rejected with `InvalidSubscriptionScope`. The scope is always `null` for controller-based observable queries (#2768) - **Chronicle.TypeScript** ([Release v6.19.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.19.0)): `ReadModelScenario` now builds projection-backed read models in-process when no reducer applies. It compiles the same model-bound or declarative definition used at registration, validates the whole definition before replay, and then replays the given events: root `fromEvent`/`.from()` keyed by the event source ID, `setFrom` and schema-based AutoMap for scalar properties, `$eventSourceId`, supported `$eventContext(...)` paths, `$value(...)`, `$null`, `removedWith` and initial values. See [Test read models without a kernel](https://github.com/Cratis/Chronicle.TypeScript/blob/v6.19.0/Documentation/testing.md#projection-capabilities) for the full capability table. - **Chronicle.TypeScript** ([Release v6.19.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.19.0)): `UnsupportedProjectionOperation`, exported from `@cratis/chronicle/testing`. Anything the in-process evaluator does not support (arithmetic such as `@count`/`@increment`, children, joins, nested projections, compliance metadata, and other listed cases) raises this error when the scenario is created, before any event is replayed, instead of producing a result the kernel might not. - **Chronicle.TypeScript** ([Release v6.19.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.19.0)): Kernel projection fixtures in `Source/testing/projections/fixtures/`, produced by the projection oracle against the pinned Chronicle kernel and compared step by step with the in-process results (`yarn oracle:check`). - **Arc.TypeScript** ([v0.40.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.40.0)): `ArcServer.runInScope(scope, callback, options?)` runs a callback inside an existing service scope, with `currentServices()` and `currentContext()` set as they are for a request. Only the correlation ID and an extra abort signal can be supplied (`RunInScopeOptions`); tenant, principal, transport and severity come from the scope. Only scopes created with `server.services.createScope(context)` can be borrowed; Arc's own request, query and observable-query scopes cannot. It rejects scopes from another server, singleton, closed or fabricated scopes, and scopes whose principal is not plain data. It is a trusted host API, not an authorization mechanism: commands still go through the normal pipeline. - **Chronicle** ([Release v19.11.0](https://github.com/Cratis/Chronicle/releases/tag/v19.11.0)): Register a .NET reactor at runtime by stable ID, explicit event types and generations, and an awaited delegate that receives the event context, the JSON content and the generational content map. Unregister it by ID; the observer keeps its stored position. Tags and filters are not yet configurable on delegate reactors (#4196) - **Chronicle** ([Release v19.11.0](https://github.com/Cratis/Chronicle/releases/tag/v19.11.0)): Reactor side-effect handlers can claim synchronous return types with `CanHandleReturnType(Type)`, including a declared `IEnumerable`. Existing handlers stay compatible (#4121) - **Chronicle** ([Release v19.11.0](https://github.com/Cratis/Chronicle/releases/tag/v19.11.0)): `IReactors.RetryFailedPartitionFor(partition)` retries a reactor's failed partition from the .NET client and returns a `ReactorPartitionRetryOutcome` (#3909) - **Chronicle** ([Release v19.11.0](https://github.com/Cratis/Chronicle/releases/tag/v19.11.0)): Batch event payloads accept an optional per-event `causation` field. Older kernels ignore it and store only the ambient chain (#4179) - **Chronicle** ([Release v19.11.0](https://github.com/Cratis/Chronicle/releases/tag/v19.11.0)): Append results expose the event types the operation wrote, including for batch appends (#4132) - **Chronicle.TypeScript** ([Release v6.18.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.18.0)): `usingKeyFromContext(...)` and `usingParentKeyFromContext(...)` on declarative `.addChild(...)`, as in Chronicle for .NET, so a child can be keyed from the event context. The context path is validated when the projection is registered. - **Arc** ([Release v22.29.0](https://github.com/Cratis/Arc/releases/tag/v22.29.0)): JavaScript `RuleBuilder.withSeverity` and `PropertyRule.withSeverity` APIs for explicit per-rule validation severity in generated command validators. - **Arc** ([Release v22.28.0](https://github.com/Cratis/Arc/releases/tag/v22.28.0)): EF Core `Observe`, `ObserveSingle` and `ObserveById` accept `ignoreQueryContext: true` for auxiliary sources in composed observable queries. Opted-in sources read their full filtered results without client paging or sorting and do not update `TotalItems`; the primary observation keeps its paging, sorting and count. Existing composed queries must opt in on their auxiliary observations to get this fix, as with the MongoDB overloads in v22.27.0 (#2804) - **Arc** ([Release v22.28.0](https://github.com/Cratis/Arc/releases/tag/v22.28.0)): `AuthorizationPrincipalScope` is public, so a query or command pipeline can be composed without `AddCratisArc`. The query pipeline guide shows the registrations it needs (#2753) - **Chronicle.TypeScript** ([Release v6.17.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.17.0)): `ActivatedArtifact.run(callback, invocation)` now receives an `ArtifactInvocationContext` for every call: the handled event's `EventContext` and handler name, or the replay notification. A host can then run each reactor or reducer invocation in a context that matches that event, for example with its correlation ID. - **Chronicle.TypeScript** ([Release v6.17.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.17.0)): `ActivatedArtifact.complete()` is an optional hook called once per activation after its batch has been processed, also when processing failed, and before the delivery is acknowledged. If it rejects, the delivery fails with `ArtifactCompletionFailed`, which keeps a processing error if there was one; `dispose()` still runs afterwards. A host can use it to fail a delivery whose resources could not be released cleanly. - **Chronicle** ([Release v19.10.0](https://github.com/Cratis/Chronicle/releases/tag/v19.10.0)): A join in a projection declaration can set its own `automap` or `no automap`, which overrides the projection's setting. The setting is stored with the definition, and applies to live join events and to backfill. Older clients and stored definitions keep inheriting the projection's setting. The fluent .NET `JoinBuilder` and generated client code don't express it yet. - **Chronicle** ([Release v19.10.0](https://github.com/Cratis/Chronicle/releases/tag/v19.10.0)): Joins inside a `nested` object are wired: joined values are set on the nested object, both when the join event arrives and through backfill. - **Stage** ([Release v4.20.0](https://github.com/Cratis/Stage/releases/tag/v4.20.0)): Stage renders more of the executable model onto Cratis now that the upstream fixes are released: - **Stage** ([Release v4.20.0](https://github.com/Cratis/Stage/releases/tag/v4.20.0)): projection literal mappings in `from` blocks, using only literals Chronicle's fluent value expression can carry exactly; - **Stage** ([Release v4.20.0](https://github.com/Cratis/Stage/releases/tag/v4.20.0)): removing a child through a join; - **Stage** ([Release v4.20.0](https://github.com/Cratis/Stage/releases/tag/v4.20.0)): `$context.occurred` on produced events, with one timestamp for the payload and the event's occurrence; - **Stage** ([Release v4.20.0](https://github.com/Cratis/Stage/releases/tag/v4.20.0)): contract and production tags that aren’t duplicated. This is part of #117. - **Stage** ([Release v4.20.0](https://github.com/Cratis/Stage/releases/tag/v4.20.0)): Validation rules and command requirements with warning or information severity reject the command, using Arc's `[BlockOnValidationSeverity]`. (#116) - **Stage** ([Release v4.20.0](https://github.com/Cratis/Stage/releases/tag/v4.20.0)): Specifications for protected queries run through Arc's query pipeline, including denials. They are admitted only when every seeded event comes from the queried key. - **Stage** ([Release v4.20.0](https://github.com/Cratis/Stage/releases/tag/v4.20.0)): The semantic runtime rebuilds its state from stored events on restart through Screenplay's `EstablishWorld`. It refuses to start on a history it can't reproduce. - **Chronicle.TypeScript** ([Release v6.16.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.16.0)): Reactor handlers receive a third argument, `services`, with the `eventStore` and `readModels` of the event store and namespace the reactor observes, plus the delivery's abort `signal`. A handler can now append explicitly and check the `AppendResult`, or look up a read model before acting, as reactors in Chronicle for .NET can through injected services. - **Chronicle.TypeScript** ([Release v6.16.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.16.0)): `ChronicleOptions.artifactActivator` lets an application or framework construct reactors and reducers, for example from a dependency injection container, like `ClientArtifactsActivator` in .NET. It returns an `ActivatedArtifact` with the instance and optional `run` and `dispose` hooks. With an activator, an artifact is activated once per delivered batch (and separately for replay notifications); `run` wraps each handler call and its returned events, and `dispose` runs when the batch is done. Activation failures fail the partition like handler failures; cleanup failures are logged. - **Chronicle.TypeScript** ([Release v6.16.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.16.0)): `ClientArtifactsActivator`, `ActivatedArtifact`, `ArtifactActivationContext`, `ReactorServices` and `ReplayState` are exported from the package root. - **Arc** ([Release v22.27.0](https://github.com/Cratis/Arc/releases/tag/v22.27.0)): MongoDB `Observe`, `ObserveSingle`, and `ObserveById` accept `ignoreQueryContext: true` for auxiliary sources in composed observable queries. Opted-in sources read their full filtered results without client paging or sorting and do not update `TotalItems`; the primary observation keeps its paging, sorting and filtered count. Existing composed queries must opt in on their auxiliary observations to get this fix; the existing overloads remain available (#2756) - **Chronicle.TypeScript** ([Release v6.15.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.15.0)): `@noAutoMap` now works on model-bound child and nested types, as in Chronicle for .NET. A child or nested definition stops auto-mapping event properties when its own type, or the type that declares it, carries `@noAutoMap`. The policy applies to that type's direct child and nested definitions and doesn't cascade further. - **Chronicle.TypeScript** ([Release v6.15.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.15.0)): `@noAutoMap` on an individual property of a child or nested type now excludes that property from auto-mapping. Previously it was ignored. - **Arc.TypeScript** ([v0.39.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.39.0)): Paired conformance checks against Arc for .NET 22.23.0 for commands whose handlers return `OneOf`/`Result` alternatives: a DTO or primitive answers 200 with it as `response`, a validation branch answers 400, a denial 403, a tuple's validation result replaces its response, and no discriminator is added to the wire. An arbitrary `Result` error DTO in .NET is an ordinary 200 response; in TypeScript, return it with `response(...)` to get the same result, or use `rejected(...)`/`denied(...)` for failures. The suite now runs 279 checks. - **Chronicle** ([Release v19.9.0](https://github.com/Cratis/Chronicle/releases/tag/v19.9.0)): Decision reads: `IDecisionReads.Get(key)` returns a read model instance (or its absence) with an opaque guard, and the unit of work's commit is rejected if an event that could change what was read has been appended since. Developers never handle sequence numbers. Admitted read models are projections keyed on the event source without joins, children, custom keys or `all`; everything else is refused with a typed reason. Text keys and canonical (lowercase) GUID keys are admitted. `Chronicle.Testing` supports decision reads in-process. This is the client part of the design for #4138. - **Chronicle** ([Release v19.9.0](https://github.com/Cratis/Chronicle/releases/tag/v19.9.0)): A unit of work that holds a decision read is completed only by its owner, so application code cannot commit it early and bypass the guard. The ASP.NET Core unit-of-work middleware owns its request's unit of work. - **Chronicle** ([Release v19.9.0](https://github.com/Cratis/Chronicle/releases/tag/v19.9.0)): `GetDecisionConflicts` explains a rejected guarded append without exposing sequence numbers. - **Arc.TypeScript** ([v0.38.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.38.0)): Opt-in, tenant-scoped observation for Drizzle read models: `withDrizzle({ observation: DrizzleObservation.InProcess })`. - **Arc.TypeScript** ([v0.38.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.38.0)): `DrizzleReadModels.observe(filter?)` and `observeById(key)` return a live RxJS observable with `current()`, which model-bound observable queries can return and serve over SSE and WebSocket like any observable query. - **Arc.TypeScript** ([v0.38.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.38.0)): `observePage(filter, options)` emits `QueryPage` results for low-level `defineObservableQuery` definitions; generated proxies don't support observable pages yet. - **Arc.TypeScript** ([v0.38.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.38.0)): `DrizzleHandle.notifyChanged(tableOrReadModelType)` announces a write. Inside an Arc command, notifications from the command and its nested commands are published once, when the outermost command finishes (also when it fails). Outside a command they are published immediately. - **Arc.TypeScript** ([v0.38.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.38.0)): The proxy generator recognizes query results whose class derives from an RxJS `Observable` or `Subject`, such as the observables returned by MongoDB and Drizzle read models, and asks for an `Observable<...>` annotation when it can't resolve the item type. - **Arc.TypeScript** ([v0.37.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.37.0)): `ChronicleQueryScenario.for(Model, 'method', ...artifacts)` runs a model-bound query against Chronicle read models without a kernel. Seed state per event source with `given.forEventSource(id, tenant?)`: `.events(...)` builds reducer-backed read models with the Chronicle SDK's `ReadModelScenario`, and `.readModel(instance)` pins an instance, which wins over seeded events. Reads are tenant-scoped, and an unseeded key resolves as missing. - **Arc.TypeScript** ([v0.37.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.37.0)): Listing, watching and projection-backed history need `ChronicleKernelScenario`, and the scenario says so rather than returning a partial answer. - **Arc.TypeScript** ([v0.37.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.37.0)): `snapshotStreamSource(result)` in `@cratis/arc.core` returns the stream a snapshot query returned by mistake, so a test host can release it. - **Arc.TypeScript** ([v0.36.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.36.0)): ARCCHR0006 in `@cratis/eslint-plugin-arc-core`'s `recommended-type-checked` preset. It reports a Chronicle `@reactor()` event handler that returns an Arc `@command()` without a replay decision: `@onceOnly()` on the reactor or handler, or a `@replay()` handler for the same event. Replaying the reactor would otherwise execute the command again. - **Arc.TypeScript** ([v0.36.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.36.0)): It follows `async` handlers, returned arrays and tuples, and helpers in the same class whose result the handler returns, including class-expression reactors. - **Arc.TypeScript** ([v0.36.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.36.0)): It does not follow inherited or external helpers, handlers whose event parameter isn't typed as the event class, decorated classes that only come from `.d.ts` files, or commands executed manually through an Arc server. The ARCCHR0006 page lists these limits. - **Arc** ([Release v22.26.0](https://github.com/Cratis/Arc/releases/tag/v22.26.0)): Select a tenant with `ITenantScope.Begin` for commands, validation, queries, and tenant-scoped reads in background work. The selection takes precedence over request tenant resolution inside the current flow. Dispose to restore the previous tenant; disposal is idempotent, and disposing an outer scope early leaves an active inner tenant selected until it ends (#2747) - **Arc** ([Release v22.26.0](https://github.com/Cratis/Arc/releases/tag/v22.26.0)): Custom `ITenantIdAccessor` registrations are preserved whether they are registered before or after Arc. Explicit tenant scopes require Arc's `TenantIdAccessor` as the effective accessor; resolving `ITenantScope` with a custom accessor throws `ExplicitTenantScopeRequiresArcAccessor` instead of silently selecting a tenant that downstream services cannot see. - **Arc** ([Release v22.26.0](https://github.com/Cratis/Arc/releases/tag/v22.26.0)): Independent HTTP requests reset inherited tenant selection when they enter Arc's request pipeline, before authentication and tenant-bound resolution. On ASP.NET Core this covers all application middleware, but not middleware added by another `IStartupFilter` registered before Arc's. Observable emissions use the subscriber's tenant, not a producer's explicit tenant, on every streaming transport. Tasks and timers started inside a tenant scope keep its tenant after the scope is disposed: do not carry that captured context into unrelated work. - **Arc** ([Release v22.26.0](https://github.com/Cratis/Arc/releases/tag/v22.26.0)): Configurable access to the command and query introspection catalogs (`/.cratis/commands` and `/.cratis/queries`) through `Cratis:Arc:Introspection` (`ArcOptions.Introspection`) (#2764): - **Arc** ([Release v22.26.0](https://github.com/Cratis/Arc/releases/tag/v22.26.0)): `Enabled` (default `true`): set to `false` to leave both routes unmapped. - **Arc** ([Release v22.26.0](https://github.com/Cratis/Arc/releases/tag/v22.26.0)): `RequireAuthentication` (default `false`): deny anonymous callers. Arc.Core returns 401; ASP.NET Core uses the configured scheme's challenge behavior. - **Arc** ([Release v22.26.0](https://github.com/Cratis/Arc/releases/tag/v22.26.0)): `Roles` (comma-separated, any one grants access, requires `RequireAuthentication`): deny callers without a listed role. Arc.Core returns 403; ASP.NET Core uses the configured scheme's forbid behavior. - **Arc** ([Release v22.26.0](https://github.com/Cratis/Arc/releases/tag/v22.26.0)): `TrustForwardedIdentityHeaders` (default `false`): lets the Microsoft Identity Platform header handler authenticate protected catalog requests; enable it only behind a trusted ingress that replaces those headers. - **Arc.TypeScript** ([v0.35.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.35.0)): `/openapi.json` describes `POST /validate` for every command, with the execute operation's request body, tag, and security requirements. Its responses are the untyped command result envelope, and its operationId is `:validate`. - **Arc.TypeScript** ([v0.35.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.35.0)): `GeneratedReturn` is exported as a type, so low-level `defineQuery` and `defineObservableQuery` descriptors can declare their return cardinality. - **Arc** ([Release v22.25.0](https://github.com/Cratis/Arc/releases/tag/v22.25.0)): A model-bound command can declare `[BlockOnValidationSeverity(ValidationResultSeverity.Warning)]`, or `Information`, so that warning- or information-level validation failures reject it. The declared severity is the lowest severity that blocks. It applies to HTTP execution, validation, `Provide()` and in-process `ICommandPipeline` execution, and derived command records inherit it. (#2760) - **Arc** ([Release v22.25.0](https://github.com/Cratis/Arc/releases/tag/v22.25.0)): Generated TypeScript proxies carry the declared severity and apply the same threshold on the client. The server stays authoritative. An out-of-range declared severity fails proxy generation. - **Arc.TypeScript** ([v0.34.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.34.0)): `ValidationResult.information(message, options?)`, `ValidationResult.warning(message, options?)`, and `ValidationResult.error(message, options?)` construct validation results at a chosen severity. - **Arc.TypeScript** ([v0.34.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.34.0)): The options object sets `members`, `state`, `reason`, and `reasonDetail`. `reason` defaults to `rule`, and omitted options are left out of the result. - **Arc.TypeScript** ([v0.34.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.34.0)): `state` and `reasonDetail` reach the command and query HTTP result envelopes. `state` must be JSON-serializable. - **Arc.TypeScript** ([v0.34.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.34.0)): `ValidationResultOptions` is exported for typing those options. - **Stage** ([Release v4.19.0](https://github.com/Cratis/Stage/releases/tag/v4.19.0)): Stage accepts Screenplay's typed-context descriptors (Screenplay 4.41) alongside a model's implementation attachments. `LoadedSemanticModel.TypedContextDescriptors`, the matching `ArtifactRenderRequest` members and a new `CratisRendering.Plan` overload carry them from the same compilation. Stage admits descriptor contract revision 1 only, and refuses descriptors that are not ready for wrapper generation, come from another compilation, are malformed or incomplete, with `STAGE-ESM-021`. - **Stage** ([Release v4.19.0](https://github.com/Cratis/Stage/releases/tag/v4.19.0)): Stage generates typed C# contexts from the descriptors for validation, never falling back to `dynamic`. No generated code uses them yet: they are emitted once reducer bodies render. This is part of #151. - **Arc.TypeScript** ([v0.33.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.33.0)): `scenario.given.forEventSource(sourceId, tenant?).events(...events)` seeds ordered history for an event source. - **Arc.TypeScript** ([v0.33.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.33.0)): When a command reads a reducer-backed read model for that source (through `commandReadModel`, `readModelForValidation` or `provide()`), the scenario builds it from the seeded events. It uses the Chronicle SDK's in-process `ReadModelScenario`, so the kernel isn't needed. - **Arc.TypeScript** ([v0.33.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.33.0)): Seeded events never count as events the command appended. - **Arc.TypeScript** ([v0.33.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.33.0)): Seeding history needs `@cratis/chronicle` 6.14 or later. It is loaded only when history is seeded, so the package's peer range stays `^6.7.0`. - **Arc.TypeScript** ([v0.33.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.33.0)): `scenario.given.forEventSource(sourceId, tenant?).readModel(instance)` pins a read model for a source. A pinned instance wins over seeded history. - **Arc** ([Release v22.24.0](https://github.com/Cratis/Arc/releases/tag/v22.24.0)): `QueryScenario` runs model-bound snapshot queries in-process through the same hosted pipeline as the HTTP endpoint, including argument conversion, authorization, validation, interceptors and owned query scopes. The principal comes from an `ICurrentPrincipalAccessor` registered in `Services`, as with `CommandScenario`. (#2762) - **Arc** ([Release v22.24.0](https://github.com/Cratis/Arc/releases/tag/v22.24.0)): `IQueryScenarioExtender` is a seam for extending query scenarios. `Cratis.Arc.Chronicle.Testing` uses it to seed read models and event history for Chronicle-backed queries, including other read model types the query reads. - **Arc** ([Release v22.24.0](https://github.com/Cratis/Arc/releases/tag/v22.24.0)): Query scenarios materialize lazy results that depend on scoped services before releasing the query scope, so the result stays readable after `Perform` returns. - **Arc.TypeScript** ([Arc for TypeScript 0.32.0 — Chronicle lint rules](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.32.0)): **ARCCHR0003:** a reactor appends to an event store field it got from its own client or runtime, instead of returning the event. The rule cannot prove the store is the reactor's own, and the documentation says so. - **Arc.TypeScript** ([Arc for TypeScript 0.32.0 — Chronicle lint rules](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.32.0)): **ARCCHR0007:** a command's `handle()` or `provide()` appends to the event log directly. That includes stores reached through injected `ChronicleReadModels` or `ChronicleRuntime`, and `.transactional` appends. Such appends escape the command's batch; return the events instead. - **Arc.TypeScript** ([Arc for TypeScript 0.32.0 — Chronicle lint rules](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.32.0)): **ARCCHR0009:** a command property with a secret-looking name that Arc does not mask at runtime, such as `passphrase`, `privateKey`, `accessKey`, `pin`, `otp`, `cvv`, `securityCode` or `authorizationHeader`. It is reported only when `@cratis/arc.chronicle` is installed, skips number, boolean, date and GUID fields, and is silenced by `@notAudited()` or `@pii()`. - **Arc.TypeScript** ([Arc for TypeScript 0.32.0 — Chronicle lint rules](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.32.0)): **ARCCHR0010:** a keyless command returns a `Guid` beside an event instead of an event source ID response. This rule needs type information. - **Arc.TypeScript** ([Arc for TypeScript 0.32.0 — Chronicle lint rules](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.32.0)): The Chronicle code analysis page maps every .NET `ARCCHR` diagnostic to a TypeScript rule, a runtime check, or the reason it does not apply. - **Components** ([Release v4.15.0](https://github.com/Cratis/Components/releases/tag/v4.15.0)): `DataTableForQuery`, `DataTableForObservableQuery`, and `DataPage` show a loading row while the first result is on its way, and a failure row when the query fails or the user is not authorized. A table that is refreshing rows it already shows keeps them visible and marks itself busy (`aria-busy` on the table, `data-busy` on the root). Server exception text is never shown. (#327) - **Components** ([Release v4.15.0](https://github.com/Cratis/Components/releases/tag/v4.15.0)): `loadingMessage`, `failureMessage`, and `unauthorizedMessage` props on `DataTableCore`, both query tables, and `DataPage`, with provider-wide defaults in `CratisComponentsProvider` `messages.dataTable.loading`, `.failed`, and `.unauthorized`. (#327) - **Components** ([Release v4.15.0](https://github.com/Cratis/Components/releases/tag/v4.15.0)): `DataTableCore` accepts `status` (`DataTableStatus.Ready`, `Loading`, `Failed`, or `Unauthorized`) so a table over local rows can show the same states. (#327) - **Components** ([Release v4.15.0](https://github.com/Cratis/Components/releases/tag/v4.15.0)): New stable parts `loading-row`, `loading-cell`, `failure-row`, and `failure-cell` (typed as `loadingRow`, `loadingCell`, `failureRow`, and `failureCell` in `DataTableParts`). The failure cell carries `data-reason`, and the loading and failure text are announced to screen readers through `role="status"` and `role="alert"`. (#327) - **Components** ([Release v4.15.0](https://github.com/Cratis/Components/releases/tag/v4.15.0)): `PivotViewer` announces its loading state to screen readers, labeled by the new `loadingLabel` prop (default `Loading…`). (#328) - **Chronicle** ([Release v19.8.0](https://github.com/Cratis/Chronicle/releases/tag/v19.8.0)): Testing scenarios accept per-run artifacts. Pass `new Defaults(clientArtifactsProvider, serviceProvider)` to `EventScenario` or `ReadModelScenario`, so each test run discovers only the artifacts you give it, not the assembly-wide set. - **Chronicle** ([Release v19.8.0](https://github.com/Cratis/Chronicle/releases/tag/v19.8.0)): `EventScenario(Defaults, ICanProvideConstraints?)` discovers constraints from the supplied defaults when no constraint provider is passed. - **Chronicle** ([Release v19.8.0](https://github.com/Cratis/Chronicle/releases/tag/v19.8.0)): `ReadModelScenario.WithProjection(Action>)` defines a projection inline for a single scenario. It takes precedence over discovered projections and reducers, and it does not leak into other runs. - **Arc.TypeScript** ([Arc for TypeScript 0.31.0 — global command and query filters](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.31.0)): `AuthorizationCommandFilter` and `CommandPipelineFilter` apply to every command. `AuthorizationQueryFilter` and `QueryPipelineFilter` apply to every query snapshot and observable subscription. Register them through `ArcOptions`, the builder's `add…` methods, or the matching decorators. - **Arc.TypeScript** ([Arc for TypeScript 0.31.0 — global command and query filters](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.31.0)): Authorization filters always run before pipeline filters, validators, dependency construction and the handler. - **Arc.TypeScript** ([Arc for TypeScript 0.31.0 — global command and query filters](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.31.0)): A denial is a 403 that never discloses validation results. It wins over invalid input, and severity filtering cannot override it. - **Arc.TypeScript** ([Arc for TypeScript 0.31.0 — global command and query filters](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.31.0)): Command `/validate` runs the same filters without calling `provide()` or `handle()`. - **Arc.TypeScript** ([Arc for TypeScript 0.31.0 — global command and query filters](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.31.0)): Observable queries run the filters once, when the subscription is admitted, not for each emission. That includes the health observable. - **Arc.TypeScript** ([Arc for TypeScript 0.31.0 — global command and query filters](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.31.0)): Helpers build filter results, for example `unauthorizedCommandResult` and `unauthorizedQueryResult`. - **Arc.TypeScript** ([Arc for TypeScript 0.31.0 — global command and query filters](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.31.0)): Command and query contexts carry `operationName`, the declared name of the operation, the same as `CommandContext.Type` and `QueryContext.Name` in .NET. Framework-built contexts always set it, and it cannot be changed. Filters that rely on it must deny or handle a manually built context without it. - **Arc.TypeScript** ([Arc for TypeScript 0.31.0 — global command and query filters](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.31.0)): Paired .NET and TypeScript HTTP checks cover denied, denied with invalid input, allowed with invalid input, and allowed commands and queries. - **Components** ([Release v4.14.2](https://github.com/Cratis/Components/releases/tag/v4.14.2)): `ColumnsProps` is exported from `@cratis/components/DataPage` for the props of `DataPage.Columns`. `ColumnProps` from that subpath is unchanged and still describes a table column. (#333) - **Screenplay** ([Release v4.41.0](https://github.com/Cratis/Screenplay/releases/tag/v4.41.0)): Screenplay publishes typed-context descriptors: language-neutral data describing exactly what each code body can see, so providers such as Stage can generate typed wrappers instead of `dynamic` contexts. They cover reducer transitions (a typed `Event` per `on` event using its current generation, and a nullable `State` shaped like the read model), validation and rule code, code policies at each place they are used, and the context of command handlers, which are still not bound. This is the descriptor part of decision 0012 and advances #139. - **Screenplay** ([Release v4.41.0](https://github.com/Cratis/Screenplay/releases/tag/v4.41.0)): `CompilationResult` exposes the descriptors through `TypedContextDescriptors` and `ContextsFor(requirementId)`. `IsWrapperReady` is true only for descriptors from a successful compilation whose types all resolve; a failed compilation publishes only command-handler descriptors, marked not ready. Every descriptor carries the definitions of the concept and composite types it refers to. - **Screenplay** ([Release v4.41.0](https://github.com/Cratis/Screenplay/releases/tag/v4.41.0)): MCP has a paged `typed-contexts` view; `implementation-requirements` items gain a small `typedContext` reference (count and operation ids). - **Screenplay** ([Release v4.41.0](https://github.com/Cratis/Screenplay/releases/tag/v4.41.0)): The descriptor contract has its own revision (1), a published vocabulary of portable type tokens and source kinds, and two readable vectors (`typed-contexts-v1.json`, `unbound-handler-context-v1.json`) packaged with the canonical vectors. Canonical executable-model bytes and revisions are unchanged. - **Chronicle.TypeScript** ([Release v6.14.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.14.0)): `@cratis/chronicle/testing` exports `ReadModelScenario`. Seed history with `scenario.given.forEventSource(id).events(...)`, then read `await scenario.instance` or `await scenario.instanceForEventSourceId(id)`. `wasDeletedForEventSourceId(id)` tells a deleted read model apart from one that never materialized. - **Chronicle.TypeScript** ([Release v6.14.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.14.0)): Events go through the same reducer dispatch and the same event serialization as production. Concept values are therefore flattened exactly as they are when appended. - **Chronicle.TypeScript** ([Release v6.14.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.14.0)): The event context carries the same defaults as the kernel, sequence numbers are global in seed order, and each event source is reduced separately. - **Chronicle.TypeScript** ([Release v6.14.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.14.0)): A reducer that fails is reported with the read model and reducer names and the original error as its cause. - **Chronicle.TypeScript** ([Release v6.14.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.14.0)): A read model built by a projection is rejected with a clear message; test it against a kernel instead. - **Chronicle** ([Release v19.7.3](https://github.com/Cratis/Chronicle/releases/tag/v19.7.3)): CHR0054 reports a reactor method whose return type Chronicle cannot discover as a handler, with a message about the return type (#4206) - **Chronicle.Elixir** ([Release v3.6.0](https://github.com/Cratis/Chronicle.Elixir/releases/tag/v3.6.0)): `Chronicle.Observers` - lists what the event store knows about its observers and removes one by id. For the observer whose declaring code is gone: a deleted read model and its projection, or a removed reactor. Removal covers the whole event store, since an observer's definition (and its projection definition, where it has one) is a store-level record. The kernel refuses while the observer is running or still has a subscribed client in any namespace, naming the namespace that blocked it - there is no override. Read model data and sink containers are left untouched. - **Chronicle.TypeScript** ([Release v6.13.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.13.0)): `eventStore.observers` - lists what the event store knows about its observers and removes one by id. For the observer whose declaring code is gone: a deleted read model and its projection, or a removed reactor. Removal covers the whole event store, since an observer's definition (and its projection definition, where it has one) is a store-level record. The kernel refuses while the observer is running or still has a subscribed client in any namespace, naming the namespace that blocked it - there is no override. Read model data and sink containers are left untouched. - **Chronicle.Kotlin** ([Release v6.6.0](https://github.com/Cratis/Chronicle.Kotlin/releases/tag/v6.6.0)): `store.observers` - lists what the event store knows about its observers and removes one by id. For the observer whose declaring code is gone: a deleted read model and its projection, or a removed reactor. Removal covers the whole event store, since an observer's definition (and its projection definition, where it has one) is a store-level record. The kernel refuses while the observer is running or still has a subscribed client in any namespace, naming the namespace that blocked it - there is no override. Read model data and sink containers are left untouched. - **Screenplay** ([Release v4.40.0](https://github.com/Cratis/Screenplay/releases/tag/v4.40.0)): `SemanticEvaluator.EstablishWorld(plan, facts)` establishes a deterministic reference world from ordered existing facts, with no read-model snapshots required. It checks every fact first: a default or null fact array, an unknown event, a payload that doesn't match the event, a missing or blank event-source identity, a source type other than the event's declared producer destination type, or a blank tag returns `SemanticRejected` with category `Contract`. A fact that affects a reducer-backed read model returns `SemanticUnsupported` with capability `Projection`, because reducer transitions are opaque. This is reference semantics and does not replace Chronicle replay. (#253) - **Screenplay** ([Release v4.38.0](https://github.com/Cratis/Screenplay/releases/tag/v4.38.0)): A `StateView` slice's specification can use `when append … for`, as long as exactly one command produces the event and so determines the source type. (#262) - **Chronicle.TypeScript** ([Release v6.12.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.12.0)): `@index()` marks a read-model property to be indexed, including properties in nested objects and in typed child collections. Paths are joined with dots, as in .NET, for example `address.zipCode` and `lines.productId`. - **Chronicle.TypeScript** ([Release v6.12.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.12.0)): Indexes are registered with the kernel at application startup for declarative projections, model-bound projections, variants and reducers, and through `readModels.register()`. The MongoDB sink creates the indexes. - **Screenplay** ([Release v4.37.0](https://github.com/Cratis/Screenplay/releases/tag/v4.37.0)): Event generations now bind to the executable model. Events with several generations share one contract identity and carry their complete prior revisions, predecessor links and revision-specific property identities. Ordinary references use the current generation. This implements decisions 0011 and 0015 and advances #71. - **Screenplay** ([Release v4.37.0](https://github.com/Cratis/Screenplay/releases/tag/v4.37.0)): Persisted event contracts can advance through an explicit, catalog-revision-checked workspace transaction. Renaming or moving an event preserves its identities across generations; combining a rename with evolution still requires explicit advancement. - **Screenplay** ([Release v4.37.0](https://github.com/Cratis/Screenplay/releases/tag/v4.37.0)): The RegisterProject v2 canonical corpus declares two event generations, removes the duplicated `projectId` from the current event payload and uses the event source as its identity. Single-file, folder, reordered and relocated forms produce the same model. This advances #168. - **Chronicle.TypeScript** ([Release v6.11.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.11.0)): `waitForCompletion({ timeoutMs, signal })` accepts an `AbortSignal`. Canceling the signal rejects the wait promptly with the signal's reason and cancels the underlying call, including while the client is still waiting for an access token. Other calls that wait for the same token are not affected. The existing `waitForCompletion(timeoutMs)` form and its five-second default are unchanged. - **Chronicle.TypeScript** ([Release v6.10.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.10.0)): `RejectedChronicleCredentials`: the client now stops retrying and rejects `getEventStore(...)` and later calls when the credentials are rejected. This applies when the token endpoint answers `invalid_client`, `unauthorized_client`, or `invalid_grant`, or the kernel refuses an API key, on three consecutive attempts. Previously a wrong password made `getEventStore(...)` wait forever. - **Chronicle.TypeScript** ([Release v6.10.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.10.0)): `@childrenFrom(Event, ChildType, identifiedBy?, parentKey?)` accepts the child class as its second argument. Use it under runtimes that emit no type metadata, such as `tsx`, so the client knows the element type of a children collection. - **Chronicle.TypeScript** ([Release v6.10.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.10.0)): A root `yarn test` script. - **Screenplay** ([Release v4.36.0](https://github.com/Cratis/Screenplay/releases/tag/v4.36.0)): MCP can export the compiled executable model: `read-workspace` view `executable-model` returns its schema, language and semantic versions, model revision and size, plus bounded base64 pages of the exact canonical bytes. It is available only when compilation succeeded; otherwise it reports `available: false` and points to the `executable-diagnostics` view. Continuation pages must pass `expectedModelRevision` and `expectedAttachmentManifestRevision`, and are refused if the model or any attached code changed, including a code edit that changes neither the workspace nor the model revision. The exported model alone is not a proof of equivalence or a runnable attachment bundle (decision 0016). - **Screenplay** ([Release v4.36.0](https://github.com/Cratis/Screenplay/releases/tag/v4.36.0)): `implementation-requirements` responses include the attachment-manifest revision. Passing it back pins a continuation and refuses it if attached code changed; continuations without it work as before. - **Chronicle.Kotlin** ([Release v6.5.0](https://github.com/Cratis/Chronicle.Kotlin/releases/tag/v6.5.0)): `set(...).toValue(value)` on the fluent projection builder sets a constant. `toValue(null)` clears the property. - **Chronicle.Kotlin** ([Release v6.5.0](https://github.com/Cratis/Chronicle.Kotlin/releases/tag/v6.5.0)): Passive reducers (`@Reducer(isActive = false)`, or a reducer whose read model is `@Passive`) are folded in the client from the reducer's event sequence on `getInstanceByKey` and `getInstances`, so they return current state. - **Chronicle.Kotlin** ([Release v6.5.0](https://github.com/Cratis/Chronicle.Kotlin/releases/tag/v6.5.0)): `ChronicleConnectionFailed` is thrown by `awaitRegistration()` and by appends that wait for registration when the kernel rejects the connection: wrong credentials, missing permission, or an incompatible server. The client keeps retrying and recovers when the kernel accepts a connection. - **Chronicle.Kotlin** ([Release v6.5.0](https://github.com/Cratis/Chronicle.Kotlin/releases/tag/v6.5.0)): `ChronicleServerIncompatible` (an `IllegalStateException`) is thrown when the compatibility check fails. - **Chronicle.Kotlin** ([Release v6.5.0](https://github.com/Cratis/Chronicle.Kotlin/releases/tag/v6.5.0)): `ArtifactRegistrationFailed` is thrown from an explicit `registerAll()` that could not start one or more reactors or reducers, naming each one. - **AI** ([Release v7.0.0](https://github.com/Cratis/AI/releases/tag/v7.0.0)): A decision engine choice: the built-in Decision Engine or TypeSafe's Jev, selected with `UseBuiltInDecisionEngine` or `UseJevDecisionEngine`. Exactly one engine is in force at a time; until one is chosen, decisions go to the built-in engine - **AI** ([Release v7.0.0](https://github.com/Cratis/AI/releases/tag/v7.0.0)): Jev support: an API key (encrypted at rest and kept out of the causation chain), a model defaulting to `jev-latest` and an endpoint defaulting to `https://api.typesafe.ai`. Questions that share a context are sent as one request - **AI** ([Release v7.0.0](https://github.com/Cratis/AI/releases/tag/v7.0.0)): The built-in engine's address and model are deployment configuration under `Cratis:AI:Decisions:BuiltIn`, bound through `IOptions` - **AI** ([Release v7.0.0](https://github.com/Cratis/AI/releases/tag/v7.0.0)): `DecisionEngineSettings.CurrentDecisionEngine` returns the engine in force, its model and a cached health check for a settings page. The API key is never returned - **AI** ([Release v7.0.0](https://github.com/Cratis/AI/releases/tag/v7.0.0)): Decision usage: `RecordDecisionUsage` and the `DecisionUsageByDay` read model, with `DecisionUsageForLastThirtyDays` - **AI** ([Release v7.0.0](https://github.com/Cratis/AI/releases/tag/v7.0.0)): A `DecisionRequest` can carry the question being asked, a description of each choice and a topic. The Decision Engine includes the question and descriptions in its prompt; without them it keeps the generic question - **AI** ([Release v7.0.0](https://github.com/Cratis/AI/releases/tag/v7.0.0)): `CratisAIBuilder.WithDecisions()` registers decision making, and `WithDecisions()` replaces how the engine is resolved - **Chronicle.TypeScript** ([Release v6.9.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.9.0)): Class-level `@onceOnly()` registers a reactor as not replayable, so the kernel never replays it. The marker is not inherited, as in .NET. - **Chronicle.TypeScript** ([Release v6.9.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.9.0)): Method-level `@onceOnly()` skips that handler when an event is delivered during a replay. - **Chronicle.TypeScript** ([Release v6.9.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.9.0)): `@replay()` marks a handler that runs instead of the regular handler for its event type during a replay. - **Chronicle.TypeScript** ([Release v6.9.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.9.0)): The shared Chronicle documentation shows TypeScript examples for once-only and replay handlers. - **AI** ([Release v6.5.0](https://github.com/Cratis/AI/releases/tag/v6.5.0)): Kubernetes workers can keep their workspace on a volume of their own. Set `Cratis:AI:ContainerRuntime:ScratchStorageClassName` and `ScratchSize`, and each worker gets a volume provisioned from that class, mounted at `/workspace` and removed with the worker. A checkout and its build output then no longer fill the node's disk or compete with other workers on it. Use a storage class that deletes volumes with their claim and binds on first consumer. Leaving either setting unset keeps today's behavior. - **Chronicle** ([Release v19.7.0](https://github.com/Cratis/Chronicle/releases/tag/v19.7.0)): The event-store dashboard, built from projections with composite keys rather than counting rows on demand, with per-namespace figures and drill-down, and key figures under each event store on the landing page (#3731) - **Chronicle** ([Release v19.7.0](https://github.com/Cratis/Chronicle/releases/tag/v19.7.0)): A declarative surface for kernel-owned projections - identified with a `$system.` prefix, owned by the kernel rather than a client, and refused by replay, because replaying one rebuilds state the kernel keeps for itself - **Chronicle** ([Release v19.7.0](https://github.com/Cratis/Chronicle/releases/tag/v19.7.0)): `ProjectionScope`, so a read model can be built per namespace, once for the whole store, or both. A `Both` declaration lowers to two single-scope definitions, and a global one is keyed with the unset namespace - **Chronicle** ([Release v19.7.0](https://github.com/Cratis/Chronicle/releases/tag/v19.7.0)): A statistics query surface over the new projections, and the Workbench screens that show it - **Chronicle.TypeScript** ([Release v6.8.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.8.0)): `@unique()` marks an event property or an event class as unique. `@removeConstraint(name)` releases a named constraint, can be repeated, and is inherited like the .NET attribute. - **Chronicle.TypeScript** ([Release v6.8.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.8.0)): The shared constraint pages on the Chronicle documentation site now show TypeScript examples for model-bound constraints. - **AI** ([Release v6.4.0](https://github.com/Cratis/AI/releases/tag/v6.4.0)): `cratis-content-length`: when content stays short, when it earns more length, and where to split it. It has pilot bands for LinkedIn, documents, video, X, Bluesky, Mastodon, community answers, blog articles, tutorials, newsletters, YouTube and release notes, and says which platform limit or soft trigger applies. Each band states how strong its evidence is. It also sets batch-variety targets so a feed doesn't read as one length. - **AI** ([Release v6.4.0](https://github.com/Cratis/AI/releases/tag/v6.4.0)): `cratis-developer-marketing`: plans how developer content earns real engagement and adoption. It covers positioning around what developers evaluate (docs, trials, peers, APIs, limits), hooks without bait, the move from pillar to canonical source to channel-native entry points, community participation, founder and company voice, a sustainable cadence, and a staged measurement framework with a small-sample experiment design. - **AI** ([Release v6.4.0](https://github.com/Cratis/AI/releases/tag/v6.4.0)): The voice and cadence skill gains a catalog of 21 AI-sounding patterns (lexical, syntactic, structural and tonal), each with a script heuristic and the human alternative. It checks a batch for sameness, fixes problems with substance, and includes a meaning-preservation check that handles curly apostrophes. It is explicitly an editing aid, never an authorship detector. - **AI** ([Release v6.4.0](https://github.com/Cratis/AI/releases/tag/v6.4.0)): The feed post skill leads with media that explains, and puts the Cratis mark on every image, document page, GIF frame and video; screenshots are framed, never stamped. It has guidance for adapting a post to other channels, and a dated evidence matrix with a URL for every source. - **AI** ([Release v6.4.0](https://github.com/Cratis/AI/releases/tag/v6.4.0)): Both new skills are in the `cratis/content` profile. - **Screenplay** ([Release v4.35.0](https://github.com/Cratis/Screenplay/releases/tag/v4.35.0)): MCP can propose a fix for a diagnostic: `read-workspace` has a `repairs` view listing the compiler-authored repairs for the workspace's diagnostics (code, subject and typed operations), and `propose-repair` turns one into a retained proposal. Review it with `read-proposal` and write it with `apply`; nothing is written before that, and a stale workspace revision is refused with a typed conflict. - **Screenplay** ([Release v4.35.0](https://github.com/Cratis/Screenplay/releases/tag/v4.35.0)): The first repair migrates a deprecated `validate csharp` block (`PLAY0397`) to a tagged ```` ```csharp ```` fence. The code body, its requirement identity and content hash, and the executable model are unchanged. The repair reprints the whole file canonically, so it is refused if that would drop a comment. Other `PLAY0397` forms are not offered a repair. - **Screenplay** ([Release v4.35.0](https://github.com/Cratis/Screenplay/releases/tag/v4.35.0)): Library hosts can find and propose repairs through `WorkspaceDiagnosticRepairs.Find` and `ProposeRepair`, which require canonical formatting (`RequiredFormatting`). - **Screenplay** ([Release v4.35.0](https://github.com/Cratis/Screenplay/releases/tag/v4.35.0)): Adding a node whose references don't resolve is refused under the safe reference policy, which is how decision 0014 covers "link" in #138. - **Screenplay** ([Release v4.34.0](https://github.com/Cratis/Screenplay/releases/tag/v4.34.0)): Events can declare their generations: `event ProjectRegistered generation 2`. An event without the marker is generation 1 and prints as before. Each earlier generation is a complete declaration in the same slice, numbered consecutively from 1; an invalid, duplicate or missing generation is a compile error (`PLAY0446`, `PLAY0447`, `PLAY0448`). Printing, workspace and MCP authoring, and editor highlighting, completion and hover support the marker. This is the grammar part of decision 0011 for #71. - **Screenplay** ([Release v4.34.0](https://github.com/Cratis/Screenplay/releases/tag/v4.34.0)): A model that uses the marker does not compile to the executable model yet: binding fails with `PLAY0449` until generation lineage ships (decision 0015). Models without the marker are unchanged. - **cli** ([Release v3.19.0](https://github.com/Cratis/cli/releases/tag/v3.19.0)): `chronicle observers remove` — removes an observer whose declaring code is gone (a deleted read model and projection, or a removed reactor), clearing its definition, state, handled counts and failed partitions across every namespace of the event store. Asks for confirmation first, stating what is deleted, that it reaches every namespace, that read models and their data are left alone, and that it cannot be undone. The kernel refuses while the observer is running or a client is still subscribed to it, and the command reports that refusal rather than reporting success. - **Arc.TypeScript** ([Arc for TypeScript 0.29.0 — query paging, sorting and QUERY bodies like .NET](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.29.0)): `QueryPagingRequired` is returned as a 400 `rule` validation result on `Size` in two cases: - **Arc.TypeScript** ([Arc for TypeScript 0.29.0 — query paging, sorting and QUERY bodies like .NET](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.29.0)): an unpaged MongoDB or Drizzle query reads more than the provider's maximum page size; - **Arc.TypeScript** ([Arc for TypeScript 0.29.0 — query paging, sorting and QUERY bodies like .NET](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.29.0)): a client asks for a page larger than that maximum. - **cli** ([Release v3.18.0](https://github.com/Cratis/cli/releases/tag/v3.18.0)): `cratis render` reads the implementation files a model references (`file ...` on policies, validation, reducers and other code) from the model folder, or from a single `.play` file's folder, and gives their contents to the Screenplay compiler, so file-backed code is identified by content. (#184) - **cli** ([Release v3.18.0](https://github.com/Cratis/cli/releases/tag/v3.18.0)): A file the loader refuses (outside the model folder, a link, missing, too large or not text) is reported as `PLAY0430`–`PLAY0434`, even when compilation fails. (#184) - **Chronicle** ([Release v19.6.0](https://github.com/Cratis/Chronicle/releases/tag/v19.6.0)): `[NotProjected]` declares a read model member that the projection deliberately does not populate, because whatever reads the model assembles it. A projection may only consume events, never another read model, so a value joined in from a second read model can only be filled in by the query that serves it — and there was previously no way to say so. Declaring it also fences AutoMap off the member, so a subscribed event carrying the same name can no longer write over the assembled value - **Arc.TypeScript** ([Arc for TypeScript 0.28.0 — Chronicle personal data in directly read models](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.28.0)): Chronicle read models that contain `@pii()` or `@encrypted()` data are decrypted before a query serves them, when the query reads them directly from their MongoDB collection through `MongoCollection`. This covers nested properties, array items, class-level markings, single results, arrays, pages and observable emissions. - **Arc.TypeScript** ([Arc for TypeScript 0.28.0 — Chronicle personal data in directly read models](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.28.0)): If decryption fails, the query or emission fails instead of serving encrypted values. - **Screenplay** ([Release v4.33.0](https://github.com/Cratis/Screenplay/releases/tag/v4.33.0)): Screenplay can show which read-model instances each projection event affects, derived from the executable model with no new syntax: one instance by key (`from`, removal), one per event source (`all`), or many through a root join (instances whose join property equals the event source id, never creating one) or a child join and `remove via join` (children whose identity equals the key, across every parent). `SemanticAffectedProjectionInstances.GetAffectedInstances` returns the relationships per event and block, with an overload that uses the application's types to resolve a child identity. This is the first part of decision 0007 for #132. - **Chronicle** ([Release v19.5.0](https://github.com/Cratis/Chronicle/releases/tag/v19.5.0)): Removing an observer and everything the event store keeps for it — its definition, its state and handled counts in every namespace, its failed partitions, its in-flight events and, for a projection, its projection definition. Refuses while the observer is running or still has a subscribed client in any namespace, naming the namespace that blocked it. Read model data is left untouched (#4151) - **Chronicle** ([Release v19.5.0](https://github.com/Cratis/Chronicle/releases/tag/v19.5.0)): `EventStore.Observers` on the .NET client, for listing the observers of an event store and removing one (#4151) - **Chronicle** ([Release v19.5.0](https://github.com/Cratis/Chronicle/releases/tag/v19.5.0)): A **Remove** action on the Workbench observers page, with a confirmation that states what removal deletes, what it leaves alone and that it cannot be undone (#4151) - **Stage** ([Release v4.17.0](https://github.com/Cratis/Stage/releases/tag/v4.17.0)): Render inputs can carry a Screenplay model's implementation attachments: the compiler's requirements and each resolved body, keyed by requirement id. Inline bodies come from the source; file bodies are loaded through Screenplay's `AttachmentFiles` from the model root. `LoadedSemanticModel` exposes the requirements, the bodies and the loader's attachment diagnostics, and new `CratisRendering.Plan` overloads accept them. - **Stage** ([Release v4.17.0](https://github.com/Cratis/Stage/releases/tag/v4.17.0)): Planning verifies every supplied body against its requirement's content hash. A body the model references that is missing, refused by the loader, or changed since compilation fails with `STAGE-ESM-020`, which names the requirement and the loader's reason (`PLAY0430`–`PLAY0434`), and no artifacts are produced. - **Orleans** ([Release v1.10.0](https://github.com/Cratis/Orleans/releases/tag/v1.10.0)): Jobs can run their steps in ordered stages. Give a step a stage with `CreateStep(request, stage)` (or `JobStepDetails.Stage`): every step in a stage reaches an outcome before any step in a later stage starts, and the steps within a stage still run in parallel. A job that never assigns a stage has every step in `JobStepStage.First` and runs exactly as before. (#27) - **Orleans** ([Release v1.10.0](https://github.com/Cratis/Orleans/releases/tag/v1.10.0)): A stage with a failed step stops the job by default. Every step behind it is recorded with the new `JobStepStatus.Unreachable` status and counted in `JobProgress.UnreachableSteps`, and the job ends `CompletedWithFailures` because it can account for every step. Override `GetFailureBehaviorFor` to return `JobStageFailureBehavior.ContinueWithNextStage` for a best-effort stage. (#27) - **Orleans** ([Release v1.10.0](https://github.com/Cratis/Orleans/releases/tag/v1.10.0)): `JobProgress.Stages` reports the progress of each stage. It stays empty for a job with a single stage. (#27) - **Orleans** ([Release v1.10.0](https://github.com/Cratis/Orleans/releases/tag/v1.10.0)): A resumed job continues from the stage it had reached. This includes a job that a stopped silo left between two stages, whether that was after one stage completed or at a failed barrier that nothing had acted on yet. (#27) - **Orleans** ([Release v1.10.0](https://github.com/Cratis/Orleans/releases/tag/v1.10.0)): `Job.KeepAfterCompletedWithFailures` lets a job remove its persisted state after completing with failures. The default is `true`, which keeps today's behavior. A job that runs on a short cadence can override it so it does not keep a record of every failed run. - **Arc.TypeScript** ([Arc for TypeScript 0.27.0 — Drizzle read models in commands](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.27.0)): A command that declares `@inject(commandReadModel(Model))` receives the Drizzle row whose primary key equals the command key. The row is read from the current tenant's database. - **Arc.TypeScript** ([Arc for TypeScript 0.27.0 — Drizzle read models in commands](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.27.0)): `DrizzleReadModels.findById(key)` loads a row by the table's single primary key. Arc's own custom columns get a typed key, and plain columns get a primitive. Invalid number and GUID keys are rejected with a clear error. - **Arc.TypeScript** ([Arc for TypeScript 0.27.0 — Drizzle read models in commands](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.27.0)): `DrizzleReadModelForCommandResolver` is exported. - **Screenplay** ([Release v4.32.0](https://github.com/Cratis/Screenplay/releases/tag/v4.32.0)): `read-workspace` has a paged `source-map` view: the compiler's map from each semantic id to its role, identity origin, document and exact source span. When compilation did not succeed it reports `available: false` and points to the `executable-diagnostics` view instead of returning an empty map. - **Screenplay** ([Release v4.32.0](https://github.com/Cratis/Screenplay/releases/tag/v4.32.0)): `find-fixtures` finds the payload values and `for` destinations of `when append` events, with the role `whenAppendedEvent`. - **Screenplay** ([Release v4.32.0](https://github.com/Cratis/Screenplay/releases/tag/v4.32.0)): Compact specification summaries show a `then denied` assertion and the appended event of a `when append` specification. - **Screenplay** ([Release v4.31.0](https://github.com/Cratis/Screenplay/releases/tag/v4.31.0)): Reaction triggers can declare the views they decide from: `reads [as ] [by ]`, with the same alias rules as command reads. Parsing, validation, printing, the syntax walker, MCP references, and editor highlighting, completion and hover all support it. - **Screenplay** ([Release v4.31.0](https://github.com/Cratis/Screenplay/releases/tag/v4.31.0)): Diagnostics for trigger reads: an unknown view, a repeated view without an alias, a duplicate alias, an alias that collides with a trigger value, a `by` that names no trigger value (`PLAY0442`, warning), a `by` under a clock trigger (`PLAY0443`, error), and a primitive type read as a view (`PLAY0444`, warning, pointing to `@reads`). - **Arc.TypeScript** ([Arc for TypeScript 0.26.0 — MongoDB watcher and joined observations](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.26.0)): `mongoDBWatcher` observes changes to a tenant's collections as RxJS observables for application code, the counterpart of .NET's `IMongoDBWatcher`. - **Arc.TypeScript** ([Arc for TypeScript 0.26.0 — MongoDB watcher and joined observations](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.26.0)): Joined observations re-emit a primary collection's results when it or one or two related collections change, like .NET's joined observe builder. - **Arc.TypeScript** ([Arc for TypeScript 0.26.0 — MongoDB watcher and joined observations](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.26.0)): Fundamentals `Point`, `LineString` and `Polygon` values are stored as GeoJSON. - **Arc.TypeScript** ([Arc for TypeScript 0.26.0 — MongoDB watcher and joined observations](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.26.0)): MongoDB client metrics through OpenTelemetry for clients Arc creates. - **Arc.TypeScript** ([Arc for TypeScript 0.26.0 — MongoDB watcher and joined observations](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.26.0)): Reads retry transient MongoDB errors, at most twice. - **Arc.TypeScript** ([Arc for TypeScript 0.25.0 — kernel-backed Chronicle tests and read consistency](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.25.0)): `ChronicleKernelScenario` in `@cratis/arc.chronicle/testing` runs commands against a real Chronicle kernel: seed events, execute commands through Arc's pipeline, wait for projections through the kernel's own completion signal, and assert on appended events, read models and constraint violations. The in-memory `ChronicleCommandScenario` stays the fast default. - **Arc.TypeScript** ([Arc for TypeScript 0.25.0 — kernel-backed Chronicle tests and read consistency](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.25.0)): `completionTimeoutMs` makes a command wait, within a bound, until Chronicle has processed the events it appended, so a query right after the command sees the result. - **Arc.TypeScript** ([Arc for TypeScript 0.25.0 — kernel-backed Chronicle tests and read consistency](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.25.0)): `ChronicleReadModels` reads can ask for `immediate` consistency for passive projections. - **Arc.TypeScript** ([Arc for TypeScript 0.25.0 — kernel-backed Chronicle tests and read consistency](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.25.0)): Guides for kernel-backed testing and for choosing read consistency. - **Arc.TypeScript** ([Arc for TypeScript 0.24.0 — Core namespaces and clean builds](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.24.0)): `server.validateCommand(...)` and `app.validate(...)` run a command's authorization and validation without executing it, like .NET's command pipeline `Validate`. - **Arc.TypeScript** ([Arc for TypeScript 0.23.0 — Chronicle read model queries](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.23.0)): `ChronicleReadModels` reads read models for the current tenant with `getAll(Type)` and `getById(Type, id)`, and observes them as RxJS observables with `observeAll(Type)` and `observeById(Type, id)`, so observable queries over Chronicle read models need no custom plumbing. - **Arc.TypeScript** ([Arc for TypeScript 0.23.0 — Chronicle read model queries](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.23.0)): `cratisArc(arc).close(server)` closes an Express host, draining open SSE and WebSocket connections first. - **Arc.TypeScript** ([Arc for TypeScript 0.22.0 — grouped options](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.22.0)): `createHonoWebSockets` for sharing one Node WebSocket helper between your Hono routes and Arc. - **Stage** ([Release v4.16.0](https://github.com/Cratis/Stage/releases/tag/v4.16.0)): The opt-in semantic Stage engine (`Stage__Runtime__Engine=semantic`) can start on a Chronicle event log that already holds events. It rebuilds its semantic world only when that can be done exactly: every projection is mirrored exactly and has caught up with its own events without failed partitions, every logged event converts back exactly, and the history satisfies the model's constraints. Otherwise it refuses with a specific `Unsupported(World)` status. (part of #23) - **Stage** ([Release v4.15.0](https://github.com/Cratis/Stage/releases/tag/v4.15.0)): A render profile can carry the model's `.strings` catalog. Generated validators then resolve `$strings.` rule and requirement messages for the request's UI culture, falling back through its parent cultures to the default locale. The key stays in the validation result's state, and generated rejection specifications compare that key, as the Screenplay reference does. A key missing from the default locale fails planning with `STAGE-ESM-018`. Without a catalog, `$strings` messages are still rejected. (part of #116) - **Arc.TypeScript** ([Arc for TypeScript 0.21.0 — vertical slices and the Library sample](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.21.0)): The Library sample: an event-sourced Arc and Chronicle application with a React frontend using generated proxies. Commands return events, a Chronicle constraint keeps author names unique, projections build the read models, and observable queries update the frontend live. A Docker Compose file starts the Chronicle kernel. - **Arc.TypeScript** ([Arc for TypeScript 0.21.0 — vertical slices and the Library sample](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.21.0)): A vertical slices guide: one file per slice holds the command, its validator and its events, or the read model with its queries and projection, as in Cratis C# applications. Discovery, proxy generation, generated artifact metadata and the ESLint rules all support several artifacts in one file. - **Arc.TypeScript** ([Arc for TypeScript 0.20.0 — Fetch runtimes](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.20.0)): `@cratis/arc.core/fetch`, an entry for runtimes that speak the Fetch API: build an application from explicitly added artifacts (or generated artifact metadata) and serve commands, queries and observable queries over server-sent events with `app.fetch(request)`. Its only platform import is `node:async_hooks`, which Deno, Bun, Cloudflare Workers (with Node.js compatibility) and Next.js provide. - **Arc.TypeScript** ([Arc for TypeScript 0.20.0 — Fetch runtimes](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.20.0)): Verified on Deno 2.9: a command, a query and an observable query over SSE. Bun, Cloudflare Workers and Next.js route handlers have examples but are not yet verified. - **Arc.TypeScript** ([Arc for TypeScript 0.19.0 — setup, configuration and host integrations](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.19.0)): `builder.withChronicle(...)`, `builder.withMongoDB(...)` and `builder.withDrizzle(...)`, named like .NET's `WithChronicle` and `WithMongoDB`. Importing an integration package adds its method to the builder through a typed extension that also works when two copies of `@cratis/arc.core` are installed. - **Arc.TypeScript** ([Arc for TypeScript 0.19.0 — setup, configuration and host integrations](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.19.0)): Configuration like .NET's: `ArcApplication.createBuilder()` reads the `Cratis:Arc`, `Cratis:Chronicle` and `Cratis:MongoDB` sections from `appsettings.json` and `appsettings.{Environment}.json`, and from `Cratis__...` environment variables. Values are converted per setting, .NET key names such as `CorrelationId:HttpHeader` and `GeneratedApis:EnableQueryHttpMethod` are accepted, other sections are ignored, and options set in code win. Use `configuration: false` to opt out or `configuration: { file, env }` to choose the source. - **Arc.TypeScript** ([Arc for TypeScript 0.19.0 — setup, configuration and host integrations](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.19.0)): `@cratis/cratis`, the counterpart of the C# `Cratis` package: `CratisApplication.createBuilder()` or `builder.addCratis()` sets up Arc with Chronicle in one call. Unlike C#, it installs no authentication handler; choose one explicitly. - **Arc.TypeScript** ([Arc for TypeScript 0.19.0 — setup, configuration and host integrations](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.19.0)): Express: `app.use(cratisArc(arc))` and `cratisArc(arc).injectWebSocket(server)` for observable queries over WebSockets. - **Arc.TypeScript** ([Arc for TypeScript 0.19.0 — setup, configuration and host integrations](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.19.0)): Fastify: `await app.register(cratisArc, { arc })` registers HTTP routes and WebSockets in one call, in either order with `@fastify/websocket`, and respects mount prefixes. - **Arc.TypeScript** ([Arc for TypeScript 0.19.0 — setup, configuration and host integrations](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.19.0)): Hono: `app.use(cratisArc(arc))` with `cratisArc(arc).injectWebSocket(server)`, or `serveCratisArc(app, arc, { port })`. - **Arc.TypeScript** ([Arc for TypeScript 0.19.0 — setup, configuration and host integrations](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.19.0)): `app.fetch(request)` and `app.handle(request)` on the built application, usable as detached functions, for hosts that speak the Fetch API. Only Node.js is verified. - **Arc.TypeScript** ([Arc for TypeScript 0.18.1 — package contents](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.18.1)): Every package has a README that describes what it contains and links to its documentation. - **Arc.TypeScript** ([Arc for TypeScript 0.18.0 — RxJS observable queries](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.18.0)): Observable queries can return RxJS subjects and observables, just as a C# query returns `ISubject`. A `BehaviorSubject` answers plain HTTP requests with its current value (200), while a `Subject`, `ReplaySubject` or `Observable` without a current value answers 202 or waits, as in .NET. Completion, errors and client disconnects end the subscription. Async iterables keep working. - **Arc.TypeScript** ([Arc for TypeScript 0.18.0 — RxJS observable queries](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.18.0)): The proxy generator and generated artifact metadata recognize RxJS `Observable`, `Subject`, `BehaviorSubject` and `ReplaySubject` return types as observable queries. - **Arc.TypeScript** ([Arc for TypeScript 0.18.0 — RxJS observable queries](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.18.0)): `observeIterable()`, `observeByIdIterable()` (MongoDB) and `watchIterable()` (Chronicle) for code that prefers async iterables. - **Arc.TypeScript** ([Arc for TypeScript 0.18.0 — RxJS observable queries](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.18.0)): `arc-proxygenerator --watch` reports `Watch ready` once the first generation has finished and the watcher is armed, and notices edits to referenced files outside the artifacts folder. - **Arc.TypeScript** ([Arc for TypeScript 0.17.0 — OpenAPI results and proxy improvements](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.17.0)): `/openapi.json` describes results: command and query result envelopes with the typed response or data (from generated artifact metadata), paging on paged queries, and the 200, 400, 403 and 500 responses, plus 202, 408 and 503 for observable queries. - **Arc.TypeScript** ([Arc for TypeScript 0.17.0 — OpenAPI results and proxy improvements](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.17.0)): GET query parameters, including paging and sorting on queries that return collections, and operation summaries from JSDoc comments. - **Arc.TypeScript** ([Arc for TypeScript 0.17.0 — OpenAPI results and proxy improvements](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.17.0)): Bearer security schemes for operations authenticated by `jwtBearer()`, and an `openApiVersion` option for the document's `info.version`. - **Arc.TypeScript** ([Arc for TypeScript 0.17.0 — OpenAPI results and proxy improvements](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.17.0)): Generated proxies for two models with the same class name in different namespaces, using import aliases. - **Arc.TypeScript** ([Arc for TypeScript 0.17.0 — OpenAPI results and proxy improvements](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.17.0)): Identity details types from `@identityDetailsProvider()` classes are generated even without an endpoint that returns them. - **Arc.TypeScript** ([Arc for TypeScript 0.17.0 — OpenAPI results and proxy improvements](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.17.0)): Generated query proxies carry the query's HTTP method preference, and command proxies carry warning handling, as with Arc on .NET's generator. - **Stage** ([Release v4.14.0](https://github.com/Cratis/Stage/releases/tag/v4.14.0)): A conformance suite runs every canonical-corpus specification through Screenplay's reference runner, Stage's semantic engine, and the specifications of the rendered application, and checks that all three agree wherever each can execute it. (part of #15) - **Chronicle.TypeScript** ([Release v6.7.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.7.0)): Read models are recognized from the projections, reducers and model-bound projection decorators that build them, the way the .NET client discovers them, so a read-model class needs no extra decorator. Use `static readModelId` on the class to choose a custom identifier. - **Chronicle.TypeScript** ([Release v6.7.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.7.0)): Event types can be constructed naturally, for example `new TaskCreated(title)`: an event class with a constructor and `@field` properties serializes, generates its schema and deserializes correctly in both standard and legacy decorator modes. - **Arc.TypeScript** ([Arc for TypeScript 0.16.0 — Chronicle aggregates and reactor commands](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.16.0)): `AggregateRoot` and `@inject(commandAggregate(Author))`: a command receives the aggregate for its key, rehydrated from the event log on the command's route. Events passed to `apply()` join the command's batch and are appended when the command succeeds, with a concurrency scope on the event source so a concurrent change is rejected. Aggregates without handlers work too, and handlers are registered per event type with an optional event context. - **Arc.TypeScript** ([Arc for TypeScript 0.16.0 — Chronicle aggregates and reactor commands](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.16.0)): Reactor commands: a Chronicle reactor can return Arc commands, which run through Arc's pipeline in the event's namespace with causation from the event. A failed command fails the reactor partition. - **Arc.TypeScript** ([Arc for TypeScript 0.16.0 — Chronicle aggregates and reactor commands](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.16.0)): Transactional commands: returned events can be combined with command operations again. If Chronicle rejects the append, the operations are compensated; if the outcome is unknown, the command is reported as indeterminate. - **Arc.TypeScript** ([Arc for TypeScript 0.16.0 — Chronicle aggregates and reactor commands](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.16.0)): `readModelForValidation()` gives validator predicates the read model for the command's key. - **AI** ([Release v6.1.0](https://github.com/Cratis/AI/releases/tag/v6.1.0)): The GitHub Copilot provider: device-flow sign-in, API-token exchange, harness support, and model listing. It was left behind when the provider backend moved into the package, so Copilot could not be configured at all through `Cratis.AI` - every other vendor could. - **AI** ([Release v6.1.0](https://github.com/Cratis/AI/releases/tag/v6.1.0)): `CopilotCredential.ExpiresAt`, which the device-flow refresh uses to tell when a token has run out. - **Chronicle.TypeScript** ([Release v6.6.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.6.0)): `reactorResultHandler` in `ChronicleOptions` lets an application handle values a reactor returns that are not events, for example commands for a CQRS framework to execute. The handler receives the returned value, the triggering `EventContext`, the reactor type, the event store name and the namespace, and returns `true` when it handled the whole result or `false` to let Chronicle append the events it recognizes. A handler that throws fails the partition, so a side effect is never acknowledged without having run. - **Arc.TypeScript** ([Arc for TypeScript 0.15.0 — generated artifact metadata](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.15.0)): `arc-proxygenerator --metadata ` writes a metadata module from the same analysis that generates proxies: parameter bindings for `handle()`, `provide()` and `@query` methods (services by class, query arguments by name and type, provided values and markers such as `commandContext()`, `abortSignal()` and `commandReadModel()`), result shapes, field options and validator targets. It is the counterpart of Arc on .NET's source-generated metadata. - **Arc.TypeScript** ([Arc for TypeScript 0.15.0 — generated artifact metadata](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.15.0)): `builder.useGeneratedMetadata(metadata)` applies it. Explicit decorator arguments still win, and a stale module fails at startup with a message to regenerate. `--check-metadata` verifies in CI that the committed module matches the source, and `--watch` regenerates it while you develop. - **Arc.TypeScript** ([Arc for TypeScript 0.15.0 — generated artifact metadata](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.15.0)): Nullable service parameters receive `null` when the service is not registered, as in .NET. Unions of several classes and other ambiguous parameters are reported with file and line. - **Arc.TypeScript** ([Arc for TypeScript 0.15.0 — generated artifact metadata](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.15.0)): The Tasks sample uses the C#-shaped commands and queries with generated metadata, and keeps one example with explicit tokens for projects without a generation step. - **Stage** ([Release v4.13.0](https://github.com/Cratis/Stage/releases/tag/v4.13.0)): The Stage sandbox can run a model on the Screenplay executable semantic model with the opt-in `Stage__Runtime__Engine=semantic`. The default engine is unchanged. (part of #23) - **Stage** ([Release v4.13.0](https://github.com/Cratis/Stage/releases/tag/v4.13.0)): Commands run through Screenplay's reference evaluator. That covers authorization, validation rules and requirements, `produces when`, destinations, `$context` values and constraints, so the sandbox behaves as the model specifies. - **Stage** ([Release v4.13.0](https://github.com/Cratis/Stage/releases/tag/v4.13.0)): Accepted events are appended to Chronicle in one atomic call. - **Stage** ([Release v4.13.0](https://github.com/Cratis/Stage/releases/tag/v4.13.0)): Unauthorized commands return 403. Validation and constraint rejections return 400 with the modeled messages and constraint name. Anything the engine cannot realize exactly returns a typed 501. - **Stage** ([Release v4.13.0](https://github.com/Cratis/Stage/releases/tag/v4.13.0)): `/stage/semantic/admission` reports which commands, queries, events and projections the semantic engine supports, and why the others are not supported. (part of #23) - **AI** ([Release v6.0.0](https://github.com/Cratis/AI/releases/tag/v6.0.0)): Model catalog discovery: a provider's published models are read and recorded, so a tier can be resolved from what the vendor actually serves. Includes a background refresh, a `RefreshAvailableModels` command, and an `AvailableAIModelDiscovery` query. - **AI** ([Release v6.0.0](https://github.com/Cratis/AI/releases/tag/v6.0.0)): ChatGPT subscription credentials - sign-in, storage, expiry-aware refresh, and the classification of whether a provider was given an API key or a subscription record. - **AI** ([Release v6.0.0](https://github.com/Cratis/AI/releases/tag/v6.0.0)): Claude Code and OpenAI Codex as provider transports. The Anthropic client now routes to Claude Code when the credential is an OAuth token, which the Messages API will not accept. - **AI** ([Release v6.0.0](https://github.com/Cratis/AI/releases/tag/v6.0.0)): Provider pools with failure- and capacity-aware member selection, plus `PoolMemberSelector.Candidates` for callers that fail over rather than picking once. - **AI** ([Release v6.0.0](https://github.com/Cratis/AI/releases/tag/v6.0.0)): Rate-limit cooldowns, per-provider usage ceilings, configurable concurrency, and usage snapshots. - **AI** ([Release v6.0.0](https://github.com/Cratis/AI/releases/tag/v6.0.0)): `IDefaultAgentInvocationModes`, which says whether a purpose runs as a job or a chat when no configured agent claims it. - **AI** ([Release v6.0.0](https://github.com/Cratis/AI/releases/tag/v6.0.0)): Generated TypeScript proxies for all of the above, published in `@cratis/ai`. - **Arc.TypeScript** ([Arc for TypeScript 0.14.0 — SQL read models with Drizzle](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.14.0)): `builder.addDrizzle({ database | databaseFactory, dialect })`, or the standalone `addDrizzle(builder, options)` function, with a Drizzle database per tenant. A single `database` serves only the default tenant, and a missing tenant fails instead of reading shared data. - **Arc.TypeScript** ([Arc for TypeScript 0.14.0 — SQL read models with Drizzle](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.14.0)): `drizzleDatabase()` injects the tenant's Drizzle database into commands and queries, and `drizzleReadModel(Model)` injects a read-only handle for a read model with `find`, `findOne` and `queryPage`. - **Arc.TypeScript** ([Arc for TypeScript 0.14.0 — SQL read models with Drizzle](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.14.0)): `queryPage` pushes Arc paging and sorting down to SQL with a count and a page-size cap. Only the read model's declared fields that are table columns can be sorted or selected; other fields answer 400. - **Arc.TypeScript** ([Arc for TypeScript 0.14.0 — SQL read models with Drizzle](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.14.0)): Column codecs for concepts, Guids, `DateOnly`, `TimeOnly`, `TimeSpan` and JSON on PostgreSQL, MySQL and SQLite, mapped from Arc field metadata. - **Arc.TypeScript** ([Arc for TypeScript 0.14.0 — SQL read models with Drizzle](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.14.0)): Guides for getting started, column types and conversions, tenancy, read-only access and paging, including how the Drizzle choice compares with Kysely, Prisma and TypeORM and which Entity Framework Core features are not ported. - **Arc.TypeScript** ([Arc for TypeScript 0.13.0 — observability, interceptors and derived types](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.13.0)): OpenTelemetry tracing and metrics through `@opentelemetry/api`, using Arc on .NET's `Cratis.Arc` source, span names and tag names for commands, command filters, queries and query filters, plus spans for HTTP handling, observable subscriptions and identity resolution, and duration histograms. Spans carry the correlation id. Install and configure any OpenTelemetry SDK in your application; without one, tracing is a no-op. - **Arc.TypeScript** ([Arc for TypeScript 0.13.0 — observability, interceptors and derived types](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.13.0)): `QueryRenderer` to turn a query result into what is sent (the first renderer that can render a result wins), and `ReadModelInterceptor` to adjust read models before they are sent, including every emission of an observable query. Both are registered on the builder or discovered, and run in the request or subscription scope. - **Arc.TypeScript** ([Arc for TypeScript 0.13.0 — observability, interceptors and derived types](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.13.0)): Derived types on the wire: a field declared with a base type accepts and returns classes marked with Fundamentals `@derivedType('id')`, using .NET's `_derivedTypeId` discriminator, and JSON Schema in introspection and OpenAPI describes the alternatives. - **Arc.TypeScript** ([Arc for TypeScript 0.13.0 — observability, interceptors and derived types](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.13.0)): `@field(Number, { namedFloats: true })` accepts `"NaN"`, `"Infinity"` and `"-Infinity"` for a field, matching .NET's named floating-point literals. - **Orleans** ([Release v1.6.0](https://github.com/Cratis/Orleans/releases/tag/v1.6.0)): `Orleans.Storage.Sql.Specs`. There was no specs project for the SQL provider at all, which is why a provider that could not create its own schema looked healthy. The specs run against a real SQLite database rather than substitutes - a mocked `DbContext` never touches a schema, so it cannot see this class of defect. - **Orleans** ([Release v1.6.0](https://github.com/Cratis/Orleans/releases/tag/v1.6.0)): An end-to-end integration spec for a job with a genuinely failing step, against a real silo and a real MongoDB, asserting the failed step stays readable. - **AI** ([Release v5.0.0](https://github.com/Cratis/AI/releases/tag/v5.0.0)): `TierModelAssignment`, which infers the tier ladder from a provider's own catalog: the words vendors use at the small and large ends of their range, with the highest version winning inside a rung. - **Arc.TypeScript** ([Arc for TypeScript 0.12.0 — Chronicle event sourcing](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.12.0)): `builder.addChronicle({ client | connectionString, eventStore, ... })`, or the standalone `addChronicle(builder, options)` function. Each tenant uses its own Chronicle namespace, and discovered event types, projections, reducers and reactors are registered with the event store. - **Arc.TypeScript** ([Arc for TypeScript 0.12.0 — Chronicle event sourcing](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.12.0)): Events returned from a command's `handle()` are appended after the command succeeds: a single event, an array of events, `tuple(...)` with a client response, or `eventForEventSourceId(...)` for another event source. The event source id comes from the command key (`@key()`, `getKey()` or a key resolver), and `eventSourceIdResponse(id)` lets a command choose it explicitly. - **Arc.TypeScript** ([Arc for TypeScript 0.12.0 — Chronicle event sourcing](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.12.0)): `@eventSourceType`, `@eventStreamType`, `@eventStreamId`, `@eventSubject` and tags route appended events, and `eventsWithConcurrencyScopes(...)` sets expected sequence numbers, including "before first". Constraint and concurrency violations come back as validation results. - **Arc.TypeScript** ([Arc for TypeScript 0.12.0 — Chronicle event sourcing](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.12.0)): Events returned from nested commands in the same request are appended in one batch with the outer command's events, only when the outer command succeeds. - **Arc.TypeScript** ([Arc for TypeScript 0.12.0 — Chronicle event sourcing](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.12.0)): `@inject(commandReadModel(Author))` gives `handle()` or `provide()` the read model for the command's key, from Chronicle (`ChronicleReadModelForCommandResolver`) or MongoDB, with `{ optional: true }` for a model that may not exist. Ownership conflicts between resolvers fail at startup. - **Arc.TypeScript** ([Arc for TypeScript 0.12.0 — Chronicle event sourcing](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.12.0)): `ChronicleReadModels` for reading Chronicle read models in queries, including observable queries. - **Arc.TypeScript** ([Arc for TypeScript 0.12.0 — Chronicle event sourcing](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.12.0)): `@notAudited()` keeps a command property out of the causation chain. - **Arc.TypeScript** ([Arc for TypeScript 0.12.0 — Chronicle event sourcing](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.12.0)): `@cratis/arc.chronicle/testing` with `ChronicleCommandScenario`, an in-memory event log and `shouldHaveAppendedEvent(Event, eventSourceId?, predicate?)`, scoped to each execution. - **Screenplay** ([Release v4.30.0](https://github.com/Cratis/Screenplay/releases/tag/v4.30.0)): `CodeBlockSyntax.BodyStartOffset`, `BodyEndOffset`, `BodyStart`, `BodyEnd` and `BodyLines`: the body's span in the document (UTF-16 offsets, BOM-less, as editors address text) and, for each body line, the original line and the column where its content starts after the common indentation is removed. This covers fenced bodies with a language info string and the legacy tag-line form, CRLF documents, tabs, blank and under-indented lines, and bodies at the end of a file. - **Screenplay** ([Release v4.30.0](https://github.com/Cratis/Screenplay/releases/tag/v4.30.0)): `SemanticImplementationRequirement.BodySpan` and `BodyLines` (`SemanticImplementationBodySpan`, `CodeBlockSourceLine`): the same map for each implementation attachment. A file attachment whose contents were supplied spans the whole file; an unresolved file attachment and an inline body without parser positions have no span. - **Screenplay** ([Release v4.30.0](https://github.com/Cratis/Screenplay/releases/tag/v4.30.0)): The MCP `implementation-requirements` views (workspace and proposal) return `bodySpan` and `bodyLines`, run-length encoded where consecutive lines share a column, so a long body stays within a page. - **Arc.TypeScript** ([Arc for TypeScript 0.11.0 — authorization policies and identity](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.11.0)): Named authorization policies: register a policy class (resolved from the execution scope with constructor injection) or a function with `builder.addAuthorizationPolicy('Name', policy)`, and require it with `@authorize('Name')` or `@authorize({ policy, roles })` on commands, read models and query methods. A policy receives the principal, the target and the resource, can be asynchronous, and an unknown policy fails at startup. - **Arc.TypeScript** ([Arc for TypeScript 0.11.0 — authorization policies and identity](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.11.0)): `@authorize({ schemes: [...] })` selects which Arc authentication handlers may authenticate a caller for an operation. - **Arc.TypeScript** ([Arc for TypeScript 0.11.0 — authorization policies and identity](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.11.0)): `jwtBearer({ jwksUri, issuer, audience, ... })` validates bearer tokens with `jose`: asymmetric algorithm allowlist, issuer, audience, lifetime and clock skew, and cached JWKS with configurable timeouts. Requests without a Bearer header are left anonymous for other handlers and anonymous operations. - **Arc.TypeScript** ([Arc for TypeScript 0.11.0 — authorization policies and identity](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.11.0)): `microsoftIdentityPlatform()` authenticates callers from Azure App Service and Container Apps authentication headers (`x-ms-client-principal`, `-id`, `-name`), stripping caller-supplied identity claims the same way Arc on .NET does. It only reads these headers when you register it. - **Arc.TypeScript** ([Arc for TypeScript 0.11.0 — authorization policies and identity](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.11.0)): `@identityDetailsProvider()` lets discovery find the identity details provider, as Arc on .NET does, and model-bound identity details types describe `/.cratis/identity-details/schema`. - **Arc.TypeScript** ([Arc for TypeScript 0.11.0 — authorization policies and identity](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.11.0)): The `development` tenant source, matching .NET's development tenant resolver. - **Arc.TypeScript** ([Arc for TypeScript 0.11.0 — authorization policies and identity](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.11.0)): New documentation for authorization and identity (`Documentation/identity`) and tenant resolvers (`Documentation/tenancy`). - **Arc.TypeScript** ([Arc for TypeScript 0.10.0 — ESLint rules for Arc artifacts](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.10.0)): `@cratis/eslint-plugin-arc-core` for ESLint 10 flat config, with a `recommended` config and a `recommended-type-checked` config for projects that lint with type information. - **Arc.TypeScript** ([Arc for TypeScript 0.10.0 — ESLint rules for Arc artifacts](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.10.0)): Rules that carry Arc on .NET's diagnostic ids where the check applies to TypeScript: ARC0002, ARC0003, ARC0004, ARC0005, ARC0010, ARC0012, ARC0014, ARC0015 and ARC0019. Each id has a documentation page with the reason, a failing example and the fix, and every other .NET id is listed with why it does not apply. - **Arc.TypeScript** ([Arc for TypeScript 0.10.0 — ESLint rules for Arc artifacts](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.10.0)): TypeScript-specific rules for the decorator programming model: properties without `@field`, decorated `declare` fields, `@inject` tokens and `@query` descriptors that do not match the method's parameters, decorators placed where they have no effect, artifacts that are not exported, and validators without a `@validator(Target)` target. An opt-in rule checks that query argument names match parameter names. - **Arc.TypeScript** ([Arc for TypeScript 0.10.0 — ESLint rules for Arc artifacts](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.10.0)): Arc decorators are recognized through their imports from `@cratis/arc.core` and `@cratis/fundamentals`, including aliased and namespace imports, so decorators with the same names from other libraries are not reported. - **Screenplay** ([Release v4.29.0](https://github.com/Cratis/Screenplay/releases/tag/v4.29.0)): A `policy` with a `csharp` body or a `file` binds as an opaque policy-predicate attachment with a stable requirement id and the capability `pure` (`SemanticOpaquePolicyCondition`). A model that has one is ESM v3, like models with reducer bodies or code validation; other models keep their bytes. - **Screenplay** ([Release v4.29.0](https://github.com/Cratis/Screenplay/releases/tag/v4.29.0)): `SemanticExecutionCapability.Authorization`, reported when authorization cannot be decided without running policy code. - **Screenplay** ([Release v4.29.0](https://github.com/Cratis/Screenplay/releases/tag/v4.29.0)): PLAY0440: a policy combines `require` with an inline code block or a file. A policy has one form or the other. - **Screenplay** ([Release v4.29.0](https://github.com/Cratis/Screenplay/releases/tag/v4.29.0)): PLAY0441: a policy has more than one `require` line. Combine the conditions with `and`/`or` in one `require`. - **Screenplay** ([Release v4.29.0](https://github.com/Cratis/Screenplay/releases/tag/v4.29.0)): Proposed decision record 0005: policy predicates as an implementation-attachment role, and authored-order composition. - **Stage** ([Release v4.12.0](https://github.com/Cratis/Stage/releases/tag/v4.12.0)): A planned artifact now names the semantic identities it realizes: `PlannedArtifact.Sources` is a sorted, distinct list of slice, command, event, read-model, projection, query, concept, type and specification ids. Scaffold artifacts have no sources. Artifact bytes and SHA-256 hashes are unchanged, so a render plan maps every artifact to both its semantic origin and its hash. (#11) - **Arc.TypeScript** ([Arc for TypeScript 0.9.0 — testing scenarios](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.9.0)): `CommandScenario.for(RegisterAuthor)` runs a decorated command through the real pipeline (authorization, validation, `provide()`, `handle()`) with services you override (`scenario.services.addSingleton/addScoped/addTransient`), a principal, tenant and context values, and a serialization round trip through the wire format by default. `execute(...)` and `validate(...)` return results with assertions such as `shouldBeSuccessful()`, `shouldHaveValidationErrors()`, `shouldHaveValidationErrorFor(message)`, `shouldHaveValidationErrorForMember(member)`, `shouldNotBeAuthorized()` and `shouldHaveExceptions()`. - **Arc.TypeScript** ([Arc for TypeScript 0.9.0 — testing scenarios](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.9.0)): Command operation assertions on scenario results: executed, compensated and indeterminate outcomes. - **Arc.TypeScript** ([Arc for TypeScript 0.9.0 — testing scenarios](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.9.0)): `QueryScenario.for(ReadModel, 'method')` performs a `@query` method with arguments, paging and sorting through the real query pipeline. - **Arc.TypeScript** ([Arc for TypeScript 0.9.0 — testing scenarios](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.9.0)): `ObservableQueryScenario` collects emissions from an observable query within one explicit deadline and reports whether the stream completed. - **Arc.TypeScript** ([Arc for TypeScript 0.9.0 — testing scenarios](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.9.0)): `shouldHaveValidationErrors()` refuses to pass when the only failures come from unavailable dependencies or failing validators, so a misconfigured test cannot pass for the wrong reason. - **Arc.TypeScript** ([Arc for TypeScript 0.9.0 — testing scenarios](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.9.0)): The Tasks sample includes command and query specs written with the scenarios. - **Arc.TypeScript** ([Arc for TypeScript 0.8.0 — MongoDB integration](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.8.0)): `builder.addMongoDB({ server | client | serverResolver, database | databaseNameResolver, ... })`, or the standalone `addMongoDB(builder, options)` function. Tenants get their own database (`tasks`, `tasks+acme`), and a server resolver can route tenants to different MongoDB servers. - **Arc.TypeScript** ([Arc for TypeScript 0.8.0 — MongoDB integration](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.8.0)): `mongoCollection(Model)` injects a tenant-scoped collection for a read model into a `@query`, with typed `find`, `queryPage`, `observe` and `observeById`. - **Arc.TypeScript** ([Arc for TypeScript 0.8.0 — MongoDB integration](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.8.0)): A metadata-driven BSON codec that reads and writes documents the way Arc on .NET does: `@key()` or `id` as `_id`, Guids as UUID binary (subtype 4), concepts as their primitive values, `DateOnly`, `TimeOnly`, `TimeSpan` and `Date` in .NET's formats, nested models and arrays, and `@derivedType` discriminators in `_derivedTypeId`. - **Arc.TypeScript** ([Arc for TypeScript 0.8.0 — MongoDB integration](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.8.0)): Naming policies: `defaultMongoNamingPolicy` matches an unconfigured .NET MongoDB builder, and `camelCaseMongoNamingPolicy` matches `.WithCamelCaseNamingPolicy()`. Custom policies are supported. - **Arc.TypeScript** ([Arc for TypeScript 0.8.0 — MongoDB integration](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.8.0)): `queryOptions()` gives a query Arc's paging and sorting options, and `queryPage` pushes them down to MongoDB with a count, a page-size cap and a field allowlist. An unknown sort field answers 400. - **Arc.TypeScript** ([Arc for TypeScript 0.8.0 — MongoDB integration](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.8.0)): `observe(filter?)` and `observeById(id)` turn MongoDB change streams into Arc observable queries, with a current value for plain GET and updates over SSE and WebSocket. Replica sets and sharded clusters are supported; a standalone server is rejected with a clear error. - **Stage** ([Release v4.11.0](https://github.com/Cratis/Stage/releases/tag/v4.11.0)): Render read-model and query specifications over read models built by scoped projections. Generated specifications replay every produced event in command order through the generated projection, including joins and removals. Replays that cannot be reproduced exactly fail with `STAGE-ESM-011`. (part of #14) - **Stage** ([Release v4.11.0](https://github.com/Cratis/Stage/releases/tag/v4.11.0)): Render complete given read models in query-only lookup specifications. Given read models before a command are still rejected. (part of #14) - **Stage** ([Release v4.11.0](https://github.com/Cratis/Stage/releases/tag/v4.11.0)): Render `then events in any order` with several events as a multiset match, checking each event's stream and payload. (part of #14) - **Arc.TypeScript** ([Arc for TypeScript 0.7.0 — command context, response handlers and operations](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.7.0)): Command response value handlers: implement `CommandResponseValueHandler` (`canHandle` and `handle`) and register it or let discovery find it. Every handler that can handle a value returned from `handle()` processes it, in a deterministic order, and a handler failure stops the rest. At most one value left unhandled becomes the client response; more than one fails the command. - **Arc.TypeScript** ([Arc for TypeScript 0.7.0 — command context, response handlers and operations](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.7.0)): `CommandContext` for each command execution, carrying the command, its key, context values, correlation id, principal, tenant, allowed severity and cancellation signal. Context value providers and modifiers can add to it. - **Arc.TypeScript** ([Arc for TypeScript 0.7.0 — command context, response handlers and operations](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.7.0)): Command keys: mark one `@field` with `@key()`, implement `getKey()` on the command, or register `CommandKeyResolver` rules ahead of the default resolver. - **Arc.TypeScript** ([Arc for TypeScript 0.7.0 — command context, response handlers and operations](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.7.0)): Parameter markers for `handle()` and `provide()`: `@inject(abortSignal(), commandContext(), provided(Type))` binds the cancellation signal, the command context and values returned from `provide()` by type. - **Arc.TypeScript** ([Arc for TypeScript 0.7.0 — command context, response handlers and operations](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.7.0)): Command operations: `handle()` can return operations (and operation batches) that are checked before any runs, executed in order, and compensated in reverse order within a timeout when the command fails before anything commits. Execution scopes report an explicit commit disposition, an unknown commit outcome is reported as indeterminate rather than success, and recovery details stay on the server. Operations are rejected from nested commands and from commands that ran nested commands, so every effect stays inside one recovery boundary. - **Arc.TypeScript** ([Arc for TypeScript 0.6.0 — proxies from TypeScript source](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.6.0)): `arc-proxygenerator --project --artifacts --output ` reads your TypeScript program with the compiler API, without running your application, and writes proxies for the published `@cratis/arc` and `@cratis/arc.react` clients: commands with `use()` hooks, snapshot and observable queries with parameters, paging, sorting, `use`, `useWithPaging`, `useSuspense` and `when`, models, enums and derived types. - **Arc.TypeScript** ([Arc for TypeScript 0.6.0 — proxies from TypeScript source](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.6.0)): Command and query result types come from the return types of `handle()` and `@query` methods, so nothing is declared twice. Field optionality, nullability, defaults and enums come from the same `@optional()`, `@nullable()`, `@defaultValue()` and `@enumeration()` annotations the server uses. - **Arc.TypeScript** ([Arc for TypeScript 0.6.0 — proxies from TypeScript source](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.6.0)): Client-safe validation rules from `@validator(Target)` classes are generated into the proxies. Rules the browser cannot evaluate stay on the server and are reported by the generator. - **Arc.TypeScript** ([Arc for TypeScript 0.6.0 — proxies from TypeScript source](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.6.0)): Routes and query names come from the same discovery walk and route rules the server uses, with `--root-namespace`, `--segments-to-skip`, `--api-prefix`, `--skip-command-name-in-route` and `--skip-query-name-in-route` options named after the .NET generator's settings. - **Arc.TypeScript** ([Arc for TypeScript 0.6.0 — proxies from TypeScript source](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.6.0)): Output management like .NET's generator: ownership headers with content hashes, unchanged files left untouched, stale generated files and barrels removed, hand-written files and barrel lines preserved, plus `--use-proxy-file-suffix`, `--emit-interfaces`, `--skip-index-generation`, `--skip-output-deletion` and `--js-import-specifiers`. - **Arc.TypeScript** ([Arc for TypeScript 0.6.0 — proxies from TypeScript source](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.6.0)): The Tasks sample has a `generate-proxies` script. - **Chronicle.TypeScript** ([Release v6.5.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.5.0)): `readModels.findInstanceById(type, id)` returns `null` when no instance exists, so callers can tell a missing read model from an empty one. - **Chronicle.TypeScript** ([Release v6.5.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.5.0)): `EventSequenceNumber.beforeFirst` for expressing "no events appended yet" as an expected sequence number in a concurrency scope. - **Chronicle.TypeScript** ([Release v6.5.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.5.0)): `isRegisteredEvent(store, value)` tells whether a value is an instance of an event type registered with an event store. - **Chronicle.TypeScript** ([Release v6.5.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.5.0)): Scoped `run` methods on the identity, causation and correlation managers, so concurrent or nested operations on a server each keep their own ambient context and restore the previous one afterwards. - **Stage** ([Release v4.10.0](https://github.com/Cratis/Stage/releases/tag/v4.10.0)): The semantic specification engine (`--engine semantic`) now runs specifications with a `given caller`, command authorization and `then denied`. Denied specifications check that nothing was appended. (part of #15) - **Stage** ([Release v4.10.0](https://github.com/Cratis/Stage/releases/tag/v4.10.0)): It evaluates command validation rules and requirements at every severity, matching Screenplay's rule order, messages and default messages, and enforces unique-value and unique-event constraints, including releases, casing and re-claiming one's own value. A constraint rejection carries the constraint name as its code. (part of #15) - **Stage** ([Release v4.10.0](https://github.com/Cratis/Stage/releases/tag/v4.10.0)): `when append` specifications that assert only events now run. (part of #15) - **Stage** ([Release v4.9.0](https://github.com/Cratis/Stage/releases/tag/v4.9.0)): Render portable `unique on ` and `unique event ` constraints as named Chronicle constraints, with every target, release, casing rule and message. Generated specifications prove violations, releases, casing and re-claiming one's own value. Constraints on optional, composite or non-text properties, and several events from one command that target or release a unique-value constraint, still fail with `STAGE-ESM-014`. Chronicle updates its constraint index after commit (Cratis/Chronicle#4123), so a storage failure there is not rejected at append time. (#118) - **Stage** ([Release v4.9.0](https://github.com/Cratis/Stage/releases/tag/v4.9.0)): Commands that produce several unconditional events render, and generated specifications assert each event on its stream in order. A specification may now expect several read models and query results. (part of #14) - **Stage** ([Release v4.9.0](https://github.com/Cratis/Stage/releases/tag/v4.9.0)): Specifications with a `given caller` fixture and `then denied` now render. The caller runs through Arc's principal override, and a denied specification checks that the command was unauthorized, that the policy is registered, and that nothing was appended. Protected-query expectations and claim conditions on the role claim type are still rejected. (part of #57) - **Stage** ([Release v4.9.0](https://github.com/Cratis/Stage/releases/tag/v4.9.0)): Render nested `from` and `clear` blocks, supported `every` event-source mappings, and root and child `RemovedWith` / `RemovedWithJoin`. A differential specification now runs admitted projection shapes through Chronicle and compares the results with Screenplay's reference execution. (part of #117) - **Arc.TypeScript** ([Arc for TypeScript 0.5.0 — model-bound commands, read models and validators](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.5.0)): Model-bound commands: a class decorated with `@command()` declares its input with Fundamentals `@field(Type)` and handles itself in `handle()`. An optional `provide()` loads data after validation and passes it to `handle()`, or short-circuits with `rejected(...)` / `denied(...)`. - **Arc.TypeScript** ([Arc for TypeScript 0.5.0 — model-bound commands, read models and validators](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.5.0)): Model-bound read models and queries: a class decorated with `@readModel()` exposes static `@query(...)` methods. `argument(name, Type)` and `service(Token)` describe the parameters in order, and `@query({ observable: true })` serves live results over the same snapshot, SSE, WebSocket and hub transports as `defineObservableQuery`. - **Arc.TypeScript** ([Arc for TypeScript 0.5.0 — model-bound commands, read models and validators](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.5.0)): Concepts from `@cratis/fundamentals` (`ConceptAs` with `static readonly valueType`) on the wire: requests decode into concept, `Guid`, `Date`, `DateOnly`, `TimeOnly` and `TimeSpan` values and responses encode back to primitives. Invalid values answer 400 with `malformedRequest`. - **Arc.TypeScript** ([Arc for TypeScript 0.5.0 — model-bound commands, read models and validators](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.5.0)): Field options `@optional()`, `@nullable()`, `@defaultValue(value)` and `@enumeration(Enum)`, which also shape the JSON Schema in introspection and OpenAPI. - **Arc.TypeScript** ([Arc for TypeScript 0.5.0 — model-bound commands, read models and validators](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.5.0)): Validators with the same vocabulary as the `@cratis/arc` client: `CommandValidator`, `QueryValidator`, `ConceptValidator` and `ModelValidator` declare rules with `ruleFor(...)` (`notEmpty`, `maxLength`, `emailAddress`, `greaterThan`, `must`, `mustAsync`, `when`, `unless`, `withMessage`, `withSeverity`, `withState` and more) and are bound to their target with `@validator(Target)`. Concept validators apply wherever the concept appears, member paths use client casing, and validators are created per execution scope. - **Arc.TypeScript** ([Arc for TypeScript 0.5.0 — model-bound commands, read models and validators](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.5.0)): Authorization decorators `@roles(...)`, `@authorize()` and `@allowAnonymous()` on commands, read models and query methods. A method declaration overrides its class, stacked declarations must all pass, and contradictory declarations fail at startup. - **Arc.TypeScript** ([Arc for TypeScript 0.5.0 — model-bound commands, read models and validators](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.5.0)): `@path(...)` to override a query route, and `generatedApis` options (`routePrefix`, `segmentsToSkipForRoute`, `includeCommandNameInRoute`, `includeQueryNameInRoute`) for conventional routes derived from the folder a command or read model lives in, matching Arc on .NET. - **Arc.TypeScript** ([Arc for TypeScript 0.5.0 — model-bound commands, read models and validators](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.5.0)): Dependency injection with classes as service tokens: `builder.services.addSingleton/addScoped/addTransient(Token, implementation?)`, `@singleton()`, `@scoped()`, `@transient()`, `@injectable(...)` and `@inject(...)`. Both TC39 standard decorators and legacy `experimentalDecorators` with `emitDecoratorMetadata` are supported; in legacy mode `@inject()` can read parameter types. - **Arc.TypeScript** ([Arc for TypeScript 0.5.0 — model-bound commands, read models and validators](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.5.0)): `ArcApplication.createBuilder(options)` with `discover(folder)` and `add(...)`, `build()`, a blocking `run()` that shuts down on SIGINT or SIGTERM, and `start()` / `stop()` for embedding. Express, Fastify and Hono mounts accept - **Stage** ([Release v4.8.0](https://github.com/Cratis/Stage/releases/tag/v4.8.0)): Run Screenplay specifications in memory against the executable semantic model with SpecRunner's opt-in `--engine semantic`. It addresses specifications by semantic id through `--specification` and `--scope`, and writes a `stage-spec-run/1` report. A specification the engine cannot execute exactly is reported `Unsupported` with a typed capability before it runs, so it is never reported as passing; there is no `Inconclusive` outcome. The default structural engine is unchanged. (part of #15) - **Stage** ([Release v4.8.0](https://github.com/Cratis/Stage/releases/tag/v4.8.0)): `Cratis.Stage.Specifications` provides `ISemanticSpecificationExecutor`, and `Cratis.Stage.Contracts` provides the semantic run report and a `.play` source loader. Commands run through Arc's command scenario against a fresh in-memory Chronicle event log for each specification. Results are checked against Screenplay's reference runner on the canonical corpus. (part of #15) - **Screenplay** ([Release v4.28.0](https://github.com/Cratis/Screenplay/releases/tag/v4.28.0)): `AttachmentFiles.Load(root, documents)` reads the files named by a model's implementation attachments (reducer rules, validation rules and code validation, command handlers, policies, reactions, query performers, file constraints) from a model root and returns their contents with warning diagnostics for anything it refuses. Pass `Contents` to `SemanticDocumentSet.Create(documents, catalog, contents)`. - **Screenplay** ([Release v4.28.0](https://github.com/Cratis/Screenplay/releases/tag/v4.28.0)): `ScreenplayWorkspace.WithAttachmentContents(contents, diagnostics)` and a matching `ScreenplayWorkspace.Create` overload carry host-supplied contents through every workspace compilation, proposal and transaction. The workspace itself never reads files, and its revision and serialized bytes do not depend on attachment contents. - **Screenplay** ([Release v4.28.0](https://github.com/Cratis/Screenplay/releases/tag/v4.28.0)): PLAY0430–PLAY0434 warnings for an attachment that is refused or missing: a path that is absolute or leaves the model root, a link, a missing file, a file over 2 MiB (or a set over 8 MiB), and content that is not UTF-8 text. A refused attachment stays unresolved; it never fails a model that compiled before. - **Stage** ([Release v4.7.0](https://github.com/Cratis/Stage/releases/tag/v4.7.0)): Render portable Screenplay policies for commands and queries as registered Arc authorization policies, including module- and feature-level `authorize`. A command or query is `[AllowAnonymous]` only when no authorization applies. Expressions Arc would enforce differently fail with `STAGE-ESM-015`: role-only or claim-only policies that do not require authentication, ambiguous command subjects, and non-text claim targets. (part of #57) - **Stage** ([Release v4.7.0](https://github.com/Cratis/Stage/releases/tag/v4.7.0)): Render all thirteen ESM validation rule kinds, concept validation rules and command requirements as generated validators, with the reference default messages. Warning and information severities, `$strings.` messages, and combinations whose failure order Arc cannot preserve are still rejected. (part of #116) - **Stage** ([Release v4.7.0](https://github.com/Cratis/Stage/releases/tag/v4.7.0)): Render ESM projection scopes: several `from` events, root joins, children identified by a property, and property and arithmetic mappings. Several read models and keyed queries in one state-view slice are now admitted. Nested blocks, `every`/`all`, removals, composite keys, event-context mappings, whole-number arithmetic, and scopes that leave a required property unset fail with `STAGE-ESM-017`. (part of #117) - **Stage** ([Release v4.7.0](https://github.com/Cratis/Stage/releases/tag/v4.7.0)): Render `given` events that state their event source in generated command, read-model and query specifications. Read-model and query assertions without `exactly` now check only the stated properties, as the reference does, and query specifications check projected state. (part of #14) - **Stage** ([Release v4.7.0](https://github.com/Cratis/Stage/releases/tag/v4.7.0)): Generated rejection specifications now check the first validation message against the modeled `then error`. - **Screenplay** ([Release v4.27.0](https://github.com/Cratis/Screenplay/releases/tag/v4.27.0)): A named rule with a `csharp` body or a `file` on a command property or a concept (`invoiceNumber rule BeUnusedInvoiceNumber file Validations/BeUnusedInvoiceNumber.cs`), and a command's `validate csharp` block, bind as opaque rule-predicate and code-validation attachments. Each carries what it guards, its message (including `$strings` keys) and severity, a stable requirement id and the capability `pure`. A bare named rule with neither body nor file is still rejected. - **Screenplay** ([Release v4.27.0](https://github.com/Cratis/Screenplay/releases/tag/v4.27.0)): `SemanticCodeValidation`, `SemanticCommand.CodeValidations`, `SemanticValidationRule.Name` and `SemanticValidationRule.RequirementId`, and the `SemanticValidationRuleKind` members `RulePredicate` and `CodeValidation`. - **Components** ([Release v4.14.0](https://github.com/Cratis/Components/releases/tag/v4.14.0)): `Column.filterOptions` supplies the values a column can be filtered by, rendered as a list instead of a free-form input, with the match modes narrowed to equals/not equals. - **Components** ([Release v4.14.0](https://github.com/Cratis/Components/releases/tag/v4.14.0)): `selectionMode='multiple'` on the data tables and `DataPage`, with a checkbox per row, a select-all header checkbox, and `selectedItems`/`onSelectedItemsChange`. - **Components** ([Release v4.14.0](https://github.com/Cratis/Components/releases/tag/v4.14.0)): `dataTable.selectAllRows` message for localizing the select-all accessible name. - **Screenplay** ([Release v4.26.0](https://github.com/Cratis/Screenplay/releases/tag/v4.26.0)): A reducer whose every `on ` rule has a body, inline or in a `file`, binds to a reducer contract in the executable semantic model: the read model it builds, the events it consumes, a key fixed to the event source id, no initial state, and a result that is the new state or a delete, as Chronicle runs reducers. Inline and file bodies bind to the same contract. The body stays opaque code, not portable meaning. - **Screenplay** ([Release v4.26.0](https://github.com/Cratis/Screenplay/releases/tag/v4.26.0)): ESM v3. A model is serialized as v3 only when it contains a bodied reducer; every other model keeps its v1 or v2 bytes exactly. v3 includes all of v2. `LanguageVersion.V3`, `SemanticVersion.V3` and `EsmSchemaV3Support` describe it, and a full v3 golden vector pins its canonical form. Reducer transitions are canonicalized by event, so reordering `on` rules does not change a model's revision. - **Screenplay** ([Release v4.26.0](https://github.com/Cratis/Screenplay/releases/tag/v4.26.0)): Implementation requirements carry `RequirementId` (derived from the owning construct, role and member, never from a path), `ContextVersion` and `ResultVersion`, `RequiredCapability` (`pure` for reducer transitions) and `AttachmentResolution`. - **Screenplay** ([Release v4.26.0](https://github.com/Cratis/Screenplay/releases/tag/v4.26.0)): `SemanticDocumentSet.Create(documents, catalog, attachmentContents)` lets a host supply the contents of `file` attachments, which are then identified by a hash of their content. Without supplied contents a file attachment is reported as `UnresolvedFile` with no hash; the file compiler, MCP server and Tool supplying contents is tracked in #244. - **Screenplay** ([Release v4.26.0](https://github.com/Cratis/Screenplay/releases/tag/v4.26.0)): PLAY0398: a reducer mixes rules with and without a body. - **Screenplay** ([Release v4.26.0](https://github.com/Cratis/Screenplay/releases/tag/v4.26.0)): PLAY0399: a reducer has more than one rule for the same event. - **Screenplay** ([Release v4.25.0](https://github.com/Cratis/Screenplay/releases/tag/v4.25.0)): `reads as [by ]` names a read, so a command can read the same view twice, for example `reads Account as source by fromId` and `reads Account as destination by toId`. A `require` path can use the alias as its qualifier: `require source.balance >= amount`. - **Screenplay** ([Release v4.25.0](https://github.com/Cratis/Screenplay/releases/tag/v4.25.0)): PLAY0410: a command reads the same view more than once and not every read has an alias. - **Screenplay** ([Release v4.25.0](https://github.com/Cratis/Screenplay/releases/tag/v4.25.0)): PLAY0411: two reads of one command use the same alias. - **Screenplay** ([Release v4.25.0](https://github.com/Cratis/Screenplay/releases/tag/v4.25.0)): PLAY0412: a reads alias has the same name as one of the command's properties. - **Screenplay** ([Release v4.25.0](https://github.com/Cratis/Screenplay/releases/tag/v4.25.0)): `ReadsSyntax.Alias`, an init-only property, carries the alias in the syntax tree, syntax JSON, the printer, the TextMate grammar and the Monaco language package (completion, keyword docs, symbols). - **Arc.TypeScript** ([Arc for TypeScript 0.4.0 — observable queries and the Arc package layout](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.4.0)): Observable queries with `defineObservableQuery`: sources can be async iterables, RxJS-style observables or `CurrentValueSubject.of(value)` / `.pending()`. Every subscription runs the query's authorization and validation and owns a service scope. - **Arc.TypeScript** ([Arc for TypeScript 0.4.0 — observable queries and the Arc package layout](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.4.0)): HTTP snapshots of observable queries: 200 with the current value, 202 while no value exists yet, and 408 when `waitForFirstResult` times out. - **Arc.TypeScript** ([Arc for TypeScript 0.4.0 — observable queries and the Arc package layout](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.4.0)): Direct server-sent events and WebSocket streams on a query's own route, and the multiplexed `/.cratis/queries/ws` and `/.cratis/queries/sse` hubs used by the `@cratis/arc` client, with subscription revisions, full and delta transfer modes, and keep-alive. - **Arc.TypeScript** ([Arc for TypeScript 0.4.0 — observable queries and the Arc package layout](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.4.0)): Emission guards (`observableEmissionGuards`) that can allow, suppress or terminate each emission, and an opt-in `/.cratis/queries/health` endpoint that shows callers their own connections. - **Arc.TypeScript** ([Arc for TypeScript 0.4.0 — observable queries and the Arc package layout](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.4.0)): Configurable limits for observable subscriptions, hub connections, queues and frame sizes, per caller and globally, plus `allowedOrigins` for WebSocket upgrades and SSE hub control requests. - **Arc.TypeScript** ([Arc for TypeScript 0.4.0 — observable queries and the Arc package layout](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.4.0)): WebSocket support for Express (upgrade listener), Fastify (through `@fastify/websocket`, reusing an existing registration) and Hono (through `@hono/node-ws`, reusing an existing helper). - **Arc.TypeScript** ([Arc for TypeScript 0.4.0 — observable queries and the Arc package layout](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.4.0)): A standalone Node.js host in `@cratis/arc.core` (`runArc`, `createArcNodeHandler`): HTTP or HTTPS, WebSocket upgrades, static files, SPA fallback, a path base, cache validators and a bounded shutdown. - **Arc.TypeScript** ([Arc for TypeScript 0.4.0 — observable queries and the Arc package layout](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.4.0)): Generated `ObservableQueryFor` proxies for observable queries. - **Chronicle.TypeScript** ([Release v6.4.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.4.0)): Declare event types, read models, projections, reducers, reactors and the other SDK artifacts with TC39 standard decorators, without enabling `experimentalDecorators`. Legacy decorators keep working. - **Chronicle.TypeScript** ([Release v6.4.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.4.0)): Schema support for explicitly typed arrays and for Guid-, Date-, and primitive-backed concepts, with a `static readonly valueType` hint for concepts when no decorator type metadata is emitted. - **Stage** ([Release v4.5.0](https://github.com/Cratis/Stage/releases/tag/v4.5.0)): Admit ESM v2 models from Screenplay 4.20. A command with a typed `produces … for` destination appends to that event source without copying the identity into the event. When a specification states `for ` on its `when` or `then` event, the generated specification checks the appended event on that stream. It also seeds the projected read model there. (#128) - **Screenplay** ([Release v4.24.0](https://github.com/Cratis/Screenplay/releases/tag/v4.24.0)): A workspace transaction that finds two files declaring the same thing returns a typed `ConflictingOwner` conflict naming both paths, instead of a generic compilation failure. Ownership belongs to the file that declares a member, never to a module or feature header restated to place a child (#137) - **Screenplay** ([Release v4.24.0](https://github.com/Cratis/Screenplay/releases/tag/v4.24.0)): Specs pin the round trip of a commented model between a single document and a folder: same semantic revision, same identities, same canonical print, and every comment kept. A folder write is rejected before touching disk when the source changed since the proposal (#137) - **Screenplay** ([Release v4.23.0](https://github.com/Cratis/Screenplay/releases/tag/v4.23.0)): `when append ` specifications: the event goes through append-time constraints and projections, then the stated read models and query results are compared. If the specification asserts events, they must equal the complete set of new facts. Reactions do not run. - **Screenplay** ([Release v4.23.0](https://github.com/Cratis/Screenplay/releases/tag/v4.23.0)): Explicit comparison qualifiers on specification outcomes. Event order defaults to authored order and can be relaxed; read-model and query properties default to subset matching and can be made exact. Conflicting actions and malformed qualifiers are reported (`PLAY0358`, `PLAY0359`). - **Screenplay** ([Release v4.23.0](https://github.com/Cratis/Screenplay/releases/tag/v4.23.0)): An inventory of the code attachments the executable model cannot run yet: command handlers and validation, concept validation, rule and policy predicates, reducer transitions, query performers and reactions. Each is listed with its role, owning declaration, language or file, content hash and source location. It sits on the compilation result, and MCP pages it by workspace revision. Binding still fails closed with `PLAY0268`. - **Screenplay** ([Release v4.23.0](https://github.com/Cratis/Screenplay/releases/tag/v4.23.0)): A `policy` may name its implementation with `file `, as an alternative to inline code. The executable model treats it like a code policy. - **Screenplay** ([Release v4.22.0](https://github.com/Cratis/Screenplay/releases/tag/v4.22.0)): Declarative policies bind into the executable semantic model and are evaluated for commands and queries. A command's or query's effective authorization is its own policies, every enclosing feature's and its module's, combined by AND (#142) - **Screenplay** ([Release v4.22.0](https://github.com/Cratis/Screenplay/releases/tag/v4.22.0)): Specifications accept a `given caller` block (`authenticated`, `role ""`, `claim "" = ""`; a claim may repeat) and a `then denied` outcome, distinct from `then error`. A denied command or query is rejected as `Unauthorized` before validation runs (#142) - **Screenplay** ([Release v4.21.0](https://github.com/Cratis/Screenplay/releases/tag/v4.21.0)): Modules and features accept `authorize`. It combines by AND with the policies of every command and query beneath them, and folder files merge it like behaviors; a repeated identical clause warns with `PLAY0394` (#75) - **Screenplay** ([Release v4.21.0](https://github.com/Cratis/Screenplay/releases/tag/v4.21.0)): Inline code blocks carry their language as a fence info string (` ```csharp `). The previous forms — a language line above a bare fence, and `validate csharp` — still parse with a `PLAY0397` warning, and printing writes the new form (#184) - **Screenplay** ([Release v4.21.0](https://github.com/Cratis/Screenplay/releases/tag/v4.21.0)): Typed accessors beside every `dynamic` context member (`CommandAs()`, `ArgumentsAs()`, `ArtifactAs()`, …), so LINQ in inline code binds at compile time. A payload of another type throws `ContextPayloadTypeMismatch` (#84) - **Screenplay** ([Release v4.21.0](https://github.com/Cratis/Screenplay/releases/tag/v4.21.0)): Canonical corpus vectors: RegisterProject with reordered and relocated documents (same revision and bytes), a pinned ESM v2 vector, and an unsupported vector that fails closed with no artifacts. The corpus package now runs package validation (#168) - **Screenplay** ([Release v4.21.0](https://github.com/Cratis/Screenplay/releases/tag/v4.21.0)): Documentation gates: every construct the parsers accept must have a grammar production and a reference page; every relative link and anchor must resolve and every page must be reachable from navigation. Documentation-only pull requests now run these checks (#146) - **Arc.TypeScript** ([Arc for TypeScript 0.3.0 — generated clients](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.3.0)): `exportClientManifest` writes a versioned JSON client manifest from registered commands and queries that declare an explicit `clientOutput` shape. - **Arc.TypeScript** ([Arc for TypeScript 0.3.0 — generated clients](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.3.0)): `@cratis/arc.server.codegen` renders `@cratis/arc` command and query proxies from that manifest, with `renderClientManifest`, `generateClient`, and a JSON-only CLI that refuses unsafe paths, symlinks, and overwrites of files it does not own. - **Arc.TypeScript** ([Arc for TypeScript 0.3.0 — generated clients](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.3.0)): Generated proxies for flat DTOs, basic and optional inputs, command responses, and DTO or array queries, verified against live Express, Fastify, and Hono hosts with the published `@cratis/arc` client. - **Screenplay** ([Release v4.20.0](https://github.com/Cratis/Screenplay/releases/tag/v4.20.0)): Executable semantic model version 2. It is selected automatically when a model uses a v2 construct and is otherwise unchanged at version 1 (#226, #167): - **Screenplay** ([Release v4.20.0](https://github.com/Cratis/Screenplay/releases/tag/v4.20.0)): Typed state-change destinations: `produces … for ` targets an event source without duplicating the identity into the event. - **Screenplay** ([Release v4.20.0](https://github.com/Cratis/Screenplay/releases/tag/v4.20.0)): Event-source context on facts, which projections read the event-source identity from. - **Screenplay** ([Release v4.20.0](https://github.com/Cratis/Screenplay/releases/tag/v4.20.0)): `for ` event-source assertions on `given` and `then` events, so a specification can name exact streams. For example, a unique constraint can be shown colliding between two event sources. - **Screenplay** ([Release v4.20.0](https://github.com/Cratis/Screenplay/releases/tag/v4.20.0)): `$context.occurred` and the caller's identity (`$context.identity.*`) in `produces`, matching Chronicle's event context. - **Screenplay** ([Release v4.20.0](https://github.com/Cratis/Screenplay/releases/tag/v4.20.0)): Projection variants execute. Each variant is its own read model; entering one removes the entity from its siblings, and projection-level handlers apply to every variant that has the property. This follows how Chronicle's variant support reclassifies them. New errors (`PLAY0382`–`PLAY0385`) cover a variant without `enters on`, an entering event claimed twice, and a shared mapping a variant's read model lacks (#185) - **Screenplay** ([Release v4.20.0](https://github.com/Cratis/Screenplay/releases/tag/v4.20.0)): Validation rules and `require` conditions accept a severity: `information`, `warning` or `error` (the default). Every failing rule still rejects the command, and the rejection reports each failure's severity (#227) - **Screenplay** ([Release v4.20.0](https://github.com/Cratis/Screenplay/releases/tag/v4.20.0)): `require` bodies accept a localized `message $strings.` (#231) - **Arc** ([Release v22.23.0](https://github.com/Cratis/Arc/releases/tag/v22.23.0)): Register scoped, asynchronous authorization policies with `IAuthorizationPolicy` and `AddArcAuthorizationPolicy()` on either Arc host (#2736). - **Arc** ([Release v22.23.0](https://github.com/Cratis/Arc/releases/tag/v22.23.0)): Use ASP.NET Core policies and authentication schemes on model-bound commands, queries, and observable subscriptions, following the [authorization contract](https://github.com/Cratis/Arc/blob/main/decisions/0004-evaluate-authorization-policies-asynchronously.md) (#2736). - **Arc.TypeScript** ([Arc for TypeScript 0.2.0 — services and identity](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.2.0)): Explicit service tokens and singleton, scoped, and transient lifetimes, with owned resource cleanup and real-pipeline testing helpers. - **Arc.TypeScript** ([Arc for TypeScript 0.2.0 — services and identity](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.2.0)): Registry-owned singleton initialization and graceful draining of admitted work without converting committed successes into shutdown failures. - **Arc.TypeScript** ([Arc for TypeScript 0.2.0 — services and identity](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.2.0)): Identity-details endpoints and a size-bounded, Unicode-compatible display cookie that is never used as a credential. - **Arc.TypeScript** ([Arc for TypeScript 0.2.0 — services and identity](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.2.0)): Explicit trusted native-principal integration for Express, Fastify, and Hono, with native TLS handling and preserved routing defenses. - **Arc.TypeScript** ([Arc for TypeScript 0.2.0 — services and identity](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.2.0)): Ordered tenant selection with optional required-tenant and membership enforcement, plus opt-in development user and tenant discovery. - **Arc.Kotlin** ([Release v7.6.0](https://github.com/Cratis/Arc.Kotlin/releases/tag/v7.6.0)): Opt into `Name.proxy.ts` filenames with `cratisArc.proxies.useProxyFileSuffix` or `--use-proxy-file-suffix true`. Generated imports and barrel exports follow the setting, while external mappings and routes stay unchanged. Switching either direction cleans up owned generated files when cleanup is enabled (#229). - **Arc.TypeScript** ([Arc for TypeScript 0.1.0 — source preview](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.1.0)): Schema-backed command and query APIs with validation-only execution, authorization, tenant and correlation context, execution scopes, and paging. - **Arc.TypeScript** ([Arc for TypeScript 0.1.0 — source preview](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.1.0)): Express, Fastify, and Hono adapters for hosting Arc APIs on Node.js. - **Arc.TypeScript** ([Arc for TypeScript 0.1.0 — source preview](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.1.0)): Tenant-aware MongoDB read helpers with trusted filtering and database-owned paging. - **Arc.TypeScript** ([Arc for TypeScript 0.1.0 — source preview](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.1.0)): Introspection, basic OpenAPI descriptions, a runnable Tasks sample, and documentation of supported capabilities and limitations. - **Screenplay** ([Release v4.19.0](https://github.com/Cratis/Screenplay/releases/tag/v4.19.0)): Specification values accept typed single-line objects and lists, such as `lines = [{"sku":"A-1","quantity":2}]` and `tags = []`. Keys are checked against the declared composite type (`PLAY0291`–`PLAY0294`). The values bind to executable composite and array values and run end to end (#215, #207) - **Screenplay** ([Release v4.19.0](https://github.com/Cratis/Screenplay/releases/tag/v4.19.0)): Specifications may state a subset of read-model or query-result properties. A query result may omit the identifier its arguments supply. Specifications with only `given` and `then query`/`then readmodel` steps and no `when` run (#207) - **Screenplay** ([Release v4.19.0](https://github.com/Cratis/Screenplay/releases/tag/v4.19.0)): Commands can produce events conditionally (`produces when …`) with conditions over command properties, and can state `require` conditions over command properties. Each condition is evaluated independently (#210, #209) - **Screenplay** ([Release v4.19.0](https://github.com/Cratis/Screenplay/releases/tag/v4.19.0)): Literal tags on events and `produces` travel as append metadata (#210) - **Screenplay** ([Release v4.19.0](https://github.com/Cratis/Screenplay/releases/tag/v4.19.0)): Constraints accept `released by `, composite properties (`unique a, b on E`), several targets under one name, `message` and `ignore casing` (#212) - **Screenplay** ([Release v4.19.0](https://github.com/Cratis/Screenplay/releases/tag/v4.19.0)): `matches ""` takes an ECMAScript regular expression, and `matches email` is a named pattern with a documented definition (#209) - **Screenplay** ([Release v4.19.0](https://github.com/Cratis/Screenplay/releases/tag/v4.19.0)): Renaming a composite type's property through MCP rewrites the object keys that name it (#215) - **Stage** ([Release v4.2.0](https://github.com/Cratis/Stage/releases/tag/v4.2.0)): Customize generated hosts through optional `ConfigureServices` and `ConfigureApplication` hooks and a `Customizations/Dependencies.props` import, without editing managed files. Includes a catalog adapter example and a customization guide. Modeled capture, reaction, and `file` bindings remain unsupported. (#121) - **Stage** ([Release v4.2.0](https://github.com/Cratis/Stage/releases/tag/v4.2.0)): Load an optional product-owned `Customizations/styles.css` after component tokens and styles, before rendering the frontend. The renderer never emits files into this directory. (#122) - **AI** ([Release v3.4.0](https://github.com/Cratis/AI/releases/tag/v3.4.0)): The social feed post skill now teaches drafting in a human voice: open with something that happened or the reader's concrete problem, talk the way the people who built it would, show the default shape next to the better one, sell with specifics instead of adjectives, put each limit inside the sentence it limits, keep review and evidence language out of the copy, and stop when you are done. - **AI** ([Release v3.4.0](https://github.com/Cratis/AI/releases/tag/v3.4.0)): The voice and cadence skill recognizes five more tells of generated prose: punchline fragments ("They run."), signpost pairs ("That's the X. Here's the Y."), labeled caveats ("One honest limit:"), aphoristic closes and reflexive triplets. - **AI** ([Release v3.4.0](https://github.com/Cratis/AI/releases/tag/v3.4.0)): The voice and cadence skill explains hedged, noncommittal copy as review language leaking into the material, and how to fix it without dropping a true limitation. - **Stage** ([Release v4.1.0](https://github.com/Cratis/Stage/releases/tag/v4.1.0)): Support scalar nested objects, all-event subscriptions, and recursive projection definitions when loading Screenplay models. (#125) - **Screenplay** ([Release v4.18.0](https://github.com/Cratis/Screenplay/releases/tag/v4.18.0)): The executable semantic model admits validation rules beyond `not empty`: `max`/`min` (length on text, value on numbers), `==`/`!=`, `>`/`>=`/`<`/`<=` on numbers, `length ==`, and `all >`/`all >=` over collections of numbers. The reference executor evaluates them all (#209) - **Screenplay** ([Release v4.18.0](https://github.com/Cratis/Screenplay/releases/tag/v4.18.0)): The executable semantic model admits every projection block the way Chronicle lowers it: several events in one `from`, `children`, `nested`, update-only `join`, `every`/`all`, `remove with`, `remove via join`, composite and literal keys, and the `add`/`subtract`/`increment`/`decrement`/`count`/`clear` mappings. The reference executor runs them all (#211) - **Screenplay** ([Release v4.18.0](https://github.com/Cratis/Screenplay/releases/tag/v4.18.0)): The executable semantic model admits `unique on ` and `unique event ` constraints, and the reference executor enforces them with Chronicle's semantics (#212) - **Screenplay** ([Release v4.18.0](https://github.com/Cratis/Screenplay/releases/tag/v4.18.0)): One event-context catalog, matching Chronicle's `EventContext`, is shared by the compiler, the editor and the documentation. The compiler checks `$eventContext` paths against it (`PLAY0295`–`PLAY0299`) and the editor underlines invalid paths (#217) - **Screenplay** ([Release v4.18.0](https://github.com/Cratis/Screenplay/releases/tag/v4.18.0)): MCP `read-proposal` has a `dropped-comments` view, and every proposal reports how many comments it drops (#216) - **Screenplay** ([Release v4.18.0](https://github.com/Cratis/Screenplay/releases/tag/v4.18.0)): A workspace operation replaces one produced-event mapping source in place (#193) - **Screenplay** ([Release v4.18.0](https://github.com/Cratis/Screenplay/releases/tag/v4.18.0)): New warnings: - **Screenplay** ([Release v4.18.0](https://github.com/Cratis/Screenplay/releases/tag/v4.18.0)): `PLAY0290`: an `import` names something the application declares itself (#208) - **Screenplay** ([Release v4.18.0](https://github.com/Cratis/Screenplay/releases/tag/v4.18.0)): `PLAY0340`: the same behavior is attached twice across folder files - **Screenplay** ([Release v4.18.0](https://github.com/Cratis/Screenplay/releases/tag/v4.18.0)): `PLAY0380`: Chronicle's projection lowering drops part of a construct - **Screenplay** ([Release v4.18.0](https://github.com/Cratis/Screenplay/releases/tag/v4.18.0)): `PLAY0381`: a projection-level key does not route events - **AI** ([Release v3.3.0](https://github.com/Cratis/AI/releases/tag/v3.3.0)): A hook guards agent-run `cratis chronicle` commands in Claude and Pi: read-only inspection and help run as before; replay, retry, quarantine clearing, job control, recommendations, and adding or removing users, applications and subscriptions are refused, as is any chronicle command the guard does not recognize. - **AI** ([Release v3.3.0](https://github.com/Cratis/AI/releases/tag/v3.3.0)): A human who has authorized a store mutation can allow it by starting the agent with `CRATIS_HOOKS_ALLOW_STORE_MUTATIONS=1`; the command lists live in `cratis-store-mutations.json` and can be extended per repository. - **Arc** ([Release v22.22.0](https://github.com/Cratis/Arc/releases/tag/v22.22.0)): `CratisProxiesUseProxyFileSuffix` names generated TypeScript files `Name.proxy.ts` instead of `Name.ts`, so generated proxies can be told apart from hand-written TypeScript in the same folders. Imports between generated files and `index.ts` barrels follow the suffix; imports of modules you mapped yourself are left as mapped. Switching the option on or off replaces the previously generated files. Off by default. - **Chronicle** ([Release v19.4.5](https://github.com/Cratis/Chronicle/releases/tag/v19.4.5)): `CHRONICLE_MONGODB_IMAGE` selects the MongoDB image the integration fixtures start. Current MongoDB refuses to start on some host kernels, and the refusal surfaces as a container start timeout that explains nothing, leaving integration scenarios unrunnable on that machine. - **cli** ([Release v3.16.0](https://github.com/Cratis/cli/releases/tag/v3.16.0)): Shell completions offer the AI and LLM command values offline, without calling out to a provider. - **cli** ([Release v3.15.0](https://github.com/Cratis/cli/releases/tag/v3.15.0)): `cratis llm-context` now gives every command an `effect` — `read-only`, `local`, `mutating` or `destructive` — and a `requiresConfirmation` flag, so agents and guards can tell observing commands from state-changing ones without keeping their own lists. - **cli** ([Release v3.15.0](https://github.com/Cratis/cli/releases/tag/v3.15.0)): The `cratis llm-context --schema` JSON Schema, the catalog's tips, the generated `CHRONICLE.md` safety notes and a new LLM Context reference page explain both fields and what each value means. - **cli** ([Release v3.14.0](https://github.com/Cratis/cli/releases/tag/v3.14.0)): `cratis run` accepts a single Screenplay (`.play`) file as well as a folder. Only that file is mounted, read-only, and handed to the Stage; the folder it sits in is not mounted (#128) - **Chronicle.Mcp** ([Release v1.4.0](https://github.com/Cratis/Chronicle.Mcp/releases/tag/v1.4.0)): Every tool declares MCP tool annotations (`readOnlyHint`, `destructiveHint`, `idempotentHint`, `openWorldHint`), so MCP clients can run read-only tools freely and ask before a tool changes state. `stop_job` and `resume_job` are state-changing, non-destructive and idempotent; `delete_job` is state-changing, destructive and idempotent; all other tools are read-only, and every tool is closed-world — it talks only to the configured Chronicle server. (#34) - **Arc** ([Release v22.21.0](https://github.com/Cratis/Arc/releases/tag/v22.21.0)): Analyzer `ARC0021` reports a `Policy` or `AuthenticationSchemes` on an authorization attribute of a model-bound command or read model. Arc enforces authentication and roles but evaluates neither of these, so the artifact is less protected than its attribute reads (#2736) - **Arc** ([Release v22.21.0](https://github.com/Cratis/Arc/releases/tag/v22.21.0)): `IAuthorizationAttributeEvaluator.GetAuthorizationRequirements`, so an evaluator can report every attribute it finds. It defaults to the existing single answer, so existing implementations keep working - **AI** ([Release v3.2.1](https://github.com/Cratis/AI/releases/tag/v3.2.1)): The Decision Engine image is built and pushed to Docker Hub with every release, as `cratis/decision-engine` - **AI** ([Release v3.2.0](https://github.com/Cratis/AI/releases/tag/v3.2.0)): `IDecisions` — submit context plus a finite set of choices, get back every choice with its probability, the highest-probability choice, and the margin to the runner-up. Thresholds are deliberately left to consumers so the raw distribution survives intact (#392) - **AI** ([Release v3.2.0](https://github.com/Cratis/AI/releases/tag/v3.2.0)): A batch overload on `IDecisions` for callers scoring many candidates against one task, with results guaranteed in request order (#392) - **AI** ([Release v3.2.0](https://github.com/Cratis/AI/releases/tag/v3.2.0)): `Decision` as an `AIProviderCapability` and an `AIModelCapability`, advertised independently of the conversational and agentic capabilities (#392) - **AI** ([Release v3.2.0](https://github.com/Cratis/AI/releases/tag/v3.2.0)): `AIProviderType.DecisionEngine` and `AddDecisionEngineProvider` / `ReconfigureDecisionEngineProvider` for configuring decision providers the same way as any other AI provider (#392) - **AI** ([Release v3.2.0](https://github.com/Cratis/AI/releases/tag/v3.2.0)): `AIModelCapabilities.For(AIProviderType, ModelName)` — capability for a decision model is declared by provider type rather than inferred from the model identifier, which carries no marker that would distinguish it from a chat model (#392) - **AI** ([Release v3.2.0](https://github.com/Cratis/AI/releases/tag/v3.2.0)): `AIProviderCapabilities` — what each provider type can be used for. A decision engine advertises `Decision` and neither `Conversational` nor `Agentic`, so existing compatibility checks refuse to schedule an agent onto it (#392) - **AI** ([Release v3.2.0](https://github.com/Cratis/AI/releases/tag/v3.2.0)): `AddCratisAI(ai => ai.WithDecisions())` registers the decision surface. Nothing decision-related is registered when it is not called (#392) - **AI** ([Release v3.2.0](https://github.com/Cratis/AI/releases/tag/v3.2.0)): Telemetry on `Cratis.AI.Decisions`: decision duration, count, and top-probability distribution. Context text is not recorded unless explicitly enabled (#392) - **AI** ([Release v3.2.0](https://github.com/Cratis/AI/releases/tag/v3.2.0)): The Cratis Decision Engine service under `Source/DecisionEngine/` — Decision API v1, CPU-first, model and calibration temperature configurable, with an artifact cache so restarts do not re-download weights (#392) - **release-action** ([Release v1.4.0](https://github.com/Cratis/release-action/releases/tag/v1.4.0)): The issues a release's notes say it resolves are closed when the release is created, each with a comment naming the release tag. Only a note bullet ending in `(#123)` counts; prose mentions and cross-repository references are left alone. Needs `issues: write`, and is turned off with `close-resolved-issues: false` - **Arc** ([Release v22.20.0](https://github.com/Cratis/Arc/releases/tag/v22.20.0)): Analyzer `ARC0019` reports `[AllowAnonymous]` declared on the same class or method as `[Authorize]` or `[Roles]`. Arc resolves that contradiction differently depending on evaluator order — rejecting the call in one order and admitting anonymous callers in the other — so the declaration now fails loudly at build time instead. Overriding a class on one query method is supported and not reported (#2714) - **Arc** ([Release v22.20.0](https://github.com/Cratis/Arc/releases/tag/v22.20.0)): Analyzer `ARC0020` reports `[Authorize]` or `[AllowAnonymous]` from `Microsoft.AspNetCore.Authorization` on a model-bound `[Command]` or `[ReadModel]`. Arc enforces only its own `Cratis.Arc.Authorization` attributes on model-bound artifacts, so the ASP.NET Core attribute protects nothing: a command marked with it is open to every caller. Use the Arc attribute of the same name. Controller-based commands and queries are unaffected (#2719) - **Chronicle.Elixir** ([Release v3.5.0](https://github.com/Cratis/Chronicle.Elixir/releases/tag/v3.5.0)): `encrypted/1,2,3` macro (`Chronicle.Confidentiality`) for values that need encryption at rest without being personal data subject to GDPR right-to-erasure — an API key, a webhook signing secret, a partner credential (Cratis/Chronicle#4095) - **Chronicle.Elixir** ([Release v3.5.0](https://github.com/Cratis/Chronicle.Elixir/releases/tag/v3.5.0)): `Chronicle.Concept` gets its own concept-level `encrypted/0,1` macro, mirroring how `pii/0,1` is the concept-level counterpart to `Chronicle.Compliance.pii/1,2` - **Chronicle.Elixir** ([Release v3.5.0](https://github.com/Cratis/Chronicle.Elixir/releases/tag/v3.5.0)): `EncryptionScope` (`:subject` default, `:namespace`, `:global`) — the identity an `encrypted` value's key is provisioned under. A subject-scoped key is always disjoint from any `pii` key for the same subject; a namespace-scoped key is shared by every value marked that way in one event store namespace; a global-scoped key is shared across the whole installation - **Chronicle.Elixir** ([Release v3.5.0](https://github.com/Cratis/Chronicle.Elixir/releases/tag/v3.5.0)): `pii` and `encrypted` cannot both apply to the same value — rejected at schema-generation time with `Chronicle.Confidentiality.PiiAndEncryptedCombinedNotSupported`, because the two would otherwise encrypt the value twice under two different keys and be unable to release it correctly - **Chronicle.Elixir** ([Release v3.5.0](https://github.com/Cratis/Chronicle.Elixir/releases/tag/v3.5.0)): `encrypted/0,1` cannot be declared on a `Chronicle.Concept` created with `event_source_id: true`, rejected at compile time, mirroring the existing restriction on `pii/0,1` - **Chronicle.Kotlin** ([Release v6.4.0](https://github.com/Cratis/Chronicle.Kotlin/releases/tag/v6.4.0)): `@Encrypted` annotation (`io.cratis.chronicle.confidentiality`) for values that need encryption at rest without being personal data subject to GDPR right-to-erasure — an API key, a webhook signing secret, a partner credential (Cratis/Chronicle#4095) - **Chronicle.Kotlin** ([Release v6.4.0](https://github.com/Cratis/Chronicle.Kotlin/releases/tag/v6.4.0)): `EncryptionScope.Subject` (default), `.Namespace`, and `.Global` — the identity an `@Encrypted` value's key is provisioned under. A subject-scoped key is always disjoint from any `@Pii` key for the same subject; a namespace-scoped key is shared by every value marked that way in one event store namespace; a global-scoped key is shared across the whole installation - **Chronicle.Kotlin** ([Release v6.4.0](https://github.com/Cratis/Chronicle.Kotlin/releases/tag/v6.4.0)): `@Pii` and `@Encrypted` cannot both apply to the same value — rejected at schema-generation time with `PiiAndEncryptedCombinedNotSupported`, because the two would otherwise encrypt the value twice under two different keys and be unable to release it correctly - **Chronicle.Kotlin** ([Release v6.4.0](https://github.com/Cratis/Chronicle.Kotlin/releases/tag/v6.4.0)): `@Encrypted` cannot be applied to an `EventSourceId`-typed concept, flagged with `EncryptedNotSupportedOnEventSourceId`, mirroring the existing restriction on `@Pii` - **Chronicle.TypeScript** ([Release v6.3.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.3.0)): `@encrypted()` decorator (`@cratis/chronicle/confidentiality`) for values that need encryption at rest without being personal data subject to GDPR right-to-erasure — an API key, a webhook signing secret, a partner credential (Cratis/Chronicle#4095) - **Chronicle.TypeScript** ([Release v6.3.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.3.0)): `EncryptionScope.Subject` (default), `.Namespace`, and `.Global` — the identity an `@encrypted()` value's key is provisioned under. A subject-scoped key is always disjoint from any `@pii()` key for the same subject; a namespace-scoped key is shared by every value marked that way in one event store namespace; a global-scoped key is shared across the whole installation - **Chronicle.TypeScript** ([Release v6.3.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.3.0)): `@pii()` and `@encrypted()` cannot both apply to the same value — rejected at schema-generation time with `PIIAndEncryptedCombinedNotSupported`, because the two would otherwise encrypt the value twice under two different keys and be unable to release it correctly - **Chronicle.TypeScript** ([Release v6.3.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.3.0)): `@encrypted()` cannot be applied to the `eventSourceId` property, flagged at decoration time with `EncryptedNotSupportedOnEventSourceId`, mirroring the existing restriction on `@pii()` - **Chronicle** ([Release v19.4.0](https://github.com/Cratis/Chronicle/releases/tag/v19.4.0)): `[Encrypted]` attribute (`Cratis.Chronicle.ProtectedValues`) for values that need encryption at rest without being personal data subject to GDPR right-to-erasure — an API key, a webhook signing secret, a partner credential (#4095) - **Chronicle** ([Release v19.4.0](https://github.com/Cratis/Chronicle/releases/tag/v19.4.0)): `EncryptionScope.Subject` (default), `.Namespace`, and `.Global` — the identity an `[Encrypted]` value's key is provisioned under. A subject-scoped key is always disjoint from any `[PII]` key for the same subject; a namespace-scoped key is shared by every value marked that way in one event store namespace; a global-scoped key is shared across the whole installation - **Chronicle** ([Release v19.4.0](https://github.com/Cratis/Chronicle/releases/tag/v19.4.0)): `[PII]` and `[Encrypted]` cannot both apply to the same value — rejected at schema-generation time, and flagged at compile time by a new analyzer (CHR0053), because the two would otherwise encrypt the value twice under two different keys and be unable to release it correctly - **Chronicle** ([Release v19.4.0](https://github.com/Cratis/Chronicle/releases/tag/v19.4.0)): `[Encrypted]` cannot be applied to an `EventSourceId`, flagged at compile time by a new analyzer (CHR0052), mirroring the existing restriction on `[PII]` - **Chronicle** ([Release v19.4.0](https://github.com/Cratis/Chronicle/releases/tag/v19.4.0)): No API anywhere can delete an `[Encrypted]` value's key — `PIIManager`'s erasure operations explicitly refuse an identifier belonging to an `[Encrypted]` value - **Chronicle** ([Release v19.4.0](https://github.com/Cratis/Chronicle/releases/tag/v19.4.0)): `Cratis.Chronicle.Testing`'s `EventScenario` and related scenario helpers now protect `[Encrypted]` values the same way they already protect `[PII]` values - **Chronicle** ([Release v19.4.0](https://github.com/Cratis/Chronicle/releases/tag/v19.4.0)): `Cratis.Chronicle.Confidentiality` — a security metadata provider system (`ICanProvideSecurityMetadataForType`/`ICanProvideSecurityMetadataForProperty`, `ISecurityMetadataResolver`) parallel to the existing GDPR compliance one, for classifying a value as needing protection for security reasons rather than compliance reasons. `[Encrypted]` is its first consumer; `[PII]` continues to resolve only through the compliance provider system and never gains `[Encrypted]`'s wider scopes - **AI** ([Release v3.1.2](https://github.com/Cratis/AI/releases/tag/v3.1.2)): A Cratis site reference for the documentation writing skill: which teaching components to use (`YouWillLearn`, `Recap`, client-language tabs), how to state an experimental product's maturity, how to state cross-product compatibility, what Prompter records as a documentation-gap signal, and who decides page structure. - **cli** ([Release v3.12.0](https://github.com/Cratis/cli/releases/tag/v3.12.0)): Render generated applications with explicit command inputs and editable keyed lookups using Stage 3.22.0. - **Stage** ([Release v3.22.0](https://github.com/Cratis/Stage/releases/tag/v3.22.0)): Compose exact required String/Guid command inputs and an explicit submit action; show unsupported required fields instead of silently omitting them. (#100) - **Stage** ([Release v3.22.0](https://github.com/Cratis/Stage/releases/tag/v3.22.0)): Generate editable lookup forms for supported optional-single queries alongside command forms, preserving exact entered identifiers and showing returned values or not-found states. (#100) - **Stage** ([Release v3.22.0](https://github.com/Cratis/Stage/releases/tag/v3.22.0)): Bind generated queries by stable source identity so ambiguous names are not silently resolved to another query. (#100) - **Scene** ([Release v3.7.0](https://github.com/Cratis/Scene/releases/tag/v3.7.0)): Let Scene command forms bind exact String and Guid inputs and submit through the native Arc form, showing unsupported required properties instead of silently omitting them. (#7) - **Scene** ([Release v3.7.0](https://github.com/Cratis/Scene/releases/tag/v3.7.0)): Rebind mounted forms when their registered command changes, so submissions use the current proxy and authorization. (#7) - **AI** ([Release v3.1.0](https://github.com/Cratis/AI/releases/tag/v3.1.0)): Selecting the `cratis/screenplay` profile makes the Screenplay MCP server available through the Cratis CLI and each supported client’s native project integration. No separate Screenplay .NET tool installation or manual MCP JSON is needed. - **AI** ([Release v3.1.0](https://github.com/Cratis/AI/releases/tag/v3.1.0)): Pi receives a native Screenplay tool bridge that discovers live tool schemas, honors profile selection and opt-out, and reports errors without retrying an uncertain source mutation. - **AI** ([Release v3.1.0](https://github.com/Cratis/AI/releases/tag/v3.1.0)): Screenplay AI guidance now teaches scoped model navigation, reviewed typed-AST proposals, safe refactoring, durable identities and explicit recovery. - **cli** ([Release v3.11.0](https://github.com/Cratis/cli/releases/tag/v3.11.0)): Run the Screenplay MCP server with `cratis screenplay mcp`, bundled into the Cratis CLI with no separate Screenplay tool installation or startup download. - **cli** ([Release v3.11.0](https://github.com/Cratis/cli/releases/tag/v3.11.0)): Configure Screenplay MCP automatically when `cratis ai install` or `cratis ai update` selects the Screenplay profile, including profiles that compose it. Supported native configurations cover Claude Code, VS Code/Copilot, Cursor, OpenCode, Codex and Pi. - **cli** ([Release v3.11.0](https://github.com/Cratis/cli/releases/tag/v3.11.0)): Choose a project-local model directory or disable registration in `.cratis/ai.json`; dry-run and status report the planned and installed registrations. - **Components** ([Release v4.13.0](https://github.com/Cratis/Components/releases/tag/v4.13.0)): Let AutoCommandForm callers place optional footer content, including a native submit action, inside the form while retaining its fields-only default. (#314) - **Screenplay** ([Release v4.16.0](https://github.com/Cratis/Screenplay/releases/tag/v4.16.0)): Embed the Screenplay MCP server in .NET 10 hosts through the `Cratis.Screenplay.Mcp` package and `ScreenplayMcpServer.Run`, without installing or launching a separate tool. The existing `screenplay mcp` command remains supported with the same protocol and authoring behavior. (#203) - **AI** ([Release v3.0.0](https://github.com/Cratis/AI/releases/tag/v3.0.0)): `DayKey`, the daily counterpart to `WeekKey` and `MonthKey`. - **AI** ([Release v3.0.0](https://github.com/Cratis/AI/releases/tag/v3.0.0)): `AgentUsageBucketKey`, the day/provider/agent/purpose/model bucket a daily usage row accumulates under. - **AI** ([Release v3.0.0](https://github.com/Cratis/AI/releases/tag/v3.0.0)): `AgentSessionUsageRecorded` now carries a precomputed `DayKey` and `DailyBucketKey`, for the reason its own remarks already give for `WeekKey`/`MonthKey`: Chronicle's model-bound key resolution keys a projection on a single event property, so a composite bucket has nowhere else to come from. - **AI** ([Release v3.0.0](https://github.com/Cratis/AI/releases/tag/v3.0.0)): `UsagePeriod` now carries the resolved `Day` and `DailyBucket` alongside `Week` and `Month`. - **AI** ([Release v3.0.0](https://github.com/Cratis/AI/releases/tag/v3.0.0)): `AgentSessionUsageRecorded` and `UsagePeriod` gained required positional parameters. Code constructing either directly must supply them; `RecordAgentSessionUsage.Provide` resolves them for the normal path. - **AI** ([Release v3.0.0](https://github.com/Cratis/AI/releases/tag/v3.0.0)): `AgentUsageByDay`'s shape and the signature of `AgentUsageByDay.LastYear` changed as described above. - **Screenplay** ([Release v4.15.0](https://github.com/Cratis/Screenplay/releases/tag/v4.15.0)): Author Screenplay models through `screenplay mcp ` with typed AST creation and editing, guarded cross-file renames, and reviewable multi-file proposals. Install the server with the existing `Cratis.Screenplay.Tool` .NET tool package. (#203) - **Screenplay** ([Release v4.15.0](https://github.com/Cratis/Screenplay/releases/tag/v4.15.0)): Navigate large, hierarchical models with scoped declaration searches, dependency views, fixture queries, and revision-safe pagination. (#203) - **Screenplay** ([Release v4.15.0](https://github.com/Cratis/Screenplay/releases/tag/v4.15.0)): Preserve model identities across server restarts and explicitly recover interrupted source writes using root-local identity state and recovery journals. (#203) - **Screenplay** ([Release v4.15.0](https://github.com/Cratis/Screenplay/releases/tag/v4.15.0)): Choose single-file, module, feature, or slice layouts, with whole-model validation before changes are applied. (#203) - **Screenplay** ([Release v4.15.0](https://github.com/Cratis/Screenplay/releases/tag/v4.15.0)): Use typed syntax schemas and source-authoring APIs independently of executable backend readiness, with safe reference validation and verified trivia-preserving renames. (#203) - **AI** ([Release v2.31.0](https://github.com/Cratis/AI/releases/tag/v2.31.0)): Add dedicated skills for release notes and migration guidance, verified technical examples, and LLM-friendly documentation delivery. - **AI** ([Release v2.31.0](https://github.com/Cratis/AI/releases/tag/v2.31.0)): Make the writing skills available through documentation, content, and engineering profiles appropriate to their tasks. - **Arc** ([Release v22.19.0](https://github.com/Cratis/Arc/releases/tag/v22.19.0)): `SortDirectionIsNotRecognized`, the validation failure raised for an unrecognized sort direction (#2715) - **AI** ([Release v2.30.0](https://github.com/Cratis/AI/releases/tag/v2.30.0)): `cratis-social-feed-post` skill covering the feed truncation model, what the opening has to do to survive it, and the formatting and reach constraints that apply to a plain-text feed. - **AI** ([Release v2.30.0](https://github.com/Cratis/AI/releases/tag/v2.30.0)): `cratis-writing-voice-and-cadence` skill covering the sentence constructions and the structural sameness that make written material read as machine-generated, and the claim-preservation checks a voice pass must pass before it is accepted. - **AI** ([Release v2.30.0](https://github.com/Cratis/AI/releases/tag/v2.30.0)): `cratis/content` profile composing both skills. - **AI** ([Release v2.30.0](https://github.com/Cratis/AI/releases/tag/v2.30.0)): Executable verification scenarios for both skills. - **Chronicle** ([Release v19.3.0](https://github.com/Cratis/Chronicle/releases/tag/v19.3.0)): `Cratis:Chronicle:Clustering:ResponseTimeout` sets how long a grain call waits for its response. Some startup work grows with the deployment — the projections for an event store are registered across every namespace it has — while Orleans' 30 second default does not, and a server that grows past that point cannot finish starting. Because it cannot finish starting it cannot start on the next attempt either, so it stays down with no way to give it more room. Defaults to the same 30 seconds Orleans uses. (#4088) - **AI** ([Release v2.29.0](https://github.com/Cratis/AI/releases/tag/v2.29.0)): `Providers.UsageReporting` - `ICanReportAIUsage`, `AnthropicUsageReporting`/`OpenAIUsageReporting` (Anthropic/OpenAI organization usage and cost report readers), the `IAIUsageReporting`/`AIUsageReporting` orchestrator, and a live `AIProviderUsageReport` query for a configured provider's trailing-30-day vendor-reported token usage and cost. - **AI** ([Release v2.29.0](https://github.com/Cratis/AI/releases/tag/v2.29.0)): `Providers.UsageReporting.SettingCredential` - `SetAIProviderUsageCredential`/`ClearAIProviderUsageCredential` for the separate Admin API key a vendor's usage report is read through. - **AI** ([Release v2.29.0](https://github.com/Cratis/AI/releases/tag/v2.29.0)): `ConfiguredAIProvider.UsageApiKey`. - **Arc** ([Release v22.18.0](https://github.com/Cratis/Arc/releases/tag/v22.18.0)): `HttpRequestContextEndpointExtensions` on `Cratis.Arc.Http`: `SetEndpointMetadata`, `GetEndpointMetadata`, and `AllowsAnonymous()` on `IHttpRequestContext`, so an `IAuthenticationHandler` can tell whether the endpoint it is about to authenticate allows anonymous access (#2706) - **Arc** ([Release v22.17.0](https://github.com/Cratis/Arc/releases/tag/v22.17.0)): `IHaveKnownChanges` lets an observable collection query state which of its items changed, so the delta for an emission is the one the provider already knows rather than one rediscovered by comparison. An emitted collection is still an `IEnumerable` of the read model, so existing subscribers are unaffected, and a provider that cannot know what changed continues to be served by the comparison fallback. - **Scene** ([Release v3.6.0](https://github.com/Cratis/Scene/releases/tag/v3.6.0)): Add query input forms that submit exact string or Guid arguments to an optional-single query, with visible validation, loading, result, and not-found states. (#39) - **Scene** ([Release v3.6.0](https://github.com/Cratis/Scene/releases/tag/v3.6.0)): Add identity-aware query registration that detects ambiguous bindings while remaining compatible with existing query views. (#39) - **cli** ([Release v3.10.0](https://github.com/Cratis/cli/releases/tag/v3.10.0)): Add `--warnings-as-errors` so Screenplay validation can reject compiler warnings in CI. (#168) - **Components** ([Release v4.12.0](https://github.com/Cratis/Components/releases/tag/v4.12.0)): `icons` on `CratisComponentsProvider`, replacing Components-owned glyphs product-wide and resolved per site as per-component prop → provider icon → built-in glyph (#299) - **Components** ([Release v4.12.0](https://github.com/Cratis/Components/releases/tag/v4.12.0)): First cut of the icon vocabulary: `close`, `remove`, `expand`, `sortAscending`, `sortDescending`, `previous`, `next` and `clear` (#299) - **Components** ([Release v4.12.0](https://github.com/Cratis/Components/releases/tag/v4.12.0)): `useCratisIcon()` and `CratisIconResolver`, the resolver Components uses at every icon site, exported from the setup-only root barrel for product components that want to follow the same vocabulary (#299) - **Components** ([Release v4.12.0](https://github.com/Cratis/Components/releases/tag/v4.12.0)): `Chip`, `DataTableCore`'s sort indicators, `ComboBox`, `Dropdown`, `TablePaginator`, `DatePickerInput`, `ProgressSpinner`, a toast's dismiss and loading marks, `CommandForm`'s chips field, `ChatSidebar`, the `Chat` panel and PivotViewer's filter/detail panels now resolve their glyphs through that vocabulary instead of hard-coding them (#299) - **Components** ([Release v4.12.0](https://github.com/Cratis/Components/releases/tag/v4.12.0)): `Documentation/Common/cratis-components-provider.md` documents `icons` the way `messages` is documented: the whole vocabulary with what each name draws, its default, and every component that uses it (#299) - **Components** ([Release v4.11.0](https://github.com/Cratis/Components/releases/tag/v4.11.0)): Per-area CSS entry points for every JavaScript subpath — `@cratis/components/Dialogs/styles`, `@cratis/components/PivotViewer/styles`, `@cratis/components/DataTables/styles` and the rest — so an application downloads only the CSS for the surfaces it mounts (#301) - **Components** ([Release v4.11.0](https://github.com/Cratis/Components/releases/tag/v4.11.0)): `@cratis/components/styles/base`, the shared internal utilities and cascade-layer order that every per-area entry point needs, imported once and never duplicated per surface (#301) - **Components** ([Release v4.11.0](https://github.com/Cratis/Components/releases/tag/v4.11.0)): `Documentation/Styling/per-area-stylesheets.md` documentation covering when to prefer them over the aggregate, the full list of entry points and what each one covers (#301) - **Components** ([Release v4.11.0](https://github.com/Cratis/Components/releases/tag/v4.11.0)): Per-area CSS budgets in the published-archive gate: each entry point has its own reviewed gzip ceiling, and a new area cannot ship without a measured number (#301) - **Components** ([Release v4.10.0](https://github.com/Cratis/Components/releases/tag/v4.10.0)): `removeIcon` on `TagGroup` replaces the glyph inside each tag's remove button, defaulting to the multiplication sign it renders today. The button, its accessible name from `removeLabel`, and its keyboard behaviour are unchanged. (#293) ## Changed - **cli** ([Release v3.21.0](https://github.com/Cratis/cli/releases/tag/v3.21.0)): The CLI now bundles Screenplay 4.43.0 and Stage 4.20.0, and `cratis run` defaults to the matching Stage image. Model authors get Screenplay's fixes up to 4.43, including `given … for` and `when append … for` in view slices, which previously failed with PLAY0273 (#193). - **cli** ([Release v3.21.0](https://github.com/Cratis/cli/releases/tag/v3.21.0)): **Chronicle login tokens only go to the server that issued them.** `cratis chronicle login` saves the token, its expiry and the issuing server in the active context. Later commands send the token only when they connect to that exact server. If you log in with `--server`, the token is used when you pass the same `--server` again, and nowhere else. Login refuses multi-host and `chronicle+srv://` connection strings, because the server that receives the token can't be determined in advance. It also no longer follows redirects, and it honours the connection string's TLS options instead of accepting any certificate. - **cli** ([Release v3.21.0](https://github.com/Cratis/cli/releases/tag/v3.21.0)): **All startup hints share one wait.** The CLI, Stage image and Cratis AI hints get at most about 300 ms together after the command finishes, instead of up to 300 ms each. `CRATIS_NO_UPDATE_CHECK` now also skips the Stage image check's local Docker lookup. - **Arc** ([Release v22.31.0](https://github.com/Cratis/Arc/releases/tag/v22.31.0)): Policies without the opt-in behave as before and still require an authenticated caller. Role requirements and authentication-scheme requirements always require an authenticated caller, even when combined with an opted-in policy. If several policies apply, a guest is only evaluated when every one of them opted in. (#2761) - **Arc** ([Release v22.31.0](https://github.com/Cratis/Arc/releases/tag/v22.31.0)): Arc's method-level authorization replaces the type-level declaration. A method with an opted-in policy is therefore reachable by guests even when its type requires a role. The authorization docs now call this out. (#2761) - **Stage** ([Release v4.21.0](https://github.com/Cratis/Stage/releases/tag/v4.21.0)): Bundle the pinned .NET reference assemblies used for audited body binding, expose the Roslyn runtime dependency, and verify a standalone packed consumer in CI. Existing projection and body-less reducer refusal remains unchanged. - **Stage** ([Release v4.21.0](https://github.com/Cratis/Stage/releases/tag/v4.21.0)): Whole-solution Debug specs pass in serial execution (`dotnet test --configuration Debug -m:1`); one optional Mongo-backed test is skipped without a configured connection. Parallel local runs suffered external SIGTERM of testhost from another worktree command; isolated Rendering.Cratis 1,751 pass + 1 skip. - **Stage** ([Release v4.21.0](https://github.com/Cratis/Stage/releases/tag/v4.21.0)): Release build zero warnings, NuGet pack and standalone consumer, frontend test/build and Python compatibility/entrypoint checks pass. Full cross-provider review on the exact committed diff passed with no findings. - **Chronicle** ([Release v19.14.1](https://github.com/Cratis/Chronicle/releases/tag/v19.14.1)): The kernel's observers now use the generic state machine from `Cratis.Orleans.StateMachines` (Cratis.Orleans 1.11.0), and Chronicle's own copy is removed. Runtime behavior and persisted observer state are unchanged. The transition trace log category is now `StateMachine` (#4289) - **Chronicle** ([Release v19.14.1](https://github.com/Cratis/Chronicle/releases/tag/v19.14.1)): Chronicle now builds against Cratis.Orleans 1.11.0, Arc 22.30.0 and Fundamentals 7.19.6 — the minimum versions Cratis.Orleans 1.11.0 requires. The Arc proxy-generator build package stays at 22.23.0 because 22.30.0 crashes on Core - **Arc.TypeScript** ([v0.43.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.43.0)): The development dependency on `@cratis/chronicle` is 6.19.0, and the samples use the same version. The peer range stays `^6.7.0`. - **Arc.TypeScript** ([v0.43.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.43.0)): With an older SDK, a projection-backed lookup fails with an error naming `@cratis/chronicle >= 6.19.0`. When a declarative projection without an explicit read-model type is registered, seeded lookups of read models that have no reducer or explicit projection now fail the same way instead of returning `null`, because Arc cannot tell which read model that projection targets. Give the projection an explicit read-model type (`@projection('', ReadModel)`) or upgrade the SDK. - **Arc.TypeScript** ([v0.42.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.42.0)): The documentation recommends the co-located layout; a separate output folder remains supported, including a dedicated folder nested inside the artifacts folder, which keeps its barrels. - **Arc.TypeScript** ([v0.42.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.42.0)): A bundler that reads slice files outside the web project must lower the proxies' decorators itself, because the web project's `tsconfig.json` does not apply to them. For Vite 8, set `oxc: { decorator: { legacy: true } }`; declare the client packages where the slice folder can resolve them. See [Set up proxy generation](https://github.com/Cratis/Arc.TypeScript/blob/v0.42.0/Documentation/proxy-generation/getting-started.md). - **Chronicle** ([Release v19.13.2](https://github.com/Cratis/Chronicle/releases/tag/v19.13.2)): Document that a webhook's non-2xx response fails delivery: transient failures are first retried by the HTTP client, then the partition follows the observer retry settings and is quarantined when attempts are exhausted. - **Chronicle** ([Release v19.13.2](https://github.com/Cratis/Chronicle/releases/tag/v19.13.2)): Document that an event source can re-claim its own unique value, and that changing the value frees the old one. - **Arc** ([Release v22.30.1](https://github.com/Cratis/Arc/releases/tag/v22.30.1)): Update the Chronicle integration to Cratis.Chronicle 19.13.0, with the Cratis.Fundamentals, Cratis.Metrics and MongoDB driver versions it requires. - **Screenplay** ([Release v4.43.0](https://github.com/Cratis/Screenplay/releases/tag/v4.43.0)): Document that C# code bodies use provider-generated PascalCase member names, while authored Screenplay identifiers remain unchanged. The portable default tenant remains the zero GUID; provider-side tenant translation is still pending. Refs #282. - **Screenplay** ([Release v4.43.0](https://github.com/Cratis/Screenplay/releases/tag/v4.43.0)): Decision records 0012 and 0018 now use the supported `implemented` stage and retain their outstanding provider-verification notes. - **Screenplay** ([Release v4.42.0](https://github.com/Cratis/Screenplay/releases/tag/v4.42.0)): A projection block that repeats `automap` or `no automap` reports `PLAY0452` (warning). The last setting still wins, and canonical printing keeps each line's comments. - **Chronicle.TypeScript** ([Release v6.20.0](https://github.com/Cratis/Chronicle.TypeScript/releases/tag/v6.20.0)): Reject constraints, batch appends (`appendMany` and plural `when.events`), and other unproven operations or inputs with `UnsupportedEventSequenceOperation`, which points to a kernel-backed test. Constraints can be disabled explicitly only for tests that do not depend on them. - **Arc.TypeScript** ([v0.41.0](https://github.com/Cratis/Arc.TypeScript/releases/tag/v0.41.0)): In PostgreSQL mode, `notifyChanged()` validates its target but publishes nothing locally; the database trigger is the only change source. In-process mode is unchanged. - **Components** ([Release v4.16.0](https://github.com/Cratis/Components/releases/tag/v4.16.0)): `Tooltip` `content` accepts any React node, and `0` now shows. `undefined`, `null`, booleans, and an empty string still disable the tooltip. Keep tooltip content non-interactive. Renderer adapters that implement `common.tooltip` receive nodes and must render them as they are; the Conformance profile now checks this. (#230) - **Components** ([Release v4.16.0](https://github.com/Cratis/Components/releases/tag/v4.16.0)): FilterPanel is now a named, non-modal dialog. Opening it moves focus into the panel, and Escape closes it and returns focus to the element that opened it. It now renders as a `div` with `role="dialog"` instead of an `