Skip to content

Release digest: November 9 - 16, 2026 (Week 46)

  • 434 releases: 234 with new features, 195 with fixes, 4 with breaking changes.
  • 630 merged pull requests and 656 issues closed.
  • From merge to release: median < 1 minute (90% within 13 minutes).
  • Busiest repository: DirectPublic (75 releases).
  • Current daily release streak: 104 days.
Repository Previous version Current version
AI v7.148.0 v7.168.4
Ante v1.12.0 v1.14.0
Arc v22.182.1 v23.12.2
Arc.Elixir v1.0.0 v1.1.0
Arc.Go v0.1.2 v0.1.3
Arc.TypeScript v1.0.0 v1.0.1
Architecture v1.0.3 v1.0.4
AuthProxy v2.57.0 v2.65.0
Choreography v2.3.1 v2.9.0
Chronicle v19.150.0 v19.170.0
Chronicle.Elixir v3.21.0 v3.24.1
Chronicle.Go v0.12.0 v0.16.0
Chronicle.Kotlin v7.8.0 v7.11.0
Chronicle.Mcp v2.1.0 v2.3.0
Chronicle.TypeScript v6.61.0 v6.64.0
cli v3.125.0 v3.139.1
Components v4.40.0 v4.42.3
DirectPublic v3.57.1 v3.119.0
Dockerfiles v8.0.9 v8.1.0
Eventmodelers-Build-Kit-CSharp v0.0.2 v0.1.1
Fundamentals v7.33.1 v7.34.1
Grip First release v1.0.0
Montage v0.0.1 v0.1.1
Prologue v3.1.0 v3.2.1
Prompter v0.14.17 v0.14.22
Scene v5.1.0 v6.0.1
Screenplay v6.9.0 v6.35.0
Screenplay.CritterStack v0.26.1 v0.27.2
Screenplay.Generation v0.20.0 v0.21.2
Showrunner v1.20.0 v2.16.1
Specifications v5.2.3 v5.3.0
Stage v5.4.0 v6.2.0
Stage.Axon v0.8.0 v0.11.1
Synopsis v1.1.3 v1.2.4
Templates v1.8.3 v1.9.0
  • Stage (Release v6.2.0): Rendered Cratis screens publish their availability gates and fetch the currently available screens through the configured Arc transport (part of #1128)
  • Stage (Release v6.2.0): Workflow actions and state machine entries can invoke abilities; the invocation is translated into an ability node and settles its ledger when the node reaches its attempt limit (part of #1118)
  • Screenplay (Release v6.35.0): screenplay rename and the MCP propose-rename tool accept a provide declaration as a target: renaming the outermost declaration of a chain rewrites its overrides beneath it and every $context.<name> read that resolves to it, across module and feature fragments in other files. Renaming an override, a built-in $context name, a name already provided in an overlapping scope, or a name with a read that cannot be proven refuses the rename. (#1308)
  • Chronicle (Release v19.170.0): A kernel that keeps its encryption keys in HashiCorp Vault can now host federation and issue mutation receipts. Before, Vault refused the kernel’s own secrets, so creating an enrollment failed and mutation receipts had no key. These secrets are stored at k1/~internal/<event-store>/<purpose>, apart from encryption keys, and the existing Vault policy already covers them.
  • AI (Release v7.168.3): IAIAdministrators and CratisAIBuilder.WithAdministrators<T>() let a host decide which callers may manage AI providers, agents, usage and decisions. See https://github.com/Cratis/AI/blob/main/Documentation/provider-administration.md.
  • Screenplay (Release v6.34.0): A provide whose value comes from a file or an inline code block is admitted into the executable semantic model as an implementation attachment, in ESM v57 (decision 0167) (part of #1307)
  • Screenplay (Release v6.34.0): ESM v57 serializes a code provide with kind code and a requirementId for its ProvideValue implementation; models without one keep their earlier ESM version, and readers below v57 refuse it (part of #1307)
  • Screenplay (Release v6.34.0): Files named by a file provide are collected with the model’s other attachment files (part of #1307)
  • Screenplay (Release v6.34.0): The Invoicing sample and the bundled editor sample show a module provide from a file and one from an inline csharp block (part of #1307)
  • Chronicle (Release v19.169.0): Federation:Hosted:Applications lists the client ids of applications that may manage the hosted federation a kernel is the authority for: creating, listing and revoking enrollments, listing issued certificates, and setting and reading subject policies and links. A listed application gets this one capability, chronicle.federation.manage, and nothing else. Administrators hold it as part of their role.
  • Screenplay (Release v6.33.0): CompilationResult.SpecificationRefusedTypedContextDescriptors publishes wrapper-ready typed context descriptors for every implementation role of the validated model in SpecificationRefusedValue, so hosts that run the healthy remainder of a model with refused specifications get descriptors for rule predicates, reactors and other bodies, not only command handlers. Failed compilations keep their original failure descriptors and diagnostics in TypedContextDescriptors. (#1315)
  • Chronicle (Release v19.168.0): New AdditiveEventTypeSchemaEvolutionEventStores setting lists the event stores where Chronicle accepts an additive change to a registered event type’s schema without a new generation. A change is additive when it only adds optional, nullable or defaulted properties. The list is empty by default, so every event store keeps strict validation; set it on every Chronicle server, in chronicle.json or with Cratis__Chronicle__AdditiveEventTypeSchemaEvolutionEventStores__0=<event store>. (#5946)
  • Chronicle (Release v19.168.0): Chronicle records an EventTypeSchemaEvolved system event when it accepts an additive schema change. (#5946)
  • Chronicle (Release v19.168.0): The event type check result now includes a classification of the schema difference: identical, tolerated, additive or breaking. (#5946)
  • Chronicle (Release v19.167.0): FileSystemCachingTokenProvider has a new constructor that takes a cache scope, such as the server address and client id. A cached token is only reused for the same scope. The existing constructor works as before; give each server and identity its own cache file when you use it. (#5598)
  • Stage (Release v6.1.0): Stage verifies embedded reference packs against SHA-256 manifests before using them. (#1073)
  • Stage (Release v6.0.0): Applications are drawn from the resolved design system: every ui profile that draws from it carries it, in the live Stage, cratis render and the generated application (#1147)
  • Stage (Release v6.0.0): Adopted free screens render as Scene screens owned by their adopting slice, with provisions as bindings, and an unprovided need is refused with a reason naming the screen and the shape (#1150)
  • Stage (Release v6.0.0): ESM v56 models are admitted
  • AI (Release v7.168.2): Deploy and compatibility gates must ask the system of record. A gate that predicts Chronicle event-type registration either calls Chronicle’s read-only registration check or carries a contract spec against Chronicle’s comparison for every change class. The enum rule in the application profile links to it (#1225)
  • AI (Release v7.168.2): Requests for human-only production actions must include necessity evidence: the actual trigger and an independent check against real system behavior that the action is needed. Reviewers ask whether the action is needed, not just whether the procedure is right (#1225)
  • Chronicle (Release v19.166.2): The standalone Workbench can bind to a configured address through ChronicleWorkbenchOptions.Address, for example localhost to listen only on loopback; leaving it empty keeps listening on all interfaces (#5597)
  • AI (Release v7.168.0): Screenplay UI composition guidance for free screens: screens declared anywhere, shape contracts, uses screen with provisions and from mappings, aliases, storyline screens, severities and design-only screens (#1181)
  • AI (Release v7.168.0): Slice design guidance for designing screens before slices exist
  • AI (Release v7.168.0): Design system guidance for component anatomy as the rendering contract, with maps to and variant-to-property links
  • AI (Release v7.168.0): Scene Design guidance for agents: design operations, the design tool loop, refusing free styling, and proposals into the design-system draft
  • Scene (Release v6.0.0): Scene renders a resolved design system: modes, token roles per theme and mode, and component anatomy (parts, variants, states) that components read their look from, with a default design system that keeps today’s look (#316)
  • Scene (Release v6.0.0): The C# engine applies every Scene edit with the same outcomes as the TypeScript engine, held to a shared fixture corpus (#317)
  • Scene (Release v6.0.0): Cratis.Scene.Screenplay, one two-way bridge between Screenplay and Scene, including design systems and free screens with their provisions (#318)
  • Scene (Release v6.0.0): Cratis.Scene.Design and @cratis/scene.design: the design catalogue, design operations with checks and refusals, screen sets with storylines, template mode and template sets, and the design session with its Chronicle events (#319)
  • Scene (Release v6.0.0): Cratis.Scene.Design.AI: the design tool loop on Cratis.AI — screens from prompts and images, edits, variations, tweaks, design-system proposals, and establishing a design system from host sources (#320)
  • Scene (Release v6.0.0): @cratis/scene.editor: the screen, UI profile, template, form, navigation, string and sample data editors, and a design-system editor (#321)
  • Scene (Release v6.0.0): @cratis/scene.design.react: the design canvas with artboards along storylines, chat, variations, tweaks, revisions and element-anchored comments (#322)
  • Stage (Release v5.30.0): Rendering copies the model’s assets folder into the rendered application, so /assets/<path> (for example a layout’s logo) works in the published app as in the sandbox (#1041)
  • Screenplay (Release v6.32.0): A screen can be declared at the top level, in a module or in a feature, as well as in a slice (#1319)
  • Screenplay (Release v6.32.0): shape declares the fields a screen needs; data <Shape>[] without via query states a need, optionally named with as
  • Screenplay (Release v6.32.0): uses screen <Name> lets a slice adopt a screen and provide each need with data <Need> via query <Query> [by …], mapping differing field names with <field> from <path>
  • Screenplay (Release v6.32.0): The compiler checks provisions against the screen’s needs and the read model (PLAY1149–PLAY1164); an unprovided need is a warning that fails a --warnaserror release check, and an unadopted screen is reported as design-only
  • Screenplay (Release v6.32.0): Sample data shapes can name a declared shape, and storylines, navigate to and show reach free screens
  • Screenplay (Release v6.32.0): ESM v56 carries free screens and slice adoptions, and the UI contract carries adopted screens with their adopting slice
  • Screenplay (Release v6.32.0): MCP typed proposals for shapes, free screens, adoptions and provisions
  • AI (Release v7.167.0): cratis-engineering-inherited-work skill in the cratis/engineering/core profile: reconstructs the original goal from the issue, pull request and commits, checks for newer architecture, competing pull requests and work already on main, and recommends continue, rework or obsolete with evidence. Takeover verifies the source head against the handoff, re-checks claimed results, reconciles earlier review findings and preserves contributor credit through merge commits, never rebase, amend or force-push. Closing someone else’s pull request stays behind the existing authorization rules. Adapted from the MIT-licensed tstack modernize and takeover skills. (#1014)
  • AI (Release v7.166.0): The cratis-ux-review skill critiques a rendered screen against its user goal: it gathers browser captures across viewports, themes and states, applies Nielsen’s heuristics plus Cratis passes for hierarchy, consistency with Cratis Components, loading, empty and error states, accessibility risk and copy, and reports severity-rated findings with evidence, the smallest fix using existing components and an observable acceptance outcome (#1015)
  • AI (Release v7.166.0): The React and Components profiles include the skill, and cratis-arc-react-page and cratis-components-accessibility link to it
  • Components (Release v4.42.0): DataPage.MenuItem command receives the current selection as a DataPageSelection<T> snapshot: the selected item in single selection mode, or a readonly selectedItems collection in multiple selection mode. Existing commands without arguments keep working. (#489)
  • Components (Release v4.42.0): DataPage.MenuItem disabled also accepts a predicate over the current selection, combined with disableOnUnselected; a disabled item never runs its command. (#489)
  • Components (Release v4.42.0): DataPageSelection<T> is exported for typing menu actions; declare the menu item as MenuItem<T> to get typed rows. (#489)
  • AI (Release v7.165.5): A conformance fixture checks that a frontend task with no browser operator available reports the UI check as unverified and stops at sign-in instead of driving a browser itself (#977)
  • AI (Release v7.165.5): A verification spec fails when the frontend developer agent, in its canonical form or any adapter, is granted a browser tool (#977)
  • Arc (Release v23.12.1): Chronicle 19.163.0: A certificate authority in the kernel for hosted federation. It issues, renews and revokes peer certificates, and keeps its keys wrapped with an operator-supplied key-encryption key that is read from a file. (cratis/chronicle#5901)
  • Arc (Release v23.12.1): Chronicle 19.163.0: One-time enrollment codes, and RedeemFederationEnrollment so an application’s kernel obtains its certificate and starts its link without a restart. The .NET client exposes it as IChronicleClient.Federation. (cratis/chronicle#5901)
  • Arc (Release v23.12.1): Chronicle 19.163.0: The chronicle.federation.enroll capability, bundled into the administrator role, and a configuration allow-list of application client ids that may redeem a code without being administrators. (cratis/chronicle#5901)
  • Arc (Release v23.12.1): Chronicle 19.163.0: Per-subject federation policy: a peer is admitted by CA chain, issued-certificate registry and policy, and each direction can be suspended, resumed or revoked on its own. (cratis/chronicle#5902)
  • Arc (Release v23.12.1): Chronicle 19.163.0: A dialer-initiated session that carries both directions over one connection through a new Serve call, and a dial-only mode that starts no listener and opens no port. (cratis/chronicle#5903)
  • Arc (Release v23.12.1): Chronicle 19.164.0: IChronicleClient.FederationPolicies to set a subject’s federation policy (target event store and namespace, allowed event types, direction), suspend, resume and revoke a subject or one direction, list policies, and read link status per subject: whether a session is open, last activity, events and bytes per direction, throttling and the last error. (cratis/chronicle#5916)
  • Arc (Release v23.12.1): Chronicle 19.164.0: The enrollment status of a kernel now reports whether its dialer session to the authority is connected, the time of the last successful exchange and the last error, so an application can prove the link works before it considers itself connected. (part of cratis/chronicle#5916)
  • cli (Release v3.138.0): cratis run accepts --stage-setting KEY=VALUE, repeatable, to pass settings to the Stage container. The last value for a key wins, and explicit settings override those the run command supplies itself. Not for secrets. (#567)
  • Arc (Release v23.12.0): A published Native AOT acceptance sample backed by Chronicle, with specs for protected read-model lookups by key and for the calling user (#3634)
  • cli (Release v3.137.0): --level screenplay, code, code-ai and ai run the packaged Cratis builder at the four modes Studio offers: Screenplay only, static code, static code refined by AI and AI only. --target axon renders for Axon Framework instead of Cratis.
  • cli (Release v3.137.0): At code-ai the model is rendered deterministically and an agent then implements the behavior the model describes on top of the generated code. At ai the agent implements the slices from the model without rendering. Every agent prompt ends with Instructions from the model: the slices’ descriptions from the order’s context.hints, the specifications to meet and the feedback people left.
  • cli (Release v3.137.0): --docker runs the builder in a packaged image with the project mounted, and --image chooses the image. A builder in a container reads its connection from CRATIS_STUDIO_URL, CRATIS_STUDIO_ORGANIZATION, CRATIS_BUILDER_ID and CRATIS_BUILDER_TOKEN.
  • cli (Release v3.137.0): --ai studio sends an agent’s model calls through Studio’s AI gateway, on the organization’s providers, over a loopback bridge that speaks the OpenAI and Anthropic APIs. Generators get STUDIO_AI_URL and STUDIO_AI_TOKEN.
  • cli (Release v3.137.0): A Dockerfile and a manual workflow for the packaged builder image.
  • cli (Release v3.137.0): Documentation for running the Cratis and Axon builders locally at every level.
  • Chronicle (Release v19.165.0): Preview on the Workbench Projections page works for projection ... => graph declarations. It shows the nodes and edges the events build and, through a view, the nested rows a graph view query returns.
  • Chronicle (Release v19.165.0): A “New graph” button loads an Organization example (people, groups, MEMBER_OF, PART_OF), and the help panel explains graph declarations.
  • Chronicle (Release v19.165.0): A PreviewGraphProjection command compiles the declaration, runs up to 1000 events of the event store through the real graph changeset builder against an in-memory graph, and evaluates graph views over the result, with compile errors, view errors and per-event failures returned in the result.
  • Chronicle (Release v19.165.0): The kernel evaluates graph views in memory, held to the same shared query vectors as the client and Arc.
  • Chronicle (Release v19.165.0): Documentation for previewing graph projections in the Workbench.
  • Showrunner (Release v2.16.0): Granted users over the Http transport. The collector serves the list of users a desk has granted to an application’s publication through a bearer-authenticated access endpoint with ETag support, and the application caches it and polls on NotesOptions.AccessRefreshInterval.
  • Showrunner (Release v2.16.0): NotesOptions.AccessMaxStaleness. The application refuses everyone when it has never fetched the list, or when the last confirmation is older than this window, and a revocation takes effect at the next poll.
  • Showrunner (Release v2.16.0): NoteCollectingOptions.AccessStores, so a collector can follow the desks that decide who may give feedback.
  • Showrunner (Release v2.16.0): NotesOptions.ApplicationKind (Published or Staged) and a NoteGivenOnStagedApplication public event. A collector sees ReceivedNote.IsStaged, and a collector that does not know the event keeps working.
  • Showrunner (Release v2.16.0): Documentation for granted users over Http, staged sessions and the access endpoint.
  • Showrunner (Release v2.15.0): Object storage abstraction with S3, Azure Blob and volume providers, and a check that key backups never share a bucket with data (part of #18)
  • Showrunner (Release v2.15.0): Discovery of a Production’s Chronicle event stores, namespaces and read-model databases, reporting unclaimed databases (part of #19)
  • Showrunner (Release v2.15.0): Scheduled database backups with manifests, tiered retention and a maximum age, owned by the Understudy (part of #20)
  • Showrunner (Release v2.15.0): CMS-encrypted key backups read from the Vault (part of #21)
  • Showrunner (Release v2.15.0): Cratis.Showrunner.Understudy.Contracts with backup facts, Kubernetes events and Prometheus metrics that carry no tenant or person labels (part of #29)
  • Showrunner (Release v2.15.0): The cratis/showrunner-understudy-image job image and its publishing, and documentation for Understudies
  • Showrunner (Release v2.14.0): Production: vault.mode: Managed runs HashiCorp Vault for Chronicle’s keys, in a development tier (one node, file storage) or a production tier (three nodes on Raft, with a Chronicle token that reaches only its own key paths). Vault is unsealed by a Secret (the default), by a cloud key service (AWS KMS, Azure Key Vault or Google Cloud KMS) or by a transit Vault. Chronicle is configured for Vault compliance storage automatically (part of #17)
  • Showrunner (Release v2.14.0): Production: vault.mode: External takes the address of your Vault and a token Secret (part of #17)
  • Showrunner (Release v2.14.0): Production: federation opens Chronicle’s federation listener on port 35100, makes it the hosted authority, or makes it dial out and serve its public events to an authority, which is the sending side of a one-way link (part of #15)
  • Showrunner (Release v2.14.0): Production: database.backup runs the Percona Backup for MongoDB agent next to every member of a managed database (part of #16)
  • Showrunner (Release v2.14.0): Performance: application.strategy, imagePullSecrets, probes (readiness, liveness and startup), resources, nodeSelector, volumes and volumeMounts, initContainers and egress shape the pod of an application you built
  • Showrunner (Release v2.14.0): Production status reports vault and the VaultModeUnchanged, VaultReady and FederationConfigured conditions
  • AI (Release v7.165.0): Cratis.AI.ReverseProxy NuGet package: a YARP proxy that serves /v1/chat/completions, /v1/messages and /v1/models and routes each request to the endpoint that serves the requested model, with streaming responses passed through as they arrive.
  • AI (Release v7.165.0): A pluggable IModelTransport, with a direct HTTP transport for backends on the same network and a seam for carrying requests to another machine, such as through a tunnel.
  • AI (Release v7.165.0): ModelDiscovery, which detects the protocols and models of an Ollama, LM Studio, vLLM or llama.cpp backend.
  • AI (Release v7.165.0): IModelAccess, which lets nobody in until the host application allows callers explicitly; the caller’s own credential is never forwarded to a backend.
  • Stage (Release v5.29.0): A Stage:Sandbox:Notes:Enabled setting that hosts the Notes backend and the model-references endpoint in sandbox mode. It is off by default, so sandbox behavior does not change unless a host turns it on.
  • Stage (Release v5.29.0): An optional Stage:Sandbox:Notes:ModelReferencesFile so notes from a sandbox session carry the ids of the model elements they are about.
  • Stage (Release v5.29.0): A “Feedback in a play session” reference page describing the settings and how to relay notes with a per-session collector token.
  • Showrunner (Release v2.13.0): FeedbackAccessGranted and FeedbackAccessRevoked public contract events, which a desk such as Direct appends to its outbox to decide who may give feedback in an application.
  • Showrunner (Release v2.13.0): NotesOptions.AccessMode (Everyone or GrantedUsers) and NotesOptions.AccessStores, also bound from configuration. Everyone is the default and keeps today’s behavior.
  • Showrunner (Release v2.13.0): IFeedbackAccess so a host can ask on the server whether the signed-in user may give feedback.
  • Showrunner (Release v2.13.0): Module and feature levels in the feedback dialog for notes about a part of the application.
  • Showrunner (Release v2.13.0): A “Who can give feedback” documentation page and a description of what a note can be about.
  • Arc (Release v23.11.0): Proxy generator --check option compares committed TypeScript clients with what the compiled backend would generate, without writing or deleting files. It lists missing, changed and obsolete files and exits 2 on drift, 0 when up to date and 1 on errors. (#3637)
  • Arc (Release v23.11.0): Proxy generator --validation-report=text|json and --validation-report-file=<path> options explain which inspected server validation rules are projected into generated TypeScript clients and why others stay server-side. (#3638)
  • Arc (Release v23.11.0): QueryOptions.MaxQueuedEmissionsPerSubscription (default 256) caps how many emissions can queue for one observable-query subscription. When a subscriber falls further behind than that over WebSocket, Server-Sent Events or the demultiplexer hub, Arc ends the subscription and the client reconnects with fresh data. (#3633)
  • Arc (Release v23.11.0): Command results now report IsMissingHandler (isMissingHandler in TypeScript) when a command has no registered handler, so clients can tell a missing handler apart from other failures. CommandForm validation treats such a result as not run, with the reason missingHandler, instead of as a failed validation. (#3869)
  • Screenplay (Release v6.31.0): Specifications can assert the exact, ordered tags of an appended event: write tag <name> lines under a then <Event> step, or no tags to assert that the event carries none. Duplicates and order count; omitting both leaves tags unchecked. Models that use tag expectations select ESM version 55, and tag expectations in given, when, redelivery and typed examples are refused with PLAY1148. The TypeScript compiler, Monaco editor, VS Code grammar, MCP server and documentation all support the new form. (#1138)
  • AI (Release v7.164.0): Kubernetes worker jobs can carry a priority class: set Cratis:AI:ContainerRuntime:PriorityClassName to the name of a Kubernetes PriorityClass so the scheduler can rank agent workers against other workloads such as CI runners; when it is not set, worker jobs are unchanged. The cluster owner creates the priority class itself (#1158)
  • AI (Release v7.162.0): Add a shared OpenTelemetry observability rule, scoped to telemetry files (part of #469)
  • Screenplay (Release v6.30.0): The VS Code extension offers the PLAY0469 identifier-payload repair. It is never part of fix-all, and Apply needs explicit consent after a full preview that lists the semantic addresses the repair retires (part of #341)
  • Screenplay (Release v6.30.0): The Screenplay MCP server now advertises PLAY0469, PLAY0516 and PLAY0664 in repair-capabilities, with optional per-repair flags for fix-all eligibility, individual review, event-contract changes and retired semantic addresses (part of #341)
  • AI (Release v7.161.0): A language model completion can take one or more images (IVisionLanguageModel, LanguageModelImage); PNG, JPEG, GIF and WebP are accepted, and usage is metered under the purpose like any other completion (#1148)
  • AI (Release v7.161.0): Anthropic, Z.AI, OpenAI, Azure OpenAI and OpenAI-compatible providers send images with the prompt through the new IAIProviderImageClient (#1148)
  • Arc (Release v23.10.0): CommandForm now reports validation metadata (pending, freshness, verdict and validated version, separately for client and server validation) through the form context, the form handle and onStateChange, so a form can tell a current verdict from one kept for earlier values or a validation that is still pending. A missing command handler is reported as an error verdict for now; see https://github.com/Cratis/Arc/issues/3869 for distinguishing it (#3624)
  • Arc (Release v23.9.0): [ProtocolOnly] for model-bound commands that run through the command pipeline in-process but are not exposed over HTTP (execute or validate routes), the command introspection catalog or generated TypeScript proxies. It is a routing control, not an authorization control: validation, authorization and filters still run. (#3774)
  • AI (Release v7.160.0): The Pi subagent resolves an agent’s modelTier and reviewer independence to concrete models from a user-owned cratis-models.json, and falls back visibly to the session model when only one provider is configured. (#866)
  • AI (Release v7.159.1): The issue design-note skill has an evaluation for an ambiguous canonical comment, so the skill must ask which comment is canonical instead of guessing (#976)
  • AI (Release v7.159.1): The Screenplay UI composition skill explains how to repair action-subject advisories one occurrence at a time (part of #944)
  • AI (Release v7.159.0): New @cratis/pi-direct Pi package for Cratis Direct local sessions: when a Direct runner launches Pi for a work item, it claims the work, keeps the claim alive with heartbeats and releases it with an outcome; in any other Pi session it does nothing. Install with pi install npm:@cratis/pi-direct; setup is in the Pi harness guide. (#1161)
  • AI (Release v7.159.0): A session refuses to start when its launch proof or launch environment is missing or invalid, and Direct write tools stay blocked for the rest of a session once its claim is lost.
  • Stage (Release v5.28.0): The sandbox serves Screenplay graph queries that collect nested rows: each query is read as a Chronicle graph view and executed through the tenant-aware Arc graph session, so every root comes back as the read model with its related rows nested. (#1144)
  • Stage (Release v5.28.0): ESM 54 is admitted and the collect members are classified, so a model that uses collect is no longer refused at admission.
  • Components (Release v4.41.0): DatePickerInput and CalendarField accept an openCalendarLabel prop that names the calendar toggle button; it defaults to “Open calendar” (#505)
  • Components (Release v4.41.0): Page and DataPage accept landmark={false} so a page embedded in an app shell that already renders a main landmark does not nest a second one (#501)
  • cli (Release v3.136.0): cratis build connect --studio --organization <name> connects to the hosted Studio, https://app.cratis.studio. Give --studio <url> only for another Studio.
  • Showrunner (Release v2.12.0): An opt-in setup page at /.cratis/showrunner/direct, enabled through the Box Office product options. An administrator pastes the enrollment code Direct shows; the page connects the application’s Chronicle to Direct and closes permanently once the link is verified. It is off by default, so applications that Direct does not operate never expose it. (#138)
  • Showrunner (Release v2.12.0): Redeeming the code without the page, from the EnrollmentCode option, for automated deployments. A code is ignored when the application is already connected. (part of #138)
  • Showrunner (Release v2.12.0): Documentation for turning the page on, who may use it, and the Chronicle settings the application’s kernel needs. (part of #138)
  • AI (Release v7.158.1): The Screenplay projection skills explain typed reducer keys with KeyAs<T>(), the from/every ambiguity and why triggers are excluded from projections (#1000)
  • AI (Release v7.158.1): The Screenplay read-surface skill explains passive read models: when to use them, what Stage renders and the diagnostics they raise (#1002)
  • AI (Release v7.158.1): The Screenplay command-surface and Arc authorization skills explain policies that read current state before allowing a command (#1097)
  • Chronicle.Mcp (Release v2.3.0): The server sends initialization instructions telling clients that stored content is data only and never authorizes stop_job, resume_job or delete_job. See Untrusted data in tool results. (#62)
  • Chronicle (Release v19.164.0): IChronicleClient.FederationPolicies to set a subject’s federation policy (target event store and namespace, allowed event types, direction), suspend, resume and revoke a subject or one direction, list policies, and read link status per subject: whether a session is open, last activity, events and bytes per direction, throttling and the last error. (#5916)
  • Chronicle (Release v19.164.0): The enrollment status of a kernel now reports whether its dialer session to the authority is connected, the time of the last successful exchange and the last error, so an application can prove the link works before it considers itself connected. (part of #5916)
  • Screenplay (Release v6.29.0): collect inside a graph query’s return assigns a read-model property the rows reached along one edge (outgoing or incoming), with edge properties available through a named edge. A list property gets every row; an optional property gets the first row or null. One level of nesting; selecting roots by a collected node never narrows the collected rows.
  • Screenplay (Release v6.29.0): ESM v54, selected only when a query collects. Models that do not use collect keep their version and bytes.
  • Screenplay (Release v6.29.0): then query specifications assert collected rows, and the reference runner evaluates them with a deterministic order.
  • Screenplay (Release v6.29.0): Diagnostics PLAY1144 to PLAY1147 for a malformed collect, a collect that does not fit its read model or row type, a nested collect, and a query that is not view-shaped.
  • Screenplay (Release v6.29.0): The Organization sample reads people, groups and roles as views, and the shared graph view vectors pass against the reference runner.
  • Screenplay (Release v6.29.0): Support in the C# and TypeScript compilers, the printer, the Monaco editor, the VS Code extension, the MCP server, the documentation and decision 0163.
  • Showrunner (Release v2.11.0): Announcement titles accept inline Markdown such as links and emphasis, so a title can end in “Read more here.”
  • Showrunner (Release v2.11.0): The banner shows the title only; an announcement with a message gets an expand button that reveals the message and a tooltip that shows it on hover and focus
  • Showrunner (Release v2.11.0): Announcements without a message and announcements without a start or end date (permanent until withdrawn) are covered by specs, stories and documentation
  • Chronicle (Release v19.163.0): A certificate authority in the kernel for hosted federation. It issues, renews and revokes peer certificates, and keeps its keys wrapped with an operator-supplied key-encryption key that is read from a file. (#5901)
  • Chronicle (Release v19.163.0): One-time enrollment codes, and RedeemFederationEnrollment so an application’s kernel obtains its certificate and starts its link without a restart. The .NET client exposes it as IChronicleClient.Federation. (#5901)
  • Chronicle (Release v19.163.0): The chronicle.federation.enroll capability, bundled into the administrator role, and a configuration allow-list of application client ids that may redeem a code without being administrators. (#5901)
  • Chronicle (Release v19.163.0): Per-subject federation policy: a peer is admitted by CA chain, issued-certificate registry and policy, and each direction can be suspended, resumed or revoked on its own. (#5902)
  • Chronicle (Release v19.163.0): A dialer-initiated session that carries both directions over one connection through a new Serve call, and a dial-only mode that starts no listener and opens no port. (#5903)
  • AI (Release v7.158.0): Providers can be restricted to a specific list of team members with the SetAIProviderAllowedTeamMembers command, so a shared credential is only used for work started by those members (#998)
  • AI (Release v7.158.0): Provider listings and configured providers expose AllowedTeamMembers and HasAllowedTeamMembersSelection, so an unrestricted provider can be told apart from one that denies everyone (#998)
  • AI (Release v7.158.0): IWorkInitiation carries the team member who started a piece of work; agent runs, conversations, pool dispatch and worker launches check it against a restricted provider’s allowed team members and refuse the work when the member is unknown or not on the list (#998)
  • AI (Release v7.158.0): IProviderSelectionAuthority decides who may change a provider’s allowed team members; the default implementation denies every change until the host replaces it (#998)
  • AI (Release v7.158.0): New documentation page on restricting providers to team members (#998)
  • Arc (Release v23.8.0): Cratis.Arc.Neo4j.Chronicle runs Chronicle graph view queries against Neo4j: register with WithNeo4jGraphViews() or AddCratisNeo4jGraphViews(), inject IGraph and call Nodes<TView>() to get typed, nested records. Tenancy follows the existing graph session, and values are always sent as query parameters.
  • Arc (Release v23.8.0): Cratis.Arc.Neo4j.Chronicle.Testing adds UseGraph() and UseGraphSubstitute() to replace IGraph in specifications.
  • Arc (Release v23.8.0): Documentation and a sample that read the graph through a view.
  • Chronicle (Release v19.162.0): Graph views: [ViewOf<TNode>], [Follows<TEdge>] and [FromEdge] declare a read model anchored at one node that follows declared edges to nested views and exposes node and edge properties. Views are validated and produce the canonical view definition JSON every Chronicle client shares.
  • Chronicle (Release v19.162.0): IGraph.Nodes<TView>() queries a view with member-selector clauses and hydrates typed records. Host packages execute reads by implementing IGraphQueryExecutor.
  • Chronicle (Release v19.162.0): GraphScenario queries views against its in-memory graph, with SeedNode and SeedEdge to seed it.
  • Chronicle (Release v19.162.0): Analyzers CHR0078 to CHR0081 report a view anchored at a non-node, Follows on a non-edge, a relation target that is not a view, and a view that is also a node or edge.
  • Chronicle (Release v19.162.0): Documentation for reading a graph with views.
  • Chronicle.Kotlin (Release v7.11.0): @ViewOf, @Follows and @FromEdge declare a graph view: a read model anchored at one node that follows declared edges to nested views and exposes node and edge properties. They work from Kotlin data classes and from Java records.
  • Chronicle.Kotlin (Release v7.11.0): GraphViews.definitionsFor builds the canonical view definitions, and GraphViewDefinition.toJson writes the JSON every Chronicle client shares.
  • Chronicle.Kotlin (Release v7.11.0): An invalid view fails with an InvalidGraphView carrying a named reason, such as EdgeNotIncidentOnRoot or RecursiveView. Every graph still registers before the failure is thrown.
  • Chronicle.Kotlin (Release v7.11.0): Documentation for declaring graph views.
  • Chronicle (Release v19.161.0): The MongoDB storage provider probes the connected server’s capabilities at startup, and the hosting documentation describes Azure DocumentDB compatibility and its measured gaps (#5642)
  • Chronicle.Go (Release v0.16.0): graphs.NewView declares a graph view: a read model anchored at one node that follows declared edges to nested views and exposes node and edge properties.
  • Chronicle.Go (Release v0.16.0): (*Graph).WithViews attaches views to a graph. Declaration.ViewDefinition and Definition.Views expose the canonical view definition, as Canonical or CanonicalWithSchema, the JSON every Chronicle client shares.
  • Chronicle.Go (Release v0.16.0): An invalid view fails Build() with a typed reason that works with errors.Is, such as graphs.EdgeNotIncidentOnRoot or graphs.RecursiveView.
  • Chronicle.Go (Release v0.16.0): Documentation for declaring graph views.
  • Chronicle.TypeScript (Release v6.64.0): @viewOf, @viewKey, @viewProperty, @follows and @fromEdge declare a graph view: a read model anchored at one node that follows declared edges to nested views and exposes node and edge properties.
  • Chronicle.TypeScript (Release v6.64.0): GraphViewDefinitionBuilder and GraphViewDefinitionSerializer build and serialize the canonical view definition, the JSON every Chronicle client shares. Graphs.viewDefinitions exposes the definitions of the discovered views.
  • Chronicle.TypeScript (Release v6.64.0): An invalid view is reported through the graph failures with a named reason, such as EdgeNotIncidentOnRoot or RecursiveView, and does not stop other graphs from registering.
  • Chronicle.TypeScript (Release v6.64.0): Documentation for declaring graph views.
  • Chronicle.Elixir (Release v3.24.0): Chronicle.Graphs.View declares a graph view: a read model anchored at one node that follows declared edges to nested views and exposes node and edge properties.
  • Chronicle.Elixir (Release v3.24.0): Chronicle.Graphs.ViewDefinition builds the canonical graph view definition and encodes it as the JSON every Chronicle client shares.
  • Chronicle.Elixir (Release v3.24.0): The view macro registers views inside a graph module. A view that cannot work fails compilation with a named reason, such as EdgeNotIncidentOnRoot or RecursiveView.
  • Chronicle.Elixir (Release v3.24.0): Documentation for declaring graph views.
  • Chronicle (Release v19.160.0): Event store subscriptions can be restricted to listed source namespaces; observers of unlisted namespaces are revoked and the subscriber drops their events (#5874)
  • Chronicle (Release v19.160.0): Azure Key Vault encryption keys migrate from earlier secret names to hashed names with an operator-listed scope check, verified copies and guarded removal (#5747)
  • AuthProxy (Release v2.65.0): Bearer routes produce signed v2 forwarded-identity envelopes for verified OAuth grants. The envelope carries the credential kind, credential id and cache epoch from active token introspection, and binds to the forwarded access token through a SHA-256 hash (#344) (part of #294)
  • AuthProxy (Release v2.65.0): The forwarded-identity readiness report marks bearer OAuth-grant flows as ready (#344)
  • Screenplay (Release v6.28.0): The compiler warns when a projection or reducer copies a secret concept into a read model, where it would be included in query results. (#1213)
  • Screenplay (Release v6.28.0): The opt-in personas completeness check reports a screen whose bound commands and queries are all definitely denied to every declared persona’s synthesized caller (PLAY1143), so a screen nobody can use is no longer silent. Unknown or undecidable gates and screens without bindings are never reported. Available in the C# and TypeScript compilers and as --completeness PLAY1143.
  • Screenplay (Release v6.28.0): Hosts can opt into an executable model that excludes broken specifications while preserving their errors and stable identities. (#1310)
  • cli (Release v3.135.0): cratis run --detach waits until the Stage is ready, prints its addresses and container name, and exits with the sandbox left running; if startup fails or is cancelled, the container is removed again (#566)
  • cli (Release v3.135.0): cratis run --timeout <seconds> sets how long the command waits for the Stage to become ready before stopping it; detached runs default to 300 seconds, foreground runs wait until you stop them (#566)
  • cli (Release v3.135.0): cratis stop stops a sandbox started by cratis run, by name or with --all, and reports Not found when the named sandbox is not running (#566)
  • Showrunner (Release v2.10.0): Cratis.Showrunner.Cue: AddCue with CueOptions.Tours (the tour names the application accepts), the StartTour command that records the first start of a tour once per person, the StartedTour.ByMe query, IViewerTours for reading the history on the server, and ISignedInViewer to replace how a person is told apart (the sub claim by default). The history is kept under a hashed event source with the person as compliance subject, so an erasure request finds it.
  • Showrunner (Release v2.10.0): @cratis/showrunner.cue: the generated proxies for that command and query.
  • Showrunner (Release v2.10.0): @cratis/showrunner.cue.react: the tour player. TourOverlayShell plays a script of sections, chapters and steps against one clock, with chapter list, subtitles, transport, pointer, callouts and an optional written chapter for each step; useCueTours and useTourNudge connect a tour button to the backend so it points at a tour until the person has taken it.
  • Showrunner (Release v2.10.0): A configurable voice-over. CueProvider takes a speech configuration: createHttpSpeech connects any text-to-speech service reached over HTTP (the address, availability address, request body, headers and cache size are the application’s), and an application with its own pipeline provides a CueSpeech of its own. Without one the tours play silently with subtitles.
  • Showrunner (Release v2.10.0): Every text of the tour’s chrome is a label the application can replace, and the application can guard a tour’s stage with its own error boundary. The styles use the --cratis-* tokens, with --cue-viewport-top and --cue-z-index to fit an application shell.
  • Showrunner (Release v2.10.0): Documentation for Cue: how it works, adding it to an application, writing a tour, configuring the voice-over, remembering who has taken a tour, and the event reference.
  • Chronicle (Release v19.159.0): The Workbench has a Constraints page where authorized operators can start a constraint reindex, behind a confirmation that governed appends may wait, with a link to the job. (#5888)
  • Arc (Release v23.7.0): Availability now passes the calling system’s client id to the audience source. For a system caller, AudienceSubject.SystemClientId is read from the client_id claim, or azp when client_id is absent, so an IAudienceSource can return the system-wide grants plus that client’s own. Callers without a client id pass none, and person callers are unchanged. (#3851)
  • Showrunner (Release v2.9.0): GuestList availability answers a system caller from the client id on its audience subject: it gets the grants every system holds plus the grants for that client id, and a caller with no client id or an unknown one gets only the product-wide ones. Person and tenant behavior is unchanged. Requires Cratis.Choreography 2.9.0.
  • Choreography (Release v2.9.0): AudienceSubject.SystemClientId carries the calling system’s client id so an IAudienceSource can return the system-wide grants plus that system’s own. It is empty when the caller names none, and existing callers and constructors are unchanged. (#226)
  • Showrunner (Release v2.8.0): AudienceLevel.NamedSystem and the SystemClientId and SystemKind (None, Mcp, Api, Other) types, so a decision can name one system without changing what the System level means (#135)
  • Showrunner (Release v2.8.0): GrantAudience and WithdrawAudience take an optional ClientId and Kind; a named-system decision must name both and no tenant or user, and a withdrawal removes that system’s grant only
  • Showrunner (Release v2.8.0): SystemsDeclared and SystemDeclaration: a product reports the systems that call it, through IKnownSystems, and the operator reads them as the ProductSystems query, so an operator can list systems with their client id and kind
  • Showrunner (Release v2.8.0): IGuestList.ForNamedSystem and ForSystemCaller, and GuestListAudienceSource.GetGrants(subject, clientId): a request made by a named system gets the audiences of every system plus its own, never another system’s and never a person’s
  • Arc (Release v23.6.0): Tenancy.RequireDuplicateHeaderPreservation refuses startup when header-based tenancy runs on a host that cannot preserve duplicate headers. (#3791)
  • Arc (Release v23.6.0): Untyped CommandScenario<object> can turn on decision reads with the new EnableDecisionReads() instead of the obsolete UseDecisionReads() (#3669)
  • Arc (Release v23.6.0): Read-protection configuration is accepted under Cratis:Arc:ReadProtection, with root-level keys still working. (part of #3778)
  • Arc (Release v23.6.0): Configuration key reference and minimal setup guides for Arc alone and Arc with Chronicle. (part of #3778)
  • AI (Release v7.157.0): Worker runs receive an explicit repository-to-mirror mapping in CRATIS_WORKER_REPOSITORY_MIRRORS, and the cache contract names each repository’s clone URL and mirror path (WorkerCacheRepository, WorkerCacheAccess) (#1152)
  • Chronicle (Release v19.158.0): An administrator query that lists stored event type schemas carrying annotations (deprecated, contentEncoding, examples, $comment), and the NormalizeEventTypeSchemas administrator command that removes those annotations from the stored schemas. (#5878)
  • Chronicle (Release v19.157.0): CheckEventTypeRegistrations kernel command: checks a set of event types against what the kernel has registered, without registering anything, and reports a verdict per event type with the first differing schema keyword and path. (part of #5877)
  • Chronicle (Release v19.157.0): ReindexConstraints operator command (administrators only) to rebuild the constraint indexes of an event store and namespace on demand. (part of #5880)
  • Stage (Release v5.27.0): The generated availability registration builds an AvailabilityManifest and registers IAvailabilityManifest as a singleton: the declared audiences, every availability block, a gate entry for each module, feature, slice, command and read model with the slices at or beneath it, and the provided context values with their scope. Every list is sorted, so the same model always renders the same bytes. A model without availability emits no manifest.
  • Showrunner (Release v2.7.0): AvailabilityDeclared and AudienceDecisionReceived public events in Cratis.Showrunner.GuestList.Contracts, generation 1 and additive, with EnvironmentName, ModelVersion, AudienceDecision and the declaration types they carry.
  • Showrunner (Release v2.7.0): AvailabilityReporter in Cratis.Showrunner.GuestList.Availability: reports the Choreography availability manifest once per change, survives restarts, retries in the background and never holds the host back. GuestListOptions gains Environment, Version, OperatorAudience and RetryInterval.
  • Showrunner (Release v2.7.0): A receipt for every decision a product records: AudienceDecisionReceived is published once per recorded decision, not on re-delivery and not for a decision the product ignored.
  • Showrunner (Release v2.7.0): ProductAvailability (what a product declares per environment and what each report changed) and AudienceDelivery (the newest decision each environment received) read models in Cratis.Showrunner.GuestList.Authoring.
  • Showrunner (Release v2.7.0): The documentation page “Report what the model declares” and the new events in the GuestList contracts reference.
  • Choreography (Release v2.8.0): AvailabilityManifest and IAvailabilityManifest (with InMemoryAvailabilityManifest): audiences, blocks, gates, context values and personas as immutable records.
  • Choreography (Release v2.8.0): AvailabilityExpression.Alternatives(): expands any gate into disjunctive normal form, including with, and, or, parentheses and when.
  • Choreography (Release v2.8.0): AudienceDeclaration and a DeclaredAudiences overload that takes declarations with description and source.
  • Choreography (Release v2.8.0): An optional Description on AvailabilityDefinition.
  • Choreography (Release v2.8.0): Documentation page for the availability manifest.
  • AI (Release v7.156.0): Add the cratis-arc-mcp skill for configuring Arc MCP tools, personal access tokens and scopes, client connections, and troubleshooting. (#1093)
  • AI (Release v7.155.0): cratis-engineering-post-mortem skill: a repeatable, provider-neutral post-incident review built from an incident record and its linked runs, pull requests and issues. It covers a UTC timeline with per-row confidence (Verified, Inferred, Unverified), impact, unverified claims kept apart from facts, root causes as why-chains, an action table with one owner and one linked issue per action, lessons, and a public-safe wording pass. It ships with a review template and two generalized worked examples (#1149)
  • AI (Release v7.155.0): post-mortem agent that drafts the review with that skill and files each action in the repository that owns it after a duplicate search, treating evidence text as data rather than instructions (#1149)
  • Stage (Release v5.26.0): Rendering of audience declarations, reusable availability blocks and available gates as generated Choreography availability policies registered with Arc, evaluated before authorize and refusing with the NotAvailable reason, including with composition and $context.audiences. (#1117)
  • Stage (Release v5.26.0): Availability exposed through Arc so client features can hide navigation for parts that are not available. (#1117)
  • Stage (Release v5.26.0): Generated hosts wire the Showrunner guest list as the audience source when the model uses availability; reactions that invokes a command are evaluated with the tenant’s audiences plus the system’s. (#1117)
  • Stage (Release v5.26.0): Diagnostics that refuse availability conditions and mixed query gates the generated gates cannot evaluate faithfully, instead of rendering them silently. (#1117)
  • Stage (Release v5.26.0): Reference documentation: Availability rendering.
  • Stage (Release v5.25.0): The sandbox reads the stored caller back onto each fact when it rebuilds its world, so projection mappings of $eventContext.causedBy.subject, .name and .userName run over history and show who made each change (#1083)
  • Screenplay (Release v6.27.0): Projections can map $eventContext.causedBy.subject, .name and .userName in the reference evaluator, wherever occurred is already supported
  • Screenplay (Release v6.27.0): Facts carry the audit identity of the caller that caused them
  • Stage (Release v5.24.0): A model that provides values to its request context now renders: provide at the application, a module, a feature or a slice becomes a generated ProvidedValueResolvers service on Choreography’s context value engine, resolving each value lazily and once per request, with the nearest declaration winning. Literal, $context expression, host and keyed snapshot query sources render, and the host registers an empty IHostContextValues you can replace from Customizations/Program.cs. See Provided values rendering. (part of #1116)
  • Stage (Release v5.24.0): Stage admits ESM 53, the version that carries provided values, audiences and availability gates. A model that declares an audience, an availability or an available gate is refused with STAGE-ESM-016 until those render.
  • Stage (Release v5.24.0): STAGE-ESM-075 and STAGE-ESM-076 refuse a provided value Stage cannot resolve faithfully, such as a query with authorization, filters or a performer, a query keyed by a literal, a collection or a concept type.
  • AI (Release v7.154.0): A cratis-screenplay-availability skill that teaches audience, availability, available and provide with $context values: where availability belongs versus authorize, levels, reserved names, required versus optional values, absence versus failure, specifications always running with everything available, unknown never opening a gate, the cross-slice warning, authoring-only persona audiences, audiences versus Box Office modules, Chronicle routing audiences and token aud, runtime ownership, and review checks for gates no persona can satisfy, unreferenced audiences, unresolvable provide keys and rules reading identity-derived values (#1144)
  • Arc (Release v23.5.0): Screenplay generation states [AvailableFor] and [AvailableWith] gates on commands and read models as audience, availability and available for / available with lines. (#3834)
  • Arc (Release v23.5.0): Screenplay generation states values resolved from a read model query, declared in a ContextValueCatalog, as provide ... from query ... by $context... lines at the application, module, feature or slice the scope names. (#3834)
  • Arc (Release v23.5.0): Diagnostic SP0080 reports a gate or value that cannot be stated faithfully: a gate registered with Gate or GateNamespace, a value the host, an expression or code provides, an audience name that is not an identifier, and a scope that names nothing of the model.
  • Arc (Release v23.5.0): Diagnostic SP0081 reports an availability declared without rules, because its definition lives in the host’s AvailabilityCatalog.
  • Screenplay (Release v6.26.0): audience and reusable availability declarations with for, when and with lines, combined with and, or and parentheses, and available for, available when and available with gates on modules, features, slices, commands, queries and screens. Gates combine down the path and are decided before authorize; an unknown audience, availability or value never opens a gate (#1301)
  • Screenplay (Release v6.26.0): Persona audience lines, for authoring only, and the $context.audiences value.
  • Screenplay (Release v6.26.0): provide <name> <Type> from <source> for scope-driven context values readable in available when.
  • Screenplay (Release v6.26.0): ESM v53, written only when a model uses availability or provided values.
  • Screenplay (Release v6.26.0): Diagnostics PLAY1130 to PLAY1141 for malformed, duplicate, unknown and circular audiences and availabilities, unprovided values, and commands that can be unavailable to their invoker.
  • Screenplay (Release v6.26.0): The same support in the TypeScript compiler, Monaco (hover, completion, go to definition, snippets), the VS Code grammar, rename and the MCP server. The event model board draws a gated slice for the personas that pass its gates and marks it.
  • Screenplay (Release v6.26.0): A documentation page on audiences and availability, and gates in the Invoicing and Commerce samples.
  • Arc (Release v23.4.0): QueryContext.Values, AuthorizationPolicyContext.Values and context.Values() on the FluentValidation context read provided values by name, such as context.Values.Vessel. ProvidedValues gives the asynchronous and typed reads, and ValuesAs<T>() reads them as a typed payload. A command reads them through CommandContext.ProvidedValues and ValuesAs<T>(), because CommandContext.Values already holds the values of the command pipeline. (#3833)
  • Arc (Release v23.4.0): IContextValueSource, registered by AddArcAvailability on the Choreography engine and on the request’s availability context, so gates, handlers, performers, policies and rules in one request share one value and a second request resolves again. (#3833)
  • Arc (Release v23.4.0): An absent value reads as unknown (null), a required value that is absent throws RequiredContextValueAbsentException, and a failure to resolve throws ContextValueUnavailableException, which command and query results report as a retryable error, never a denial. (#3833)
  • Arc (Release v23.4.0): Documentation: https://github.com/Cratis/Arc/blob/main/Documentation/backend/csharp/context-values.md (#3833)
  • Showrunner (Release v2.6.0): Cratis.Showrunner.BoxOffice.Product.Availability: AddBoxOfficeEntitlementsAvailability() supplies the host-provided context value entitlements (provide entitlements Entitlements from host), readable in available when conditions as the tenant’s active state, readOnlyReason, seats and each module’s level (None, Preview, Trial, Full) and usable (#127)
  • Showrunner (Release v2.6.0): Documentation on using entitlements in availability conditions and how Box Office modules relate to GuestList audiences
  • Screenplay (Release v6.25.0): provide <name> <Type> [optional] from query <Query> [by <expression>, ...], from host, from <literal or $context expression>, or a file reference or inline code block beneath it, at the application, module, feature and slice levels. The nearest declaration wins and an override keeps the type (#1300)
  • Screenplay (Release v6.25.0): Diagnostics PLAY1119 to PLAY1129 for malformed, duplicate, reserved-name, mistyped, unknown-query, observable-query and cyclic provides
  • Screenplay (Release v6.25.0): A Values property and ValuesAs<T>() on CommandContext, QueryContext, RuleContext, PolicyContext and the new ProvideContext, so code reads provided values by name
  • Screenplay (Release v6.25.0): provide support in both compilers, the printer, Monaco (completion, hover, validation), the VS Code grammar and the MCP authoring index, with documentation and a multi-file fixture
  • Arc (Release v23.3.0): Cratis.Arc.Availability package: AddArcAvailability(...), [AvailableFor] and [AvailableWith] attributes, and options.Gate<TPart>(...) / options.GateNamespace(...) gates built on Choreography AvailabilityExpression. Gates apply down the path (namespace, part, attributes) and the audiences and context values of a request are resolved once. (#3831)
  • Arc (Release v23.3.0): Commands and queries of a part that is not available are refused before authorize with the NotAvailable reason (AvailabilityReason.NotAvailable) and HTTP 403. Unknown denies. (#3831)
  • Arc (Release v23.3.0): CommandResult and QueryResult carry AuthorizationFailureReason and IsRetryable; a failure to decide whether a part is available is a retryable error (HTTP 503), never a denial. (#3831)
  • Arc (Release v23.3.0): The /.cratis/availability observable query reports what is not available to the current context, with the slice of each part, and re-emits when audiences change. (#3832)
  • Arc (Release v23.3.0): @cratis/arc/availability and @cratis/arc.react/availability: AvailabilityProvider, RequireAvailable, useAvailableItems and useAvailability hide unavailable parts, navigation items and screens and show them again live; command results expose isNotAvailable, onNotAvailable and isRetryable, and isNotAvailable(result) reads query results. (#3832)
  • Arc (Release v23.3.0): MCP tools whose command or query is not available are omitted from the tool listing; a call is refused with the NotAvailable reason, and the tool outcome now includes reason and isRetryable. (#3832)
  • Arc (Release v23.3.0): Documentation for availability and React availability. (#3832)
  • AI (Release v7.153.10): Spec guidance on choosing the cheapest real proof: hosts, kernels, containers and browsers only prove contracts the repository owns, consumer routing/e2e and service-boundary regression tests stay in the pull-request lane, and retiring a consumer assertion needs a named upstream spec. Run cratis ai update to get it. (#1139)
  • Showrunner (Release v2.5.0): Cratis.Showrunner.GuestList.Availability: AddGuestListAvailability registers a Choreography IAudienceSource over GuestList’s local read models. The effective audiences are the union of the system’s, the tenant’s and the user’s grants, each tagged with its level. Nothing is asked of the operator, so the last known state stays in force while the link is down. Grants for audiences the application does not declare are carried, never match a gate and are reported (a warning once per grant; the UndeclaredGrant query lists them). Cratis/Choreography#221
  • Showrunner (Release v2.5.0): Open sessions update: IAudienceSource.OnChanged is raised when a grant or withdrawal changes the product’s read models, including for tenants added later.
  • Showrunner (Release v2.5.0): The cratis.showrunner.guestlist.audience_lag metric reports the seconds since the product last received a change to its audiences.
  • Showrunner (Release v2.5.0): Documentation: Feed the availability engine.
  • Showrunner (Release v2.4.0): Cratis.Showrunner.GuestList.Authoring, the operator side of audiences, which works without Direct: the GrantAudience and WithdrawAudience commands for a tenant, a user or the system, the ProductGuestList and UndeclaredAudienceGrant queries, and an outbox reactor that publishes AudienceGranted and AudienceWithdrawn once, in the order they were decided (#126)
  • Showrunner (Release v2.4.0): Commands refuse a missing product, an invalid audience name, a tenant or user a level does not need or does not name, and an unknown tenant (through the optional IKnownTenants); granting a held audience or withdrawing one that is not held records nothing
  • Showrunner (Release v2.4.0): AddGuestListAuthoring with AddressToProducts and DeclaredAudiences options, and GuestListAuthoring.Policy for the host’s authorization
  • Showrunner (Release v2.4.0): Integration specifications that run an operator store and a product store against a real Chronicle kernel
  • Showrunner (Release v2.4.0): A guide to granting audiences as an operator, and GuestList in the audience routing table
  • Showrunner (Release v2.3.0): Cratis.Showrunner.GuestList, the product side of audiences: it receives AudienceGranted and AudienceWithdrawn through the inbox and records them in the tenant’s own namespace (user grants in the tenant’s namespace, system grants in the product’s), so the newest decision wins, a duplicate is recorded once and a withdrawal removes only its own level’s grant (#125)
  • Showrunner (Release v2.3.0): IGuestList and the GrantedAudience and UndeclaredGrant queries for a tenant’s, a user’s and the system’s audiences and for grants that match no declared audience; they answer from what the product recorded, so the last known state stays when the operator is unreachable
  • Showrunner (Release v2.3.0): AddGuestList with Product, OperatorStores, SubscribeForProduct, DeclaredAudiences and PollingInterval options
  • Showrunner (Release v2.3.0): A guide to receiving audiences in a product
  • Stage (Release v5.23.0): A signal a screen handles with on <signal> is bound to Scene’s signal trigger when the name is a signal the component’s contract declares; a name the contract does not declare stays an application trigger. When the component raises the signal, the runtime runs the behaviors attached to that component through the Scene interaction engine, and signal.<value> arguments read the values the component raised. See Handling a raised signal. (part of Cratis/Screenplay#1248)
  • Showrunner (Release v2.2.0): Cratis.Showrunner.GuestList.Contracts: the public events AudienceGranted and AudienceWithdrawn, which grant and withdraw an audience at Tenant, User or System level, with Product, Level, TenantId, UserId and Audience fields (#124)
  • Showrunner (Release v2.2.0): GuestList documentation: overview, how it works and a contract page with the event table
  • Choreography (Release v2.7.0): Availability engine that evaluates for, when and with gates combined with and, or and parentheses in authored order, with three outcomes (available, unavailable, unknown), where unknown and absence deny and a failure is an exception, never a denial (#220)
  • Choreography (Release v2.7.0): Audience abstraction (IAudienceSource) with effective audiences as the union of tenant, user and system grants, grants for undeclared audiences carried and reported but never matching, and a change subscription for reactive invalidation, plus in-memory implementations (#220)
  • Choreography (Release v2.7.0): Request-scoped context values declared at application, module, feature and slice level, resolved lazily once per request with nearest-level override, cycle detection, required and optional values, and providers for read models, literals, expressions, the host and code (#222)
  • Choreography (Release v2.7.0): Environment switch that grants every declared audience, off by default and refused outside local and test environments (#223)
  • Choreography (Release v2.7.0): Documentation for the availability engine
  • Stage (Release v5.22.0): The ability catalog, the component placements, the setting declarations and the per-screen backend usage are built from the compiled model and the loaded packages’ contracts. A system no loaded package realizes has no abilities, and a component the contract does not declare is not placed. See https://github.com/Cratis/Stage/blob/main/Documentation/extensions/end-to-end.md (part of Cratis/Screenplay#1248)
  • Stage (Release v5.22.0): A screen that places component <System>.<Component> renders as a Stage:extensionComponent element carrying the locked package’s frontend address, the abilities the contract lets the component invoke, the signals it raises and its placeholder.
  • Stage (Release v5.22.0): The page tells the host which screen was reached (POST /stage/extensions/activation/screens/<screen>), so the backends of that screen’s systems start before the component’s first invocation.
  • Stage (Release v5.22.0): Samples/Extensions/Notifier, a minimal extension with a contract, a React component, a placeholder and a C# backend, and specifications that run it from a lock through a real Orleans silo.
  • Scene (Release v5.4.0): SignalInteractionTrigger (signalName) in @cratis/scene.model and Cratis.Scene.Model.Interactions, a new interaction trigger kind next to the built-in, event, interval and application-trigger kinds. Existing triggers and documents are unchanged.
  • Scene (Release v5.4.0): resolveSignalBehaviors(attachments, signalName) in @cratis/scene.engine, which collects the bindings for a raised signal in the same deterministic order as the other triggers and never matches an application trigger of the same name.
  • Scene (Release v5.4.0): Documentation of the signal trigger in the extension contract guide and the glossary.
  • AuthProxy (Release v2.64.0): Opt-in ForwardSessionContext service setting that adds the browser session start time (urn:cratis:session:started) and sign-in provider (urn:cratis:session:sign-in-provider) claims to the forwarded principal (#327)
  • AuthProxy (Release v2.63.0): RequireVerifiedEmail on OIDC providers: the callback is refused unless the signed-in person has exactly one e-mail address marked verified, and the person is answered like a failed sign-in without a session. email_verified is mapped from the user info endpoint when the ID token does not carry it. (#329)
  • AuthProxy (Release v2.63.0): DenialResponse: "FailedSignIn" on OIDC providers: when identity details deny a session from that provider, AuthProxy ends the session and answers like a failed sign-in instead of showing the 403 page. (#329)
  • AuthProxy (Release v2.63.0): AuthorizationParameters on OIDC providers, for parity with OAuth providers; parameters the authentication handler owns are rejected at startup. (#329)
  • AuthProxy (Release v2.63.0): Documentation for gating an e-mail-code provider at sign-in. (#329)
  • Showrunner (Release v2.1.0): Payments: Cratis.Showrunner.Payments is a provider-neutral contract for taking payments. IPaymentProvider covers customers, first and one-off payments, charges against a customer’s permission, subscriptions and refunds, and IPaymentWebhookHandler is what an application registers to hear that a payment changed.
  • Showrunner (Release v2.1.0): Cratis.Showrunner.Payments.Mollie implements the contract against Mollie. AddMolliePayments registers it and MapMolliePaymentWebhook maps the webhook, which reads the payment back from Mollie before the application hears of it, so a forged callback cannot change what a payment says.
  • Showrunner (Release v2.1.0): Documentation for Payments, with the options and the webhook’s answers.
  • AI (Release v7.153.8): Opt-in security hardening for Docker workers, and per-job resource limits applied to the worker container. (part of #1047)
  • AuthProxy (Release v2.62.0): Each OidcProviders[] and OAuthProviders[] entry can set its own browser-session lifetime with an optional Session block (Lifetime, SlidingExpiration). A provider value can only shorten the global Session:Lifetime or turn sliding expiration off; a non-positive value or one longer than the global lifetime stops startup with a message explaining the fix. Providers without the block keep the global settings, sessions that already exist keep their current lifetime, and personal access tokens and other non-browser credentials are not affected. Stored user tokens follow the same lifetime, so they never outlive the session (#326)
  • Stage (Release v5.21.0): React and mount extension components, with user, tenant, locale, theme, public settings, strings, invoke, raise and on, and the useUser, useTenant, useLocale, useTheme, useSettings, useStrings, useInvoke, useRaise and useTrigger hooks. Language and theme changes update the context. (#1070)
  • Stage (Release v5.21.0): A placeholder, marked busy, while a component loads, and a readable message when the module does not export it or exports it as the other kind. A package’s placeholder is shown in a frame that cannot run script.
  • Stage (Release v5.21.0): invoke goes through the host with one interaction identity across waits and refuses an ability outside the contract in the browser as well as on the host. Secrets never reach the browser: the page asks only for the identity, the public settings and invocations.
  • Stage (Release v5.21.0): @cratis/scene.extensions is a shared module on the page’s import map, so an extension’s hooks read the context Stage provides.
  • Stage (Release v5.21.0): Documentation of the browser side in Run extension components.
  • Arc.Elixir (Release v1.1.0): A :arc_analyzer compiler. Turn it on with compilers: [:arc_analyzer] ++ Mix.compilers() in mix.exs, or run mix igniter.install cratis_arc. The installer is safe to run twice and updates every app of an umbrella.
  • Arc.Elixir (Release v1.1.0): Rules ARCE0001 (a module declares a schema and handle/2 but does not use Arc.Command), ARCE0002 (a command or query is both anonymous and restricted), ARCE0003 (an @observe query has neither :watch nor :topics), ARCE0004 (a command appends to Chronicle itself) and ARCE0005 (two commands or queries resolve to the same route).
  • Arc.Elixir (Release v1.1.0): Configuration with config :cratis_arc, :analyzer: a global enabled switch and a severity per rule (:error, :warning, :info or :off). @arc_analyzer ignore: ["ARCE0001"] turns a rule off for one module, and mix compile --warnings-as-errors fails on warnings from the analyzer.
  • Arc.Elixir (Release v1.1.0): A Code analysis section in the documentation with a page for every rule, and a changelog.
  • AI (Release v7.153.7): A cratis-screenplay-extension-packages skill for creating, verifying, locking, restoring, vendoring and trusting extension packages: the contract and manifest, settings, components, screenplay.lock, cratis extension new, verify, restore, update and vendor, the publisher allow-list and exit codes. (part of #1121)
  • AI (Release v7.153.7): Guidance on invoking an ability from reactions, workflows and state machines with $result and $failure, on realizing a system with an extension, and on what is not yet admitted. (part of #1121)
  • AI (Release v7.153.7): Extension components on screens and given/then invokes ability answers in specifications, as references. (part of #1121)
  • Stage (Release v5.20.0): Browser invocations: a screen component can ask Stage to run an ability, limited to the contract’s invokes allowlist and the screen’s authorization. The request is recorded as a new ScreenInteraction origin, and a repeated interaction identity is a retry, not a second run. (part of #1070)
  • Stage (Release v5.20.0): Public settings for extension components: only settings declared public reach the browser; secret settings never do. (part of #1070)
  • Stage (Release v5.20.0): Static placeholders for pages without a browser runtime (previews, exports, first paint). (part of #1070)
  • Stage (Release v5.20.0): Documentation: “Run extension components” in the extensions section. (part of #1070)
  • Templates (Release v1.9.0): Cratis.Templates.Extensions, a template package of its own, with two templates: cratis-extension for a full extension, and cratis-extension-package for a frontend-only component package. See the extension templates guide. (#104)
  • Templates (Release v1.9.0): cratis-extension takes Backend (csharp, kotlin, go, typescript or none) and Frontend (react, mount, screenplay or none), and every combination is valid, including none with none. cratis-extension-package takes Component (react or mount). Both take DisplayName, Description and Publisher, and the package name is the template name.
  • Templates (Release v1.9.0): Every package contains contract.play with its manifest (display name, description, icon, marketplace image and requirements), a placeholder icon and image, a static HTML placeholder for each React or mount component, a sample ability or component with specifications, build, test, package, verify and publish scripts, a .extensionignore and a README. Each package passes cratis extension verify without edits.
  • Templates (Release v1.9.0): Backends use the Stage extension SDKs and keep the sample ability in plain code, so a specification calls it without a host. React and mount components run the Scene conformance kit in their specifications.
  • Templates (Release v1.9.0): Until the Kotlin, Go and TypeScript backend SDKs and @cratis/scene.extensions are published, the generated scripts use a local build when CRATIS_STAGE_SDK or CRATIS_SCENE_SDK is set, and the README says how.
  • Templates (Release v1.9.0): Documentation for the templates, linked with the Screenplay, Stage, Scene and Cratis CLI documentation.
  • cli (Release v3.134.0): cratis config --requires <model> lists everything a model needs from the selected environment - identity provider keys, named secrets (secrets.<Name>) and the settings of its extensions (systems.<System>.<setting>) - with whether each is set. It never prints a value, and exits with 5 while a key is missing or an extension is not restored. (#577)
  • cli (Release v3.134.0): cratis run admits a model’s extensions before starting Docker: each must be pinned in screenplay.lock and its publisher and reference allowed in .cratis/extensions.json, otherwise nothing starts (exit 5). Contracts are restored from the lock into the digest-keyed cache, and the Stage keeps pulled packages by digest in a cache that survives runs. (#577)
  • cli (Release v3.134.0): cratis run hands the Stage the extension settings as systems__<System>__<setting> configuration, named secrets mapped to the settings that use them, registry credentials, the allow-list and the signing keys of the locked publishers. The Stage starts each backend in its tier when it is first needed. (#577)
  • cli (Release v3.134.0): Documentation for extension settings, named secrets, registry credentials and allow-lists in the environments and run pages, linked with the Screenplay and Stage documentation. (#577)
  • Screenplay (Release v6.24.0): component <System>.<Component> <name> on a screen places a component through the system that names the extension, not through a package. property lines are checked against the contract (PLAY1114, PLAY1115). (#1255)
  • Screenplay (Release v6.24.0): on <signal> under an extension component handles a signal its contract raises, and with <input> from signal.<value> reads a value the signal carries (PLAY1116, PLAY1117). on <System>.<Trigger> anywhere on a screen handles an extension trigger, and PLAY1112 reports one the contract does not offer.
  • Screenplay (Release v6.24.0): PLAY1118 warns when a ui profile targets a platform the component’s contract does not list.
  • Screenplay (Release v6.24.0): The UI contract (export --format ui, MCP read-workspace view ui-contract) carries each placement with the contract’s kind, platforms, placeholder and the static placeholder HTML when the restored package holds a safe one, and lists the extensions each screen needs so a host can start their backends ahead of use.
  • Screenplay (Release v6.24.0): Executable model ESM v52: a screen that places an extension component is admitted with ExecutableScreens.Admit as an ESM v52 screen with extensions and components; default compilations keep their version and bytes. The published esm-v52.schema.json and golden are included.
  • Screenplay (Release v6.24.0): The event model board draws an extension component as an extension-component element named after the component.
  • Screenplay (Release v6.24.0): The TypeScript compiler exports checkExtensionUseSites and reads target platform of a ui profile, matching the C# checks.
  • Screenplay (Release v6.24.0): Monaco and VS Code highlight signal.<value> and document component and signal; the Invoicing sample places Mailer.MailPreview on InvoiceBalance and its vendored contract now lists ios and android.
  • Stage (Release v5.19.0): Execution tiers for backends that come from extension packages: no process for frontend-only extensions, a shared host per runtime (dotnet, node, jvm) that isolates the extensions it loads, a native process, or a dedicated container. The deployment decides what may share a host with Stage:Extensions:Execution:Sharing; anything else needs a container configured under Containers, and a system without one is refused with a message that names the setting.
  • Stage (Release v5.19.0): Lazy activation: a backend starts on the first ability call, proxied request or delivered inbound request that needs it, stops after its idle timeout (ten minutes by default) when nothing is in flight, and starts again for the next call. A call that finds its backend stopped waits for the start and is not lost.
  • Stage (Release v5.19.0): Activation policy: the extension contract’s default, overridden by the system’s own activation always | on demand [idle after <n> <unit>] line in the model. always keeps the backend running and starts it again if it fails.
  • Stage (Release v5.19.0): Frontend-aware activation: reaching a screen that places an extension component starts that extension’s backend before the component’s first call, with POST /stage/extensions/activation/screens/{screen}. Reaching the screen is the trigger and mounting a component is not; the reasoning is in the documentation. Which systems a screen places comes from IScreenExtensionUsage, which is empty until screens can use extension components (Cratis/Screenplay#1255).
  • Stage (Release v5.19.0): Workbench visibility: GET /stage/extensions/activation and a script-free page at /stage/extensions/activation/view show each extension’s tier, state (inactive, starting, active, stopping), policy, last activation and any reason it could not start.
  • Stage (Release v5.19.0): Documentation: Execution tiers and activation, linked with the extension packages page, the Screenplay systems overview and settings page. Part of Cratis/Screenplay#1248. (#1066)
  • cli (Release v3.133.0): cratis extension verify [TARGET] checks a package folder, or a package a registry serves (a catalog short name, an OCI reference or an npm package), and reports every check with a status and exact diagnostics. See https://github.com/Cratis/cli/blob/main/Documentation/reference/extension-verify.md. (part of #576)
  • cli (Release v3.133.0): Checks: the contract compiles with no errors or warnings; the manifest has a display name, a description, an icon and stated requirements, and the icon and marketplace images exist, are png, jpg, webp or svg by their content and are within the size limits; the package ships what the contract declares and nothing else (a folder lists what its build does not ship in .extensionignore); every placeholder is static HTML; the package digest and contract hash match screenplay.lock; and the contract is usable by the Screenplay compiler, with --baseline <FOLDER> to require a drop-in replacement for the previous release.
  • cli (Release v3.133.0): A check that applies but could not run is reported as skipped, never as passed. The frontend (Scene conformance kit) and backend (protocol handshake) checks are skipped for now; --strict fails them, and warnings, too.
  • cli (Release v3.133.0): Human-readable output by default and --format json on request. Exit code 0 when the package is correct, 5 when a check failed, 1 when the target or reference is not found, 2 when a registry is unreachable and 4 when its credentials are refused.
  • cli (Release v3.133.0): A package that cratis extension new creates from templates that follow the documented template interface passes cratis extension verify.
  • Arc (Release v23.2.0): Workload caller admission for Kubernetes workloads on capability ports, with tenantless execution and a token-review cache capped at 30 seconds (#3710)
  • Arc (Release v23.1.0): ISystemAbilities, SystemAbilities and IAbilityInvoker: a system becomes an injectable, substitutable collaborator whose methods are its abilities, and each call is handed to the extension host with the command’s causation (command, correlation, operation, phase) and an idempotency key that is stable for the call and differs between Execute and Compensate. A failed ability throws AbilityInvocationFailed, which fails the command and triggers compensation as for any other operation. (part of #3792)
  • Arc (Release v23.1.0): The Screenplay generator reads an operation whose Execute and Compensate only call abilities into invokes <System>.<Ability> phases, declares each invoked system with its abilities, and supports operations that invoke more than one system. A phase that does anything else stays in code and reports why. (part of #3792)
  • Arc (Release v23.1.0): Documentation: Invoke Screenplay abilities from command operations, linked with the Screenplay operations and Stage ability invocations pages. (part of #3792)
  • cli (Release v3.132.0): cratis extension new creates a full extension (an OCI artifact) or a frontend-only component package from the Cratis.Templates.Extensions templates. A full extension takes a --backend (csharp, kotlin, go, typescript or none) and a --frontend (react, mount, screenplay or none); a frontend-only package takes a --component (react or mount). Every package gets a contract.play with its manifest, a placeholder icon and image, a static HTML placeholder per frontend component, a sample ability or component with specs, a README and the build and publish scripts. See https://github.com/Cratis/cli/blob/main/Documentation/reference/extension-new.md. (part of #575)
  • cli (Release v3.132.0): An interactive wizard that asks only what the flags did not answer. The wizard and the flags build the same request and are held to the same rules, so they create the same package. --no-prompts never asks; --dry-run lists the files; --format json reports them.
  • cli (Release v3.132.0): --template-path, --package and --version choose where the templates come from. The CLI fails with exit code 2 and names the symbol when a template does not offer a choice the request needs.
  • cli (Release v3.132.0): The template interface, the names of the templates and the symbols the CLI passes to them, is documented so the templates can be built against it.
  • Stage (Release v5.18.0): Extension packages are loaded from the model’s screenplay.lock: full extensions as OCI artifacts and frontend-only packages from npm. Stage fetches exactly the locked digest, never a tag or a version range, caches it by digest and hashes the bytes against the lock on every read. See https://github.com/Cratis/Stage/blob/main/Documentation/extensions/packages.md. (#1064)
  • Stage (Release v5.18.0): Trust is decided by the deployment, never by the model: an allow-list of publishers and references in .cratis/extensions.json, narrowed by Stage:Extensions:Packages:Allow, and a signature that must verify against the key of the publisher the lock records (cosign key-based signatures for OCI, the registry signature for npm). Registry credentials come from Stage:Extensions:Packages:Registries only.
  • Stage (Release v5.18.0): A package that is not allowed, not signed, signed by another key, has another digest or contract than the lock, needs another Stage or Screenplay version, ships a placeholder that runs script or is not safe to unpack is refused with its reason through /stage/semantic/admission. The model is not loaded while a package is refused, and a published host refuses to start.
  • Stage (Release v5.18.0): Every ability of an extension is pinned to the locked package digest, so every workflow run pins the package that was admitted. IExtensionPackages and LoadedExtensionPackage.UnpackBackend expose the loaded packages and their verified backend bytes for activation.
  • Stage (Release v5.18.0): Frontend assets are served at /extension-assets/{id}/{path}, and the manifest icon, images and each component’s placeholder under /stage/extensions/packages/{id}. Placeholders are served with a content security policy that forbids scripts and external loads, and only into a frame.
  • Stage (Release v5.18.0): GET /stage/extensions lists loaded and refused extensions with their manifest, images, contents and requirements, and /stage/extensions/view renders the same listing as a page.
  • Screenplay (Release v6.23.0): invokes <System>.<Ability> in reactions, with the ability’s inputs and one branch per answer: on returned (reads $result.<field>), on failed (reads $failure.reason) and on <Outcome> for a declared outcome. (#1252)
  • Screenplay (Release v6.23.0): Workflow actions invoke abilities too, with an edge per outcome and values mapped from literals, the subject or an earlier node’s result (Node.field). A compute node, an approval answered through an ability (via) and expires after parse, print and validate.
  • Screenplay (Release v6.23.0): State entries invoke abilities: entering invokes <System>.<Ability>, or a bare entering with a C# body.
  • Screenplay (Release v6.23.0): Specifications script an ability’s answer with given <System>.<Ability> returns, answers or fails and assert the call with then invokes. The reference evaluator runs reactions that invoke abilities.
  • Screenplay (Release v6.23.0): Diagnostics PLAY1001 to PLAY1017 cover unknown targets, unmapped or mistyped inputs, unreachable or duplicate branches, values read outside their branch and abilities that answer later.
  • Screenplay (Release v6.23.0): Executable semantic model v51 carries reaction, workflow-action and state-entry invocations. Models that invoke no ability keep v50 or earlier.
  • Screenplay (Release v6.23.0): The TypeScript compiler, the Monaco editor (completion, highlighting, hover), the VS Code grammar, the event model board and the MCP operation inventory (invokedBy call sites) understand the new forms.
  • Screenplay (Release v6.23.0): A Shipping sample with a REST carrier and a chat system invoked from a reaction, a workflow and a state machine, and ability invocations in the Invoicing sample.
  • cli (Release v3.130.0): cratis extension restore fills the extension cache from screenplay.lock. A reference the lock does not pin is resolved to the newest release in its range and pinned with its version, digest, contract hash and publisher. --locked fails on a missing or mismatched entry and never changes the lock. (part of #578)
  • cli (Release v3.130.0): cratis extension update [SYSTEM] moves one system’s extension, or every referenced extension, to the newest release in its range. It reports what each new contract adds, removes or changes, and every use in the model the new contract no longer offers, before the lock is written. --dry-run writes nothing; --allow-incompatible writes anyway.
  • cli (Release v3.130.0): cratis extension vendor <DESTINATION> copies every locked package, with its signature, to a folder or an oci://host/prefix registry for air-gapped deployments. cratis extension restore --source <DESTINATION> then restores from the copy without reaching the original registries.
  • cli (Release v3.130.0): Packages come from catalog short names ("cratis/stripe"), full OCI references and frontend-only package references. Private registries authenticate with credentials stored through cratis config under extensions.registry.<host>.token (or username and password); no command prints a credential.
  • cli (Release v3.130.0): Trust: a package must be signed, its signature must be valid for its digest, and its publisher must be on the project’s allow-list in .cratis/extensions.json. A first-time publisher is confirmed interactively and recorded; a non-interactive run fails instead. A publisher whose key changed is never offered for trust.
  • cli (Release v3.130.0): Reference pages for the extension commands, linked with the Screenplay extension contracts and lock reference.
  • Screenplay (Release v6.22.0): The extension contract file: display name, description, icon, image with captions, requires stage | screenplay | platform | runtime, setting <name> [public | secret], ability, trigger, component (kind, platform, placeholder, property, raises, invokes), backend and frontend, parsed by both the C# and the TypeScript compiler. A setting that is both public and secret is an error, so a secret can never reach a browser. See https://github.com/Cratis/Screenplay/blob/main/Documentation/screenplay/extension-contracts.md. (#1253)
  • Screenplay (Release v6.22.0): A system that names an extension gets the contract’s abilities, and its triggers are available to reactions as when <System>.<Trigger>. Settings are checked against the contract.
  • Screenplay (Release v6.22.0): screenplay.lock, a plain-text lock beside the model root that pins each reference’s version, digest, contract hash and publisher, with a vendored extensions folder and a digest-keyed cache.
  • Screenplay (Release v6.22.0): screenplay restore [<folder>] [--locked] [--update] [--source <directory>] [--vendor] to pin and restore extensions; --locked is for CI and never resolves a range.
  • Screenplay (Release v6.22.0): Provider compatibility: a use of a trigger the extension no longer offers is reported at each use (PLAY1112), and ExtensionCompatibility.Mismatches compares two contracts.
  • Screenplay (Release v6.22.0): Editors (screenplay mcp, the language service) restore unresolved references automatically and report them as warnings until they are restored.
  • Screenplay (Release v6.22.0): Diagnostics PLAY0998, PLAY0999 and PLAY1100 to PLAY1113, Monaco and VS Code highlighting of contract lines, and a locked extension in Samples/Invoicing.
  • AuthProxy (Release v2.61.0): A signed urn:cratis:bearer:resource claim on the forwarded bearer principal, set to the configured audience the token was validated against, so a backend can confirm the token was issued for the resource it serves (#324).
  • AuthProxy (Release v2.61.0): A startup warning when a bearer route is configured but no ingress proxy is trusted, so every request would be refused (#323).
  • Stage (Release v5.17.0): The built-in http extension. An ability’s http block gives the method and path, headers, query, a structured body, what each response status returns, and which status settles with a named outcome. It decorates the registered ability backend, so abilities without a block still reach their connected extension backend. Register it with AddStageHttpAbilities after the invocations. It runs in-process; moving it to packaged extensions follows Cratis/Stage#1064. (#1069)
  • Stage (Release v5.17.0): Base address and authentication (none, bearer, basic or apiKey) come only from the settings and secrets of the system, systems:<System>:Http:*. The model holds no credential: a block that sets Authorization, Cookie, X-API-Key or Host is an error. Secrets are never logged or put in a failure reason, and redirects are not followed.
  • Stage (Release v5.17.0): A response with no matching line fails the ability: a client error other than a timeout rules the effect out, anything else (a server error, a timeout, a dropped connection) leaves it open for reconciliation. A missing setting or input is reported as not sent, naming the setting and never its value.
  • Stage (Release v5.17.0): A reference page for the block: https://github.com/Cratis/Stage/blob/main/Documentation/extensions/http.md
  • Stage (Release v5.16.0): Inbound requests with a method that may change something (POST, PUT, PATCH, DELETE) to /extensions/<System>/... are stored with their raw body and headers and acknowledged with 202 Accepted before the extension is involved. An extension that is not running is activated to take delivery. (part of #1068)
  • Stage (Release v5.16.0): Delivery with retries: 2xx is delivered, a 4xx such as 401 for a signature that does not verify is rejected for good and never retried, and 408, 425, 429, 5xx or no answer retry with a doubling wait until MaxAttempts, then show as failed. Every attempt carries the same delivery identity as invocation_id and idempotency_key.
  • Stage (Release v5.16.0): Replay protection: a request identical in method, path, query and body to one already held is acknowledged and not delivered again, while the first is waiting and for ReplayWindow (24 hours). A request that was given up on is not treated as a replay, so a sender’s retry is delivered.
  • Stage (Release v5.16.0): A cap on waiting requests (MaxOpen, answers 503 with Retry-After) and a streamed body limit, so an anonymous sender cannot fill storage.
  • Stage (Release v5.16.0): Workbench endpoints GET /stage/extensions/deliveries and POST /stage/extensions/deliveries/retry list inbound traffic with its status, attempts and last outcome, and retry a failed or rejected request. They never show a body or header values.
  • Stage (Release v5.16.0): correlation_key on RaiseTrigger, so a raised trigger also resumes the workflow runs that wait for it about the same thing. HostServices.Trigger takes a correlationKey.
  • Stage (Release v5.16.0): C# SDK WebhookSignature verifies an HMAC-SHA256 signature in constant time, with an optional signed timestamp and tolerance to refuse a captured request replayed later. HttpCall carries DeliveryId and Attempt.
  • Stage (Release v5.16.0): Documentation: Inbound traffic and webhooks, linked from the extensions overview, the protocol and host services references, the connect-a-backend guide and the C# SDK page.
  • Stage (Release v5.16.0): Settings under Stage:Extensions:Inbound.
  • Screenplay (Release v6.21.0): secret <Name> (top level, optional description), setting <name> from secret <Name>, setting <name> = <literal>, extension "<package>" version <v> and activation always | on demand [idle after <n> <unit>] under a system, in both the C# and TypeScript compilers, with diagnostics PLAY0990 to PLAY0997. (#1254)
  • Screenplay (Release v6.21.0): Settings, secrets and activation are exposed on the semantic compilation as realization metadata; they change no executable-model bytes.
  • Screenplay (Release v6.21.0): EnvironmentRequirements lists named secrets; unmapped settings read from systems.<System>.<setting>. EnvironmentRequirements stays C#-only.
  • Screenplay (Release v6.21.0): Highlighting, completion and hover for the new lines in the Monaco language service and VS Code, plus documentation in Environments, Systems and Grammar and an Invoicing sample.
  • Stage (Release v5.15.0): The extension protocol, cratis.stage.extensions.v1, as versioned .proto files under Source/Extensions/Protocol, linted with buf. Stage calls Describe (a handshake that checks the running backend against the contract of its system), Invoke, HandleHttp and Health; the backend calls GetSetting, GetSecret, RaiseTrigger, Answer, Log and RecordMetrics. Every request carries the tenant, invocation identity, idempotency key, attempt, deadline and trace context.
  • Stage (Release v5.15.0): Durable ability invocations now reach a backend: set Stage:Extensions:HostPort and list each system’s backend under Stage:Extensions:Backends. Without it nothing listens and abilities answer “not sent” as before. A backend that cannot be reached, fails the handshake or does not honor its contract is “not sent” and safe to retry; an error after the call was sent is “may have reached the system”.
  • Stage (Release v5.15.0): Host services on a separate gRPC port, scoped to one system by a session credential delivered only in the handshake. Secrets reach an extension only through GetSecret, never through its environment or a file. Raising a trigger needs a deduplication key and reports when nothing reacts to it. Logs and metrics are tied to the invocation’s causation.
  • Stage (Release v5.15.0): Inbound HTTP at /extensions/<System>/<path>, routed to the backend that declared the route. Cookies and authorization headers are not forwarded.
  • Stage (Release v5.15.0): SDKs with their own tests, build and a minimal example: Cratis.Stage.Extensions (C#, net10.0 and net11.0), io.cratis.stage:stage-extensions (Kotlin), a Go module and @cratis/stage-extensions (TypeScript). Each passes the shared conformance suite in Source/Extensions/Conformance over the wire.
  • Stage (Release v5.15.0): Documentation: the protocol reference, host services reference, connecting a backend, the conformance suite and a getting-started page for each SDK, linked with the Screenplay, Choreography and Scene documentation. The protocol and SDKs live in Cratis/Stage, and version one leaves out a key-value state store and an outbound credential proxy; the overview explains why. (#1065)
  • Stage (Release v5.14.0): ESM v43 is audited. A set once mapping renders as Chronicle’s SetOnce. A children collection renders its ordering: insert first as Prepend(), and sort by as OrderBy or OrderByDescending on the child property. The specification runner runs both, and the reference runner agrees on the set-once keep-first rule and on both sort directions. (part of #1056)
  • AI (Release v7.153.6): A systems-and-abilities reference in the Screenplay automations skill: declaring a system and its abilities, choosing safe, idempotent or once, typed inputs, returns, outcomes and answers later. (part of #1121)
  • Stage (Release v5.13.0): Durable ability invocations: an invocation is recorded with the fact, run or transition that caused it before anything runs, then performed by a Choreography run under the capability ability:<System>.<Ability>@<contract major> with the extension package digest pinned. Its identity is derived from the origin’s semantic address and causation, never the attempt, and is the grain key, the run’s deduplication key and the idempotency key the extension receives. (#1067)
  • Stage (Release v5.13.0): Effect classes: safe retries freely, idempotent retries with the same key, and once is never retried when an attempt may have reached the system. It stops for reconciliation instead, including when a restart interrupts an attempt.
  • Stage (Release v5.13.0): GET /stage/invocations lists invocations and the ones stopped for reconciliation. POST /stage/invocations/{identity}/reconciliation records which outcome happened and the origin continues from that choice. POST /stage/invocations/{identity}/answer answers an ability that answers later, after checking the identity against the persona or policy the invocation names. Both are sandbox tooling and are not mapped in a published runtime.
  • Stage (Release v5.13.0): Per-system gates from deployment configuration under Stage:Invocations:Systems: MaxConcurrent, RequestsPerSecond and MaxAttempts.
  • Stage (Release v5.13.0): Documentation: Durable ability invocations, linked with the Screenplay reactions, workflows, state machines and operations pages and with the Choreography runtime pages.
  • Choreography (Release v2.6.0): useCanvasPresence in @cratis/choreography/collaboration/react shares this session’s position on a canvas: it holds the room’s connection while the canvas is mounted, announces the canvas as soon as it opens, maps the pointer into content space, follows the content under a pointer that stands still while the canvas pans or zooms, and leaves the area when the canvas closes. Wire its handlePointerMove onto the canvas and call handleTransformChange when it pans or zooms. See Send the pointer position.
  • Choreography (Release v2.6.0): contentPointOf and reportCanvasPresence in @cratis/choreography/collaboration do the same steps without React, and PresenceSink describes what they send to.
  • Screenplay (Release v6.20.0): ability <Name> [safe | idempotent | once] under a system, with typed inputs, a returns block, outcome <Name> lines, answers later, and an AbilityEffect implementation (file, tagged fence or implementation wrapper). An omitted effect class means once, which is never retried. Both compilers parse, validate, print and round-trip them, held equal by a new conformance document (#1250).
  • Screenplay (Release v6.20.0): Diagnostics PLAY0983 (duplicate ability, compared ignoring case), PLAY0984 (unknown effect class), PLAY0985 (outcome named next, refused, failed, returned or expired) and PLAY0986 (undeclared input or returned type). Malformed abilities, outcomes with a payload and empty returns blocks report PLAY0495.
  • Screenplay (Release v6.20.0): Executable semantic model v50: a model that declares an ability carries application.systems with each ability’s effect class, typed inputs and returns, outcomes, answersLater and realization (none or code). Models without abilities keep their bytes and version. The ESM v50 JSON Schema and golden vector are published.
  • Screenplay (Release v6.20.0): A “Systems and abilities” guide, grammar and diagnostics reference entries, and an ability-declaring PaymentGateway system in the Invoicing sample.
  • Screenplay (Release v6.20.0): Ability completion, hover, validation and highlighting in the Monaco language service and the VS Code grammar, and ability details in the MCP system-intent-details view.
  • Chronicle (Release v19.156.0): The production image ships createdump, so setting DOTNET_DbgEnableMiniDump=1 writes a crash dump. The production and Kubernetes hosting pages describe how to enable, size, collect and safely handle dumps (#5814)
  • Chronicle (Release v19.156.0): connectedClients.subscriptionCheckIntervalSeconds (default 60) and connectedClients.subscriptionSettleSeconds (default 30) control how often reactor and reducer subscriptions are checked once they are known to be intact, and for how long they are checked closely after a silo leaves the cluster (#5816)
  • Chronicle (Release v19.156.0): The container resources page publishes measured container profiles for 1, 2 and 4 CPUs with the default, Workstation and classic Server garbage collectors, and the benchmark harness accepts --cpus and --memory to measure your own sizes (#5110)
  • Scene (Release v5.3.0): New npm package @cratis/scene.extensions 1.0.0: the extension component contract with two component kinds, reactComponent(Component) (web only) and mountComponent((host, properties, context) => { update, unmount }), a framework-neutral floor for Vue, Svelte, Lit, web components or plain DOM. (#296)
  • Scene (Release v5.3.0): ExtensionContext with the user, tenant, locale, theme, public settings, strings, invoke, raise, on and change notifications, and createExtensionContext for hosts, previews and specs to build and change one.
  • Scene (Release v5.3.0): React hooks useExtensionContext, useUser, useTenant, useLocale, useTheme, useSettings, useStrings, useInvoke, useRaise and useTrigger, which re-render only when their own part changes, with ExtensionContextProvider.
  • Scene (Release v5.3.0): Composition in both directions: MountedComponent lets a React component host a mount component, context.renderSlot and ExtensionSlot host Scene content, and mountExtensionComponent gives a host one path for both kinds.
  • Scene (Release v5.3.0): Frontend manifest types and validateFrontendManifest for the component part of an extension contract.
  • Scene (Release v5.3.0): A conformance kit, createExtensionConformanceChecks, that runs the same expectations against a component of either kind.
  • Scene (Release v5.3.0): resolveExtensionComponent in @cratis/scene.engine resolves extension components from a UI profile’s packages alongside runtime packages, including shadowing and platform support.
  • Scene (Release v5.3.0): Documentation: a contract reference and a how-to for building a component in React and with mount, linked with the Screenplay screens page and Stage custom packages.
  • Screenplay (Release v6.19.0): A workflow action <Node> invokes <Command> has a refused outlet, separate from failed. A refused command is not retried, and an unconnected refused outlet fails the run. (part of #1251)
  • Screenplay (Release v6.19.0): A deprecation migration note in the state machine and workflow documentation, and a specification section for state machines and workflows.
  • cli (Release v3.128.0): cratis render --upgrade-profile moves an existing Cratis application to the newest scaffold profile (.NET 11) (#579)
  • Stage (Release v5.12.0): The generated policy reads the caller’s identifier from the principal Arc authorized: the urn:cratis:identity:subject claim first, then the name identifier claim, then sub. A principal that carries none, or two different values of the first claim it has, makes the policy unavailable, so it denies, including for !=. An application that identifies callers another way implements the partial method ResolveCallerId on the generated PolicyValues class. (#1061)
  • Stage (Release v5.12.0): A specification’s caller can name its identifier with id "alice"; the generated test puts it in the principal’s name identifier claim, and the in-process specification runner evaluates the policy the same way.
  • Choreography (Release v2.5.0): WorkflowNodeOutcome.Suspended(key, expiresAfter): a performer that accepted the work answers later. The node waits like a wait without holding a worker, and ends when it is completed by key or expires through the expired outlet (#200)
  • Choreography (Release v2.5.0): IWorkflowCompletions.Complete completes the suspended node by WorkflowCompletionKey, and WaitKind.Completion is a new wait kind
  • Choreography (Release v2.5.0): WorkflowsOptions.CapabilityLimits bounds the performer calls of a capability in flight on a silo, by capability id or a prefix such as ability:Slack.*, through IWorkflowCapabilityGates
  • Choreography (Release v2.5.0): IWorkflowRun.Reconcile resumes a run stopped on an ambiguous outcome with a chosen success, failure or skip, recorded as WorkflowNodeReconciled with the actor. IWorkflowRun is now at [Version(1)]
  • Choreography (Release v2.5.0): NodeExecutionSnapshot.Reason and NodeExecutionSnapshot.IdempotencyKey tell a person what was ambiguous and which invocation to look up
  • Choreography (Release v2.5.0): Documentation: suspension by key, capability gates and reconciliation, linked with the Stage invocation work
  • Chronicle.Elixir (Release v3.23.0): The :observation_reconnect client option (base_delay, max_delay, healthy_stream_duration, in milliseconds) tunes the stream reconnect backoff, and invalid values are rejected when the client starts
  • Stage (Release v5.11.0): CratisRendering.CreateProfile has an overload that takes a scaffold profile version. Version 3 (net10.0) stays the default; passing "4" creates a net11.0 profile that the artifact render planner admits, and an unsupported version is refused with an error naming the supported versions (#1078)
  • Stage (Release v5.10.0): The Host and the spec runner can pass a scaffold profile version to the body worker (Stage:BodyWorker:ProfileVersion for the Host, --body-worker-profile-version for the spec runner). Version 4 analyzes method bodies against .NET 11 references. When no version is set, version 3 (.NET 10) is used as before. An unsupported version is rejected at startup with a message that names the supported versions. (#1074)
  • Stage (Release v5.9.0): Version 4 of the Cratis render profile renders applications that target .NET 11; version 3 keeps targeting .NET 10 (part of #1047)
  • Arc (Release v22.185.1): CratisProxiesSkip (alias DisableProxyGenerator) MSBuild property that skips TypeScript proxy generation for a build, for example -p:CratisProxiesSkip=true (#3799).
  • Chronicle (Release v19.155.0): Client packages now target net11.0 alongside net10.0 (#5763)
  • Chronicle (Release v19.154.1): A Kubernetes hosting guide with a reference manifest tested on a three-node cluster: StatefulSet with anti-affinity and a PodDisruptionBudget, startup, readiness and liveness probes on a dedicated exclusive health port, a hardened security context for the chiseled image, NetworkPolicies for the kernel’s ports, guidance for running with TLS and authentication off, choosing between Recreate and rolling updates, and handling the connection string, certificates and the encryption certificate (#5793)
  • Chronicle (Release v19.154.1): The container resources page describes a small-container profile and a throughput profile, with the garbage collector settings for each and the commands to measure them on your own workload (part of #5110)
  • Chronicle (Release v19.154.0): Observer state and job progress are published as metrics: failed and quarantined partitions and running state per observer (reported only while an observer needs attention, then as zero for a short while after it recovers), resident observers per event store, namespace and type, running catch-up and replay jobs, catch-up and replay progress per observer, and cratis.chronicle.event_sequence.append.duration as a histogram in seconds. The maximum number of series per metric can be set with Telemetry:MetricSeriesLimit (#4610)
  • Chronicle (Release v19.154.0): Opt-in standby for start-before-stop rollouts (Clustering:SingleWriterLease:Standby). A replacement kernel waiting for the single-writer lease reports ready with a Standby status so Azure Container Apps, Cloud Run and Kubernetes rolling updates can stop the old instance. Event processing starts only once the lease is held, client calls during standby fail with a retryable status, and Clustering:SingleWriterLease:StandbyStartupTimeout bounds how long a kernel that holds the lease may keep reporting standby while it starts (#5238)
  • Chronicle (Release v19.154.0): observers:maxConcurrentSubscriptions bounds how many observer subscriptions and failed-partition recoveries a silo runs at once across all event stores. By default it is sized to the machine’s CPUs
  • Chronicle (Release v19.154.0): observers:idleDeactivationAfter releases an observer that has no subscription and no pending work after it has been idle for that many seconds (900 by default, 0 turns it off). Releasing an idle observer frees about 40 KB of memory, and a benchmark in Benchmarks/Chronicle.Benchmarks.Kernel measures what an activation retains (#5792)
  • AI (Release v7.153.0): Host-prepared workspace mode for Docker workers: set CRATIS_WORKSPACE_MODE=host-prepared and CRATIS_WORKSPACE_HOST_PATH to mount an existing checkout at /workspace instead of cloning. The path is validated before launch, git metadata is mounted read-only, and the worker leaves its results as uncommitted working-tree changes. Kubernetes workers refuse host-prepared jobs with a clear error (#1070)
  • AI (Release v7.153.0): CRATIS_GIT_DEADLINE_SECONDS (default 600) bounds every git command a worker runs; a command that exceeds it is stopped and reported as [git-timeout] (#1069)
  • Choreography (Release v2.4.0): net11.0 targets alongside .NET 10, using the .NET 11 System.Text.Json and Microsoft.Extensions.Logging.Abstractions packages on .NET 11 (#197)
  • Dockerfiles (Release v8.1.0): .NET 11 base development images (cratis/base:dotnet11 and cratis/base-mongodb:dotnet11) built on the .NET 11 GA ASP.NET Core runtime for Ubuntu 26.04; the existing .NET 10 images and tags are unchanged (#26)
  • Stage (Release v5.8.0): An action on a screen is checked against the server before it is offered. The server decides from the same policy that guards the command, so a policy that reads recorded state, such as the plan of the asset on the screen, answers for that asset. A refused action is shown disabled with the reason on hover, and is asked again when the data the screen reads changes. Only an explicit refusal withholds the action: an unanswered or failed check leaves it offered, and the server still decides when the command runs. (part of #1050)
  • Screenplay (Release v6.17.0): SemanticScreenAvailability.Evaluate reports every element of a screen as available, unavailable or undecided for a caller. It names the policies that gate the element and why it is withheld. A policy that decides from recorded state is evaluated against the data the screen is showing, so one asset’s plan can offer an action that another’s withholds. A missing instance denies, and an opaque predicate is undecided rather than available. The report presents the fact and never replaces enforcement. (part of #335)
  • Stage (Release v5.7.0): Audit of ESM v48 (agent exposure) and v49 (the caller’s identifier in a policy state condition). Agent exposure is a contract for the hosting surface, so the generated backend neither renders nor refuses it.
  • Stage (Release v5.7.0): A policy that compares a recorded property with $identity.id, and a caller fixture that names an identifier, are refused with STAGE-ESM-016. Stage has no mapping from Arc’s authorization principal to that identifier yet, and a wrong guess would let the wrong caller through. (part of #1061)
  • Screenplay (Release v6.16.0): article.author == $identity.id (or !=) in a policy state condition, over a required text property. A caller with no identifier gives nothing to compare, so the condition is false and a policy that cannot tell who is asking never allows. (#1233)
  • Screenplay (Release v6.16.0): id "alice" on a given caller fixture, the value $identity.id reads when a specification runs.
  • Screenplay (Release v6.16.0): ESM v49, selected only by a model that uses either; every earlier model keeps its bytes and revision. The conformance corpus and the C# and TypeScript compilers cover it.
  • Chronicle (Release v19.153.1): The production hosting page recommends an exclusive health port (Cratis__Chronicle__Health__Exclusive=true) together with the dedicated health port, explains that the Workbench must then be served from the main port, and the Workbench hosting page shows the reverse proxy setup that works with it, including how to trust the kernel’s certificate (#5794)
  • Chronicle (Release v19.153.1): The container resources page has a measured sizing example from a production kernel, with the queries to reproduce each figure, a rule of thumb for memory per grain activation, guidance that CPU is sized for cold start, and a guide to choosing between a shared kernel and a kernel per tenant (#5795)
  • Screenplay (Release v6.15.0): An agents block declares an explicit, default-deny list of the queries and commands an AI agent may call, each with a required description and a read or write scope, for personal access tokens. The executable semantic model carries it as ESM v48, and the compiler, MCP server, CLI, Monaco editor and VS Code extension all understand it. (part of #1165)
  • Screenplay (Release v6.15.0): screenplay export --format capability-manifest and the MCP capability-manifest workspace view emit the screenplay-capability-manifest/1 allowlist from the agents block only. Nothing is emitted when the model has errors or no agents block, and a failed export removes an earlier manifest file. The schema and a paired example are published at https://github.com/Cratis/Screenplay/blob/main/Documentation/screenplay/capability-manifest-v1.schema.json. (#1199)
  • Stage (Release v5.6.0): Rendering of narrow <Policy> on a collection query (ESM v47) as an Arc row narrowing. The generated narrowing decides each row with the policy’s reads keyed by the row’s own properties, and Arc applies the result before sorting, paging and counting. A row whose state is absent, unreadable or rejected is dropped. (#1049)
  • Chronicle.Go (Release v0.14.0): Sequence.Import imports entries in bulk from an iter.Seq2[Entry, error]: every event is validated before anything is committed, entries are read as they upload and sent in chunks, and the commit runs on the kernel as a job.
  • Chronicle.Go (Release v0.14.0): Sequence.BeginImport opens an explicit ImportSession for adding entries in steps, and Sequence.ReattachImport resumes a session by its ImportID after a dropped connection.
  • Chronicle.Go (Release v0.14.0): Entry carries an imported event’s correlation id, caused-by identity, generation, source sequence number and idempotency key. Appends, batches and units of work refuse entries that set them, rather than dropping them silently.
  • Chronicle.Go (Release v0.14.0): The contracts/imports package with the generated Imports service contracts.
  • Chronicle.Elixir (Release v3.22.0): Chronicle.Imports.import/2 imports any Enumerable, a lazy Stream included: every event is validated before anything is committed, the source is read while it uploads and sent in chunks, and the commit runs on the kernel as a job. import_async/2 runs it as a Task.
  • Chronicle.Elixir (Release v3.22.0): Explicit import sessions: begin/1 opens one, Chronicle.Imports.Session.add/2 adds events in steps, complete/1 and abandon/1 end it, and reattach/2 resumes a session by its import id after a dropped connection.
  • Chronicle.Elixir (Release v3.22.0): get/2 reads an import’s state, and observe/2 delivers its progress as messages to a process until unobserve/1.
  • Chronicle.Elixir (Release v3.22.0): EventForEventSourceId carries an event’s correlation id, generation, source sequence number, idempotency key and named tags, which an import keeps on the stored events.
  • Stage (Release v5.5.0): Rendering of Screenplay policies with reads and state conditions (ESM v44 to v47): the generated policy reads each declared read model by the key the operation supplies, and a missing key, a missing instance or a failing read denies. A negated condition cannot turn an absent instance into an allow. Text and membership conditions (contains, starts with) and typed policy inputs with authorize mappings render the same way. (#1048)
  • Stage (Release v5.5.0): The ESM pairs v44 to v47 are audited. A query that narrows its rows (v47) is refused with STAGE-ESM-016 until list narrowing renders, so no model silently returns every row. (part of #1049)
  • Chronicle.TypeScript (Release v6.62.0): eventLog.import(events, options?) imports events in bulk from an AsyncIterable or an Iterable: every event is validated before anything is committed, the events are read as they upload and sent in chunks, and the commit runs on the kernel as a job.
  • Chronicle.TypeScript (Release v6.62.0): beginImport(options?) opens an explicit import session for producers that are not a single stream, with add, complete, abandon and a progress() stream, and beginImport(importId, options?) reattaches to a session after a dropped connection, continuing after the chunks the kernel already acknowledged.
  • Chronicle.TypeScript (Release v6.62.0): EventForEventSourceId gains correlationId, causedBy, generation and sourceSequenceNumber, which an import keeps on the stored events.
  • Chronicle.TypeScript (Release v6.62.0): ReactorScenario delivers the events of one events(...) call, or of a page(...) across event sources, to reactor batch methods as one page; shouldHaveFailed and shouldHaveDeferred assert what a batch method settled.
  • Chronicle.Kotlin (Release v7.9.0): eventLog.import(events) imports events in bulk from a Flow or a Sequence: every event is validated before anything is committed, the events are read lazily and sent in chunks, the commit runs on the kernel as a job, and progress is reported while it runs. Imported events reach every observer once.
  • Chronicle.Kotlin (Release v7.9.0): beginImport() opens an explicit import session for adding events in steps, and beginImport(importId) reattaches to a session after a dropped connection.
  • Chronicle.Kotlin (Release v7.9.0): Java callers get the same through importEvents(...) and beginImport(...) on the blocking event sequence, returning CompletableFuture.
  • Chronicle.Kotlin (Release v7.9.0): EventForEventSourceId carries an event’s correlation id, caused-by identity, generation, source sequence number and idempotency key, which an import keeps on the stored events.
  • Chronicle.Kotlin (Release v7.9.0): EventBatch exposes the partitions a batch method deferred and failed.
  • Chronicle.Kotlin (Release v7.9.0): ReadModelScenario runs reducers whose method takes an EventBatch, calling it once per fold the way Chronicle delivers a page; a failed partition rethrows its error and a deferred one throws ReducerDeferred.
  • AI (Release v7.151.0): Agent worker callbacks report why a push of committed work failed as a fixed category (permission, non-fast-forward, hook, authentication, network or unknown), without including git’s error output. (#1100)
  • Chronicle (Release v19.153.0): Client reducers that take pages receive events in pages spanning many event sources on live delivery, catch-up and replay. The kernel reads the current read models of a page together, writes the event sources that succeeded together, and writes nothing for an event source the reducer failed or deferred. See Batches for reducers.
  • Chronicle (Release v19.153.0): [BatchSize] on a reactor or reducer declares the most events and bytes in one page and, for reducers, how many event sources of a page are reduced at once (MaxConcurrency, the processor count by default). MaxDelayMilliseconds is accepted but not applied yet.
  • Chronicle (Release v19.153.0): The kernel honors the page bounds a client declares on every path, capped by the new Observers.MaxEventsPerPage (1 000 by default) and Observers.MaxBytesPerSubscriberCall (4 MiB by default) settings. A delivery above the bounds is sent as several pages in order, and a single event larger than the byte bound is sent on its own. See Observers configuration.
  • Chronicle (Release v19.153.0): Analyzers CHR0070 to CHR0077 report batch method mistakes at compile time: [Observes<T>] on a method that does not take an EventBatch, a batch method that observes nothing, an event type that reaches more than one method, a BatchContext on a per-event method, a reactor batch method that returns something, a reducer that mixes batch and per-event methods, a batch signature Chronicle cannot call, and a warning for a pattern on an event type the method does not observe. See Code analysis.
  • Chronicle (Release v19.153.0): Registering a reactor or reducer refuses a batch method whose parameters Chronicle cannot supply, and a per-event reducer method that takes a BatchContext. A batch method may declare CancellationToken cancellationToken = default.
  • Chronicle (Release v19.153.0): ReactorScenario runs batch methods: the events of one Events(...) call, or of Given.Page(...) across event sources, reach them as one page, and ShouldHaveFailed and ShouldHaveDeferred assert what a batch method settled. ReadModelScenario runs batch reducers and surfaces a deferral as ReducerDeferred.
  • Chronicle (Release v19.153.0): Event sequences can import large volumes of events through a resumable import session: eventLog.Import(events) takes an IAsyncEnumerable or IEnumerable and streams it in chunks, and BeginImport gives an explicit session that can be reattached by ImportId. Every event is validated before anything is committed, the commit runs as a job that survives restarts without appending twice, ordinary appends keep flowing during the commi
  • AuthProxy (Release v2.59.0): Opt-in DPoP proof verification on OAuth bearer routes: DPoP authorization scheme, ES256 proofs only, htm, htu (from the configured public origin only), iat window, ath access-token binding and cnf.jkt key binding, with WWW-Authenticate challenges (part of #258).
  • AuthProxy (Release v2.59.0): A shared Redis replay store so a proof jti cannot be reused on another replica, with fail-closed handling when the store is unavailable, its clock is off or it was just provisioned (part of #258).
  • AuthProxy (Release v2.59.0): Optional server-issued DPoP nonces, bound to the key and origin (part of #258).
  • AuthProxy (Release v2.59.0): DPoP configuration documentation covering the public origin, the replay store and deployment requirements (part of #258).
  • Chronicle.Go (Release v0.13.0): Graph projections: the graphs package declares nodes with graphs.NewNode[T]() (one field tagged chronicle:"key"), edges with graphs.NewEdge[T](source, target) and the graph with graphs.New(name, elements...).Build(), registered with Registry.AddGraph. See Graph projections.
  • Chronicle.Go (Release v0.13.0): Graph node and edge options From, RemovedWith (with graphs.Detach() for nodes), UsingKey, UsingSourceKey, UsingTargetKey, UsingIdentity, OnlyWhenExisting, mappings Set, SetFromContext, SetFromEventSourceID, SetValue, Add, Subtract, Increment, Decrement, Count, Clear, and declaration errors as *graphs.DeclarationError matchable with errors.Is.
  • Chronicle.Go (Release v0.13.0): graphs.Neo4j (the default) and graphs.InMemoryGraph sinks, and chronicle.WithDefaultGraphSinkType.
  • Chronicle.Go (Release v0.13.0): eventsequences.ConstraintIndexUnavailable: an append the Kernel refuses while a unique-constraint index rebuilds is reported as a rejection that stored nothing and can be retried.
  • Chronicle.Go (Release v0.13.0): Key read-model dictionary entries by event content, event context or the causing user, and remove entries with RemoveKey.
  • Chronicle.Go (Release v0.13.0): Set values only once with MapOnce, ContextOnce, ValueOnce and their every/all variants, or once=true in model-bound tags.
  • Chronicle.Go (Release v0.13.0): Map the causing user into read models with CausedBy, CausedByOnce and EveryCausedBy.
  • Chronicle.Go (Release v0.13.0): Insert children at the start with Prepend() or keep them sorted with OrderBy and OrderByDescending, also available as model-bound tags, completing projection dictionary, set-once and child-ordering parity with the C# client (#127)
  • Chronicle (Release v19.152.0): AddCratisChronicleUsingConnectionString registers the client from a named connection string. (part of #5778)
  • Chronicle (Release v19.152.0): The kernel reads storage connection details from a file through ConnectionDetailsFile, and infers the storage type from the connection string at startup. (part of #5778)
  • Chronicle (Release v19.152.0): Clients report their startup state and connect in the background. (part of #5778)
  • Arc (Release v22.184.0): StateAwareEmissionGuard<TState>, the emission-guard counterpart of StateAwareAuthorizationPolicy<TState>. It re-reads the recorded state on each guarded emission and ends the subscription when the caller is no longer entitled. It fails closed: a missing key, a missing instance, a failing read or a failing decision all end the subscription, reported through OnDenied with the same StateDenialReason. (#3766)
  • Arc (Release v22.183.0): IQueryRowNarrowing and the QueryRowNarrowing<TReadModel, TKey> base. A narrowing supplies a predicate over the read model; Arc applies it before sorting, paging and counting, so a store-backed IQueryable filters in the store.
  • Arc (Release v22.183.0): UnsupportedQueryRowNarrowing, thrown when a narrowed query returns a result Arc cannot narrow (such as an observable query), so rows are never returned unnarrowed. (part of #3765)
  • Screenplay (Release v6.14.0): narrow <Policy> on a collection query. The policy is evaluated once per row with the row’s own properties as the artifact; a denied row, or a row with no recorded state, is dropped. authorize still refuses the whole call and composes with narrow. (#1234)
  • Screenplay (Release v6.14.0): ESM v47, selected only by a model that declares narrow; every earlier model keeps its bytes and revision. The reference evaluator applies the narrowing before a then query assertion compares rows, in both the C# and TypeScript compilers.
  • Screenplay (Release v6.13.0): A policy declares typed inputs such as asset AssetId, a read takes its key with by asset, and authorize PlanGrants carries a mapping block such as asset = vesselId. An input that is not mapped is filled from the artifact property of the same name, so existing state policies keep working. Both compilers parse and print it, and the reference evaluator and specifications resolve the key through the mapping. (#1231)
  • Screenplay (Release v6.13.0): ESM v46, selected only by a model that declares an input or a mapping; every earlier model keeps its bytes and revision. The canonical JSON, the published esm-v46 schema, the golden and the documentation describe it.
  • Screenplay (Release v6.12.0): ESM v45. contains over a required text collection or text property and starts with over a text property are admitted in policy state conditions, against a text constant. Both are ordinal and case-sensitive, an absent value never matches, and not composes with them. Only a model that uses one selects v45; every earlier model keeps its bytes and revision. (#1232)
  • Screenplay (Release v6.12.0): The reference evaluator, canonical JSON, published esm-v45 schema, golden and documentation cover the operators, with specifications for membership, prefixes, absence and negation.
  • Chronicle (Release v19.151.0): Added an opt-in command to the Chronicle server, --migrate-encryption-keys, that copies unambiguous legacy Vault encryption keys to the current key layout. It supports --dry-run, verifies the result, is safe to repeat and leaves the legacy keys in place; entries that cannot be migrated safely are reported for operator review (#5746)
  • Chronicle (Release v19.151.0): Added a configurable mode that refuses to start while legacy Vault encryption keys remain; the default stays warn-and-continue (#5746)
  • Chronicle (Release v19.151.0): Added documentation for the key migration, its exit codes and required Vault permissions, and a staging procedure for verifying it before production (#5746)
  • Screenplay (Release v6.11.0): ESM v44. A model with a policy that declares reads and a state condition such as plan.dataQuality == true selects it; every earlier model keeps its bytes and revision. The canonical JSON, the published esm-v44 schema and the golden describe it. (part of #1233)
  • Screenplay (Release v6.11.0): The reference evaluator and specification runner read the given read-model state through the policy. An absent instance denies, and a specification expresses the outcome with given readmodel and then denied.
  • Screenplay (Release v6.10.0): Policies accept reads lines and a state condition such as plan.dataQuality == true or article.author == $identity.id. Both compilers parse and print them, and the syntax tree carries them as StateConditionSyntax. A read that finds nothing denies. (part of #1230)
  • AI (Release v7.150.0): Added Chronicle and Arc configuration skills that cover the important settings, their defaults, and when and how to change them, plus development, production and troubleshooting references (part of #1091)
  • cli (Release v3.126.0): cratis build service install, uninstall and status run a project’s build loop as a user service that starts at sign-in and restarts 30 seconds after it stops: a launchd agent on macOS and a systemd user unit on Linux. install takes the options of cratis build run; the service gets the PATH of the installing shell and no credentials. See cratis build service. (part of Cratis/StudioIssues#1352)
  • AI (Release v7.149.0): The reverse-engineering skill has a process-drift mode: each derived model records a watermark (the target commit or version it describes), and a newer target revision re-derives only the flows the diff touches, producing a model delta and a list of behavior changes. A drift-scope.mjs script maps a target diff onto the model’s flows (part of #1056)
  • Stage (Release v6.2.0): Rendering an ability invocation from a lifecycle is refused with STAGE-LIFECYCLE-010 (part of #1118)
  • AI (Release v7.168.4): The corpus is pinned to Screenplay 6.32.0, and the free screens guidance is compiled against it instead of being shown as excerpts (#1181)
  • AI (Release v7.168.3): Hosts that manage providers, agents, usage or decisions must register an administrators implementation with WithAdministrators<T>(); without one, these operations are denied.
  • AI (Release v7.168.3): Usage, rate-limit and credential recording performed by Cratis.AI itself keeps working for every caller, including during requests from users who are not administrators.
  • Screenplay (Release v6.34.0): The reference evaluator treats a code-provided value as opaque: availability gates that depend on it are treated as available, so specifications of the gated slices still run (part of #1307)
  • Chronicle (Release v19.168.0): Removing, renaming or retyping a property of a registered event type is still rejected with EventTypeSchemaChanged in every event store; breaking changes need a new generation. Chronicle’s own event types are never evolved in place. (#5946)
  • Chronicle.Elixir (Release v3.24.1): Requires grpc 1.0.6 or later.
  • Chronicle (Release v19.167.1): The hosting documentation describes certificate renewal. The password and the encryption certificate are still read at startup.
  • Chronicle (Release v19.167.0): The token cache file and its folder are readable and writable by the current user only, on Windows as well as Unix. The file is protected before the token is written and replaced atomically, and a cache file other users can read is ignored and rewritten. (#5598)
  • Chronicle (Release v19.167.0): A cached token is never kept longer than the configured lifetime, even when the token itself expires later. (#5598)
  • Chronicle (Release v19.167.0): The connection string documentation explains where the token cache lives and that, with SRV discovery, the selected target host receives the client credentials for the token request. (#5598)
  • Stage (Release v6.1.0): The host and rendered applications omit raw event source ids from trace spans by default; opt in with EventSourceIdTracing.Raw or EventSourceIdTracing.Hashed. (#970)
  • Stage (Release v6.0.0): Screenplay to Scene conversion runs through Cratis.Scene.Screenplay behind one entry, StageSceneConversion; Stage keeps the render plan, findings, routes and shipped packages
  • AI (Release v7.167.3): Writing and review skills now check prose around every language tab, treat tab notes and security claims as claims to verify against source, search a series before changing a repeated fact, keep limits through length trims, and bound quick-review findings. (#459)
  • cli (Release v3.139.0): cratis build run --docker picks the builder image for the target: cratis/builder, or cratis/studio-axon-builder with --target axon. It runs the newest version already pulled, or pulls the latest released version when none is. --image with a repository and no tag is resolved the same way.
  • cli (Release v3.139.0): After a command, the CLI tells you when a newer version of a builder image you have is released, and cratis update pulls it, as it does for the Stage image.
  • Chronicle (Release v19.166.1): Document the ownership rules for saved queries and folders in the Workbench: only the owner or an administrator can change or delete them, and sharing with Everyone controls visibility only (#5594)
  • Components (Release v4.42.3): Restructured the chips field, password field, toaster, events view, chat topic list, filter panel and pivot viewer internals into smaller parts for maintainability; behavior is unchanged (part of #506)
  • Components (Release v4.42.2): Restructured the command stepper, components provider, data table core, chips field and canvas internals into smaller parts for maintainability; behavior is unchanged (part of #506)
  • AI (Release v7.165.8): The Claude Code provider’s MCP server, stream event parsing and chat client are restructured into smaller parts with the same behavior, with new specs for retries before initialization, stop reasons on non-text deltas and mixed assistant error content (part of #1080)
  • AI (Release v7.165.7): The Screenplay skills explain that a resolved, language-tagged handler can declare may produce, binds at ESM v35 with handler result contract v2 and returns an ordered selection of its declared events, and that PLAY0800 refuses only handlers with neither unconditional produces nor may produce (#1017)
  • AI (Release v7.165.7): The Screenplay skills cover nested collection sample rows, the hint for a misplaced rule <predicate>, and PLAY0166 as an error for an unresolved qualified from input of a source events capture
  • AI (Release v7.165.7): The Stage rendering skill describes the construct-naming messages of STAGE-ESM-002, STAGE-ESM-014 and STAGE-ESM-015 and that an exact Int64 overflow in a whole-number projection product reports Unsupported (#904)
  • Components (Release v4.42.1): Restructured the schema editor, type cell, column filter menu, chat sidebar and dialog internals into smaller parts for maintainability; behavior is unchanged (part of #506)
  • AI (Release v7.165.3): The new-repository intake rule treats a direct, named issue operation or an accepted scoped policy as enough authority, without an extra confirmation step; creating a repository or having tool access still grants no issue authority (part of #977)
  • AI (Release v7.165.3): The frontend developer agent hands browser checks to the browser operator with the URL, scope, permit and artifact folder, and reports the UI as unverified when no browser operator is available (part of #977)
  • AI (Release v7.165.3): Superseding a decision record is append-only: existing trailers and history stay as written and the new record id applies to new work (#979)
  • AI (Release v7.165.3): The GitHub Actions rule retries a bot push with a merge (git pull --no-rebase) instead of a rebase (#979)
  • AI (Release v7.165.3): Verification discipline separates the local Tier 1 gate from integration coverage, which may defer to CI only where CI enforces it; missing coverage fails closed and a stricter local policy wins (#983)
  • AI (Release v7.165.3): The Stage sandbox guidance documents the semantic engine as the default, with the legacy engine only on explicit request, and a verification check keeps the evaluations in line with the CLI and Stage behavior (#985)
  • AI (Release v7.165.2): The Orleans rule, the Copilot Orleans and framework instructions, and the orleans and cratis-orleans-jobs skills now use the Cratis.Choreography package names and AddCratisChoreography entry point from Cratis/Choreography 2.0.0, and mention the old Cratis.Orleans names only to explain the rename for upgraders (#1193)
  • AI (Release v7.165.2): The NuGet pin list used by the hooks now pins Cratis.Choreography, Cratis.Choreography.Chronicle, Cratis.Choreography.Storage.MongoDB and Cratis.Choreography.Storage.Sql 2.0.0 instead of the Cratis.Orleans packages; run cratis ai update to pick up the hook change (#1193)
  • Arc (Release v23.12.1): Cratis.Chronicle, Cratis.Chronicle.AspNetCore and Cratis.Chronicle.Testing are updated to 19.164.4
  • Arc (Release v23.12.1): Chronicle 19.164.4: The per-reactor “Subscribing reactor” and “Reactor disconnected” log lines are now Debug instead of Information. Failures, timeouts and ungraceful disconnects keep their levels.
  • cli (Release v3.138.0): Internal restructuring of the new, run and extension verify commands to improve maintainability, with no change in behavior. (part of #572)
  • cli (Release v3.137.1): cratis build run --docker runs cratis/builder from Docker Hub by default, at the version of the CLI. Pass --image to run another image.
  • cli (Release v3.137.1): The cratis/builder image is published to Docker Hub automatically for every CLI release.
  • cli (Release v3.137.0): The builder speaks builder protocol versions 1 and 2.
  • Chronicle (Release v19.165.1): “Client disconnected” and “Observer unsubscribed” are logged at Debug instead of Information. A client that disconnects ungracefully still logs its warning.
  • Chronicle (Release v19.165.0): The projection editor recognizes graph declarations and no longer marks them as errors, so Preview and Save stay available.
  • Chronicle (Release v19.164.6): “Observer deactivating”, “Source event store became available” and “Event store subscription is ready to receive events” are logged at Debug instead of Information. Failures and warnings keep their levels.
  • Showrunner (Release v2.16.0): GrantedUsers access mode no longer needs the same-kernel transport, and the host no longer refuses to start with it over Http.
  • Showrunner (Release v2.16.0): The React and JavaScript packages now accept @cratis/arc and @cratis/arc.react 22.185.1 or later, and 23.
  • Showrunner (Release v2.15.0): The Understudy resource is now reconciled, with status conditions, instead of schema only
  • Showrunner (Release v2.15.0): The operator chart grants CronJob and Job rights in managed namespaces and exposes a metrics port
  • Showrunner (Release v2.14.0): Changing vault.mode or vault.managed.tier on a Production that runs is refused, like the database and graph modes, because the keys stay where they are
  • Showrunner (Release v2.14.0): The operator’s Role in each managed namespace also covers ConfigMaps, ServiceAccounts, Roles and RoleBindings (for the Vault helper) and deleting NetworkPolicies (for removed egress rules)
  • AI (Release v7.164.4): Screenplay skills now describe ESM v37 clock operands (today, now, date of ...), application and command calendars, declared context time zones and given time zone as executable in command conditions. The guidance also covers the Screenplay 5.5.0 minimum, where Stage refuses clock constructs per scope, that every/at clock triggers are still not realized, and why Studio refuses the typed-context revisions these constructs produce (#1022)
  • Showrunner (Release v2.13.0): In GrantedUsers mode, Availability answers false for users who were not granted, the feedback button hides itself, and the note commands refuse them with the same message whether they were never granted or revoked.
  • Showrunner (Release v2.13.0): GrantedUsers mode needs the same-kernel transport; the host refuses to start with it over the Http transport.
  • AI (Release v7.164.1): The Screenplay read-surface, projection, specification and toolchain skills explain graph query collect with nested rows, ESM v54 and diagnostics PLAY1144–PLAY1147, and the corpus is pinned to the Screenplay 6.29.1 contract. (#1166)
  • AI (Release v7.164.1): The projection skills explain dictionary entries keyed from event content, set once and children ordering, so declarative projections replace reducers for these cases. (#1072)
  • AI (Release v7.164.1): The Screenplay toolchain and authoring skills explain screenplay export, diff, rename and persisted identities. (#1050)
  • AI (Release v7.164.1): The Screenplay skills explain admitting screens to the executable model with --screens and ESM v42. (#1071)
  • AI (Release v7.164.1): The Screenplay skills explain the OpenAPI and UI contract exports. (#1059)
  • AI (Release v7.164.1): The Screenplay skills explain the published ESM JSON Schemas and the per-slice change summary in diff. (#1051)
  • AI (Release v7.164.1): The Screenplay skills explain storylines and two-way value lineage with trace-lineage direction and screenplay lineage. (#1060)
  • AI (Release v7.164.1): The Screenplay skills explain development users (user ... as <Persona>) and how they relate to personas. (#1042)
  • Chronicle (Release v19.164.4): The per-reactor “Subscribing reactor” and “Reactor disconnected” log lines are now Debug instead of Information. Failures, timeouts and ungraceful disconnects keep their levels.
  • AI (Release v7.163.0): The Pi cratis-mcp extension no longer registers every selected MCP server’s tools at session start. The agent starts a server on demand with the new cratis_enable_mcp tool, and its tools are callable from the next step. Set mcpServers.<id>.eager to true in .cratis/ai.json to register a server’s tools at start-up as before. (#814)
  • Screenplay (Release v6.30.0): VS Code offers only the C#-backed repairs the configured Screenplay server advertises. With an older server, the extension keeps offering the repairs that server supports instead of refusing to connect (part of #341)
  • AI (Release v7.161.0): A model without the Vision capability, a provider client that cannot send images, or an unsupported image type refuses the completion with a clear reason instead of ignoring the image; a provider pool skips such a member and tries the next (#1148)
  • AI (Release v7.160.4): A new Screenplay release no longer turns the AI Publish run red: the scheduled Screenplay contract comparison reports drift as a warning, a run summary and the tracking issue, while releases keep checking the pinned contract (#1103)
  • AI (Release v7.160.4): Bumping the pinned Screenplay contract is one command, yarn workspace @cratis/ai-verification run bump <version>, which updates the contract, its version file and the compatibility table together; the procedure is in https://github.com/Cratis/AI/blob/main/Documentation/compatibility.md
  • AI (Release v7.160.4): The Screenplay MCP tool reference no longer states a fixed tool count, and the preferred-syntax reference lists every style diagnostic in the pinned contract, including PLAY0955
  • AI (Release v7.160.2): The Screenplay projection, read-surface and specification skills explain how to read a graph in queries and specifications, including then query steps and given clock to fix $eventContext.occurred. (#1039)
  • AI (Release v7.160.2): The Screenplay projection skill shows foreach in graph projection handlers and the diagnostics it reports. (#1040)
  • AI (Release v7.160.2): The Screenplay skills explain screen visuals, placing one slice in several places and issue notes on a model. (#1063)
  • AI (Release v7.160.2): The Screenplay skills explain validate file, occurred in scoped projections, host execution of rule, validation and reducer bodies, and admissible compilation. (#953)
  • AI (Release v7.160.2): The Screenplay projection, toolchain and model-review skills explain the PLAY1142 warning for secret concepts copied into read models and how to fix it, and the corpus is pinned to the Screenplay 6.28.0 contract. (#1067)
  • AI (Release v7.160.1): The Screenplay read-surface skill explains how for item resolves on a screen with several data declarations: it acts on the one collection a table in scope shows. (#1117)
  • AI (Release v7.160.1): The Screenplay specification skills show how to write given, when append and for case specifications for events that no single command produces, with the identity taken from the read-model projections that consume them. (#1110)
  • AI (Release v7.160.1): The Screenplay skills explain how reaction bodies run through a host-supplied body execution provider, including which reactions qualify and what a body may return. (#959)
  • AI (Release v7.160.1): The Screenplay toolchain skill describes the opt-in unknown-preserving reader for consumers that keep unknown model additions without executing them, its admission range and its refusals. Requires Screenplay 4.256.0. (#957)
  • AI (Release v7.160.1): The Screenplay skills explain that read-model property declaration order is not preserved by default and how a C# host can opt in when binding a model. (#966)
  • Stage (Release v5.28.0): Cratis Arc moves to 23.8.0, Chronicle to 19.162.0 and Screenplay to 6.29.0.
  • Stage (Release v5.28.0): The renderer still refuses graph queries with STAGE-ESM-068; the message now says when the query collects.
  • cli (Release v3.136.0): --studio accepts the builder address https://<studio host>/builders/connect/<organization> and takes the organization from it, instead of failing with 405 MethodNotAllowed.
  • cli (Release v3.136.0): The documented examples now use the hosted Studio’s address rather than https://cratis.studio.
  • AI (Release v7.158.2): The cratis-documentation-writing skill puts its completion checklist early and moves detailed writing guidance into a reference file with a pointer to when to read it (#973)
  • AI (Release v7.158.2): The cratis-writing-voice-and-cadence skill keeps its stop conditions and core rules in the skill body and moves the longer voice guidance into a reference file (#973)
  • Showrunner (Release v2.12.0): Showrunner now uses Chronicle 19.164.0, which hosts the federation client the page relies on.
  • AI (Release v7.158.1): Screenplay skill bodies are reorganized into focused references so each skill stays within its size budget
  • Chronicle.Mcp (Release v2.3.0): Every tool result except get_server_version is wrapped in an untrustedData envelope (source, tool, notice, content). Hosts reading structured results must read untrustedData.content instead of the old top-level payload; the original JSON value is unchanged there.
  • Chronicle.Mcp (Release v2.3.0): Each text block starts with a notice and is enclosed in CHRONICLE_UNTRUSTED_DATA delimiters carrying a random per-call ID. The body is JSON-encoded so stored text cannot close the block; non-JSON text, including error messages, becomes a JSON string literal.
  • Showrunner (Release v2.11.0): The message of an announcement is optional in authoring, validation and rendering
  • Showrunner (Release v2.11.0): MarqueeLabels has two new labels, expand and collapse; code that builds a complete MarqueeLabels object itself must add them
  • AI (Release v7.158.0): WorkerLaunchOutcome has a new ProviderAccessDenied value, and WorkerJob has a Provider property that names the provider whose credential the worker receives (#998)
  • AI (Release v7.158.0): Providers configured before this release stay open to everyone until a team member selection is set (#998)
  • Arc (Release v23.8.0): Cratis.Chronicle packages move to 19.162.0.
  • Chronicle (Release v19.161.0): Event type registration keeps migration validation and schema comparison in dedicated types, with unchanged behavior (#5889)
  • AuthProxy (Release v2.65.0): Bearer authentication fails closed when grant evidence is missing or inconsistent: DPoP-bound tokens, delegated or actor tokens, non-person subjects and client-credentials grants never receive an envelope, and nothing falls back to v1 or unsigned identity. Personal access tokens continue to be forwarded without an envelope (#344)
  • AuthProxy (Release v2.65.0): Cached introspection answers keep their original expiry, and the envelope’s signing deadline never outlives it (#344)
  • Showrunner (Release v2.10.1): StartedTour.ByMe is an observable query instead of a snapshot one, so the generated ByMe.use() hook in @cratis/showrunner.cue returns the result and a sorting setter, and no longer a perform-query function. useCueTours and useTourNudge in @cratis/showrunner.cue.react are unchanged for callers.
  • Chronicle (Release v19.159.0): Projections resolve keys without array indexers and copy list state with less work per event. (part of #5824)
  • Arc (Release v23.7.0): Cratis.Arc.Availability requires Cratis.Choreography 2.9.0 or later.
  • Showrunner (Release v2.9.0): Cratis.Choreography updated to 2.9.0.
  • Showrunner (Release v2.8.0): AudienceGranted, AudienceWithdrawn and AudienceDecisionReceived are generation 2 and carry ClientId (and Kind on the decisions). Generation 1 is kept and migrated, so an event published or stored before reads as the product-wide System holder
  • Showrunner (Release v2.8.0): ProductGuestList, HeldAudience and UndeclaredAudienceGrant carry ClientId and Kind
  • Showrunner (Release v2.8.0): Update products before granting an audience to a named system: a product that has not been updated ignores those decisions and never widens them to every system
  • AI (Release v7.157.0): Worker jobs mount only the run’s own memory key and the repositories it is authorized for, instead of the whole repository cache volume, on both Docker and Kubernetes; cache paths are verified on the host before launch (#1152)
  • AI (Release v7.157.0): The secret and shell-write guards admit only reviewed command shapes and refuse everything else, including leading environment assignments outside a short list of display settings (#1076)
  • Arc (Release v23.5.1): Authenticated callers without an identifying claim (name identifier, subject or name) can no longer manage subscriptions on server-sent-event observable query connections
  • Chronicle (Release v19.157.0): Rebuilding constraint indexes reads only the event types that constraint definitions use, so stored events of other types, including retired types without a registered schema, no longer stop the rebuild. (part of #5880)
  • Chronicle (Release v19.157.0): Event type registration checks report a failing entry instead of aborting the whole check when one schema cannot be processed. (part of #5877)
  • Stage (Release v5.27.0): Rendered applications reference Cratis.Choreography 2.8.0.
  • Showrunner (Release v2.7.0): The undeclared grants report uses the audiences a product reported for its primary environment (GuestListAuthoringOptions.PrimaryEnvironment, default Production) before DeclaredAudiences, which stays as the fallback.
  • Showrunner (Release v2.7.0): Cratis.Choreography is updated to 2.8.0.
  • Stage (Release v5.26.0): Generated applications pin NuGet Arc 23.5.0 and Showrunner guest list 2.6.0; the npm Arc packages stay on 22.184.0, the line the Showrunner notes packages accept.
  • Stage (Release v5.26.0): The generated backend scaffold gains an availability registration seam that does nothing when the model declares no availability.
  • Stage (Release v5.25.0): Updated Cratis.Screenplay to 6.27.0, and the conformance matrix, the framework name catalog and the pinned render plan fingerprints with it
  • Screenplay (Release v6.27.0): Facts given before a specification’s given clock take that instant as their occurrence time, so projections that read occurred run over them
  • Screenplay (Release v6.27.0): Facts a specification gives or produces without a caller are attributed to the specification audit identity
  • Stage (Release v5.24.0): Stage now builds against Screenplay 6.26.0 and Choreography 2.7.0, and rendered applications pin Choreography 2.7.0. The scaffold adds GeneratedProvideRegistration.cs and registers it from Program.cs.
  • AI (Release v7.154.0): The slice design, read surface, command surface, UI composition, model review, toolchain and streams skills point to the availability skill at the decisions where it matters
  • AI (Release v7.154.0): The toolchain diagnostics fix guide, cheat sheet and language admission table cover PLAY1119-PLAY1141 and ESM v53
  • AI (Release v7.154.0): The Screenplay contract pin moves to 6.26.0
  • Arc (Release v23.5.0): Screenplay generation now builds on Cratis.Screenplay 6.26.0 and generation 0.21.2.
  • Screenplay (Release v6.26.0): provide is admitted when its source is a literal, the host or a query; provide from a file or code block stays a preview.
  • Screenplay (Release v6.25.0): Provided names and $context.audiences no longer raise PLAY0153 as unknown context paths
  • Screenplay (Release v6.25.0): A model that uses provide in executable form reports PLAY0268 until a later release admits it; it is a preview construct
  • Arc (Release v23.3.0): Raises SharpCompress to 0.50.8, which Cratis.Choreography 2.7.0 requires.
  • AI (Release v7.153.9): The screen composition and extension package skills now teach how a screen’s on <signal> interaction runs: a handled signal is a Scene signal trigger bound by Stage, signal.<value> reads what the component raised, and it never fires an application trigger of the same name. They link the Stage and Scene pages by absolute URL. (part of #1121)
  • Scene (Release v5.4.1): The task dialog a toolbar slice button opens no longer shows the slice’s kind and model name (State Change · PlaceOrder) under its title. The person sees the button’s title and the fields; the slice stays on the dialog’s data-scene-slice-dialog attribute.
  • Stage (Release v5.23.0): Stage now builds on Scene 5.4.0 for every Scene package, npm and NuGet, and on @cratis/components 4.40.1, which Scene 5.4.0 requires. Generated applications pin the new versions, so their plans have new hashes.
  • Stage (Release v5.23.0): The Notifier sample screen handles its dismissed signal and the extensions documentation no longer describes signal binding as pending.
  • Stage (Release v5.22.0): Stage builds against Screenplay 6.24.0, which the extension screens need. The renderer refuses the new ability invocation, workflow compute and state entry body members with STAGE-ESM-016 until they run, and the conformance matrix tracks the v51 and v52 vectors. (part of #1118)
  • Stage (Release v5.22.0): A model is compiled against the extension lock beside the model, not beside the directory Stage was started from. Starting Stage from another directory no longer reports Extension '...' is not in screenplay.lock.
  • Stage (Release v5.22.0): A workflow action that invokes an ability is refused with STAGE-LIFECYCLE-010 instead of failing while the host admits the model. Running ability invocations from reactions, workflow actions and state entries is not done yet. (part of #1118)
  • AuthProxy (Release v2.64.1): A valid DPoP proof that lacks the required scope now gets HTTP 403 insufficient_scope without reserving its proof identifier. Successful authorization still requires an atomic replay reservation. (#302)
  • AuthProxy (Release v2.64.1): The replay-store health check now gives up after a bounded wait and fails closed, rejecting the request, instead of holding requests while Redis is unresponsive. (#302)
  • Chronicle (Release v19.156.4): The .NET client logs reactor registration, disconnection and reconnection at Information level, so a reactor that stops after a kernel restart shows up in the application logs (part of #5855)
  • Chronicle (Release v19.156.4): Chronicle now uses Cratis Choreography 2.6.1, which keeps job-step state intact across restarts with SQL storage (part of #5855)
  • Chronicle (Release v19.156.4): CI now posts a status comment when the nightly full test matrix on main goes red or recovers, and records the failed specs from a failing run so flaky lanes are visible without digging through logs (#5849)
  • AuthProxy (Release v2.62.1): Updated the shared Cratis AI guidance used for AI-assisted development in this repository
  • Showrunner (Release v2.0.0): Renamed the Usher contract event IssueReopened to IssueReopenedByReporter. Consumers must update their references to the new name.
  • Showrunner (Release v2.0.0): Renamed the Usher contract event WorkStarted to WorkStartedOnIssue. Consumers must update their references to the new name.
  • AI (Release v7.153.8): DockerWorkerRuntime starts the worker container first and delivers secrets through an exec into a root-owned tmpfs, then publishes a readiness marker that the worker entrypoint waits for before starting the agent. (#1047)
  • AI (Release v7.153.8): Docker worker image references are preserved exactly as configured instead of being rewritten. (part of #1047)
  • Stage (Release v5.21.0): Stage now depends on version 5.3.0 of every Scene package, up from 5.1.0, and on @cratis/scene.extensions 5.3.0. Scene 5.3.1 is not used until @cratis/scene.extensions 5.3.1 is published.
  • Stage (Release v5.21.0): A screen’s on <signal> interactions are not yet bound to a raised signal, because Scene 5.3.0 has no trigger kind for one. Raised signals reach StageExtensionServicesProvider’s onSignal and a stage-extension-signal event on the component’s element.
  • Arc.Elixir (Release v1.1.0): Builds that add the analyzer can report new warnings after an upgrade that adds a rule. ARCE0002 and ARCE0005 default to errors; set a rule to :warning or :off under config :cratis_arc, :analyzer while you fix the findings.
  • AI (Release v7.153.7): The environments skill covers extension settings, named secrets, activation and cratis config --requires.
  • AI (Release v7.153.7): The toolchain skill explains the lock and restore diagnostics.
  • AI (Release v7.153.7): The pinned Screenplay contract and compatibility table move to 6.24.0.
  • Templates (Release v1.9.0): Cratis.Templates.Extensions is packed and published with the other template packages in each release. It is not part of Cratis.Templates.
  • cli (Release v3.134.0): cratis config set always stores a key under secrets. as a secret, with or without --secret, and refuses a value given as an argument.
  • cli (Release v3.134.0): cratis config --missing also lists the named secrets and extension settings a model needs.
  • cli (Release v3.134.0): A secret passed to the Stage goes in a file only your user can read, passed with --env-file and deleted when the run ends; a secret value that spans several lines, or a registry host with a port, is refused by name.
  • cli (Release v3.134.0): cratis run on a single .play file refuses a model that has extensions: run the folder that holds the model and the lock.
  • Stage.Axon (Release v0.11.1): Stage.Axon is built with the latest C# language version instead of C# 14, in line with the other Cratis repositories on .NET 11. (#94)
  • Screenplay (Release v6.24.0): A component placed as <System>.<Component> no longer needs the system’s package in a ui profile: PLAY0632 is not reported for a system that names an extension.
  • Screenplay (Release v6.24.0): The vendored Invoicing extension contract changed (its platform line), so its digest in screenplay.lock and its folder under extensions/ changed.
  • Stage (Release v5.19.0): Receiving an inbound webhook no longer waits for a cold start: it is stored and acknowledged, and the backend starts when the stored request is delivered. IExtensionEndpoints gains Knows, which implementations that only resolve endpoints get for free.
  • Stage (Release v5.19.0): IExtensionPackages gains Systems, which lists the systems of the model that name an extension. A custom implementation must add it.
  • Stage.Axon (Release v0.11.0): Stage.Axon moves to Stage 5.11.0 / Screenplay 6.22.0 and admits semantic versions through V50; every new SDK member is classified (#90)
  • Stage.Axon (Release v0.11.0): Screens, systems, agents, projection ordering and set-once, the new Contains/StartsWith conditions and caller-identity operands are reported as unsupported (warning, refused in strict mode) instead of being silently ignored (#90)
  • Arc (Release v23.1.0): The Screenplay generator now depends on Cratis.Screenplay 6.23.0 (was 6.0.0). Generated models containing operations still bind to PLAY0268 until Screenplay admits operations (Cratis/Screenplay#301) and ability invocations from operations (Cratis/Screenplay#1252); the generator accepts those messages as known admission limits.
  • Chronicle (Release v19.156.3): The event store list (and its live view) shows only the event stores the caller is entitled to read when store entitlements are enforced; administrators and in-process callers still see every store (#5836)
  • Chronicle (Release v19.156.3): Observers match events against large subscribed event-type sets with a set lookup, and projection saves skip future-save work when nothing is pending (#5822)
  • Chronicle (Release v19.156.3): Pull request CI builds the spec binaries without analyzers and runs the analyzer build as a parallel required job, so the specs start sooner (#5837)
  • Chronicle (Release v19.156.3): The SQL storage specs run each specification’s setup once per class instead of once per fact, which shortens the SQL spec runs in pull request CI (#5832)
  • Stage (Release v5.18.0): Stage requires Cratis.Screenplay 6.22.0, and the conformance matrix records its new ESM vector V50.
  • Stage (Release v5.18.0): /stage/extensions is a tooling route: a published application does not serve it.
  • Scene (Release v5.3.1): @cratis/scene.components and @cratis/scene.blueprint.default now accept Arc 23 (@cratis/arc and @cratis/arc.react below 24) and require @cratis/components 4.40.1 or later, the first Components release that accepts Arc 23 (#310)
  • cli (Release v3.131.0): Chronicle client and integration image move to 19.156, with System event store commands run as administrator and refusals showing the administrator-login hint (#595)
  • Screenplay (Release v6.23.0): Compute nodes, approval ... via, state entry bodies, operation-phase invocations and $trigger values are not executable yet: binding reports PLAY0268 naming issue 1252.
  • Components (Release v4.40.1): @cratis/arc and @cratis/arc.react peer ranges now accept Arc 23 (>=20.3.1 <24), so applications on Arc 23 install Components without peer dependency conflicts (#509)
  • cli (Release v3.130.0): The CLI bundles Screenplay 6.22.0, which adds the extension contracts and the lock.
  • Screenplay (Release v6.22.0): A system that names an extension can no longer declare abilities of its own (PLAY1106); the contract is the only source of its abilities.
  • Screenplay (Release v6.22.0): Compiling a model whose system names an extension now needs screenplay.lock and the restored contract; run screenplay restore once and commit the lock (PLAY1107, PLAY1108).
  • Stage (Release v5.17.1): Rendered C# places preprocessor directives at column 0, so generated applications pass dotnet format whitespace --verify-no-changes without a format pass (#1084)
  • Stage (Release v5.17.1): Restructured specification and run admission for maintainability, with no behavior change (part of #1051)
  • cli (Release v3.129.0): Chronicle applications and users commands (and the Workbench lists) work with an administrator login and show a cratis chronicle login hint when Chronicle refuses them (#557)
  • cli (Release v3.129.0): Chronicle commands now exit with the authentication error code, instead of the server error code, when the server rejects the credentials or the stored login token, and say whether to check the credentials or run cratis chronicle login again
  • AuthProxy (Release v2.61.0): Requests to a bearer route over plain HTTP are refused before any credential is read and are never forwarded. LocalDevelopment and loopback requests are exempt. Deployments that terminate TLS in front of AuthProxy must trust that proxy (#323).
  • AuthProxy (Release v2.61.0): Bearer routes forward X-Forwarded-Proto with the effective scheme, replacing any client-supplied value (#324).
  • Arc (Release v23.0.0): Read protection is on by default for commands that inject read models; set <CratisReadProtection>Off</CratisReadProtection> or adopt On through Measure. See the upgrade guide (#3255)
  • Arc (Release v23.0.0): Strict key coverage is the default: ProtectedReadModelKeyOptions.Strict is true, and ReadProtection:RequireGeneratedMetadata is true unless set to false on a runtime with dynamic code support. Enable the source generator or register key accessors, or opt out explicitly. See the upgrade guide (#3393)
  • Arc (Release v23.0.0): The MCP endpoint is gated by default after routing when no selection is set, and McpRequiresGatedEndpoints is removed. See the MCP upgrade guide (#3777)
  • Arc (Release v23.0.0): MapCratisArcMcp() is now MapArcMcp() with an obsolete forwarder, string ExposeQuery is replaced by ExposeQuery<TReadModel>, and McpToolCeiling is now McpToolCatalog with no forwarder. See the MCP upgrade guide (#3775)
  • Arc (Release v23.0.0): The MCP authorization vectors are pinned to version 2.0.0
  • cli (Release v3.128.1): The CLI uses Cratis.Fundamentals 7.34.0. (#591)
  • Stage (Release v5.16.0): Reactions started by a raised trigger run as the actor extension:<System>, the extension that raised it, instead of the anonymous system actor.
  • Stage (Release v5.16.0): POST requests to an extension endpoint are answered 202 with an empty body, not with the extension’s answer. GET, HEAD and OPTIONS are still answered with what the extension answers.
  • Stage (Release v5.16.0): A path an extension does not declare is rejected at delivery, rather than answered 404, until the extension has run once.
  • Stage.Axon (Release v0.10.0): Cratis.Stage.Rendering.Axon targets net10.0 and net11.0; building the repository requires the .NET 11 SDK (11.0.100 or a later feature band, no previews) (#87)
  • Screenplay (Release v6.21.0): Renaming a secret updates its declaration and every from secret mapping.
  • Arc.TypeScript (Release v1.0.1): Simplified the PostgreSQL observation manager and the proxy generator’s source type resolver for maintainability, with new characterization specs and no behavior or public API change (part of #206)
  • Stage.Axon (Release v0.9.0): Stage.Axon now builds against Cratis.Stage.Contracts 5.0.0 and Cratis.Screenplay 6.0.0, with the vendored corpus migrated to Screenplay 6 syntax (#89)
  • Stage.Axon (Release v0.9.0): The renderer refuses Screenplay 6 constructs it cannot render (state machines, workflows, graph, clock and calendar operands, one-of, possible events, date-only operands, application time zone and context members) with STAGE-AXON-UNSUPPORTED-SEMANTICS: a warning by default, an error in strict mode (#89)
  • Stage.Axon (Release v0.9.0): Generated TypeScript client files now carry the generated-file header, which Stage 5 owns (#89)
  • Stage (Release v5.15.0): A backend answers the invocations of its own system without the persona or pol
  • Stage (Release v5.14.0): Stage takes Chronicle 19.155.1, which is the first release with set-once, Cratis.Fundamentals 7.34.0 and Cratis.Choreography 2.3.1. Generated applications pin the new versions.
  • Stage (Release v5.14.0): The ESM feature matrix lists versions 43 to 49 as audited.
  • AI (Release v7.153.6): Workflow, state machine and specification guidance writes invokes and starts instead of the deprecated sends, entering send and entering start.
  • AI (Release v7.153.6): The pinned Screenplay contract and compatibility table move to 6.20.1.
  • Chronicle (Release v19.156.1): Restructured Vault key-store migration and secret stores into smaller units with no behavior change (#5768)
  • Chronicle (Release v19.156.1): Simplified mutation validation and the SQL mutation registry with no behavior change (#5664)
  • Stage (Release v5.13.0): A workflow action that invokes a command now leaves through refused when the command was handed on and rejected, and through failed only when the invocation itself broke. A refusal that no outlet routes still fails the node. The rendered action performers behave the same way. (part of #1251)
  • Stage (Release v5.13.0): Upgraded to Cratis.Choreography 2.5.0, Cratis.Chronicle 19.148.0 (the version Choreography 2.5.0 requires) and Cratis.Screenplay 6.19.0.
  • Stage (Release v5.13.0): The sandbox host no longer registers a no-op Chronicle telemetry callback, because Chronicle now binds its telemetry configuration itself.
  • Stage (Release v5.13.0): A once ability is refused while the host keeps its grain storage in memory, because a restart would lose the record that stops a repeat. Set Stage:Orleans:Storage to MongoDB, or set Stage:Invocations:AllowVolatileOnce to true in a sandbox.
  • Screenplay (Release v6.20.1): Builds with the latest C# language version and suggests collection-expression and labeled break/continue forms in the IDE; Screenplay.Conformance still compiles with C# 12 because its sources ship to consumers. (#1258)
  • Screenplay (Release v6.20.1): Simplified the workspace timeline repair and content-proof code without changing its behavior, and pinned guarded-action diagnostic order and timeline repair outcomes with new specifications. (part of #1238)
  • Screenplay (Release v6.20.1): The Screenplay benchmarks executable targets .NET 11 only. (#1259)
  • Screenplay (Release v6.20.0): A system that declares an ability now binds; operations and systems without abilities still report PLAY0268.
  • Prompter (Release v0.14.22): Internal refactors of Discord answer splitting, forum answering, evaluation console output and groundedness scoring, with no change in behavior. (part of #151)
  • Chronicle (Release v19.156.0): The client subscription keeper no longer calls every connected reactor and reducer every 2 seconds. It checks subscriptions when a silo leaves the cluster, plus a jittered safety net, which cuts its grain calls on an idle kernel about twentyfold. The restore bounds for each kind of lost subscription are documented (#5816)
  • Chronicle (Release v19.156.0): Observer metric instruments are created the first time an observer records them, and the instruments of a scope share their tags, which saves about 3 KiB for each observer activation that records no metrics. Metric names, units and tags are unchanged (#5815)
  • Chronicle (Release v19.156.0): The container profile guidance now follows the measurements: keep the image’s default Server GC with DATAS, use Workstation GC only when memory rather than CPU limits a container with several CPUs, and do not turn DATAS off
  • Prompter (Release v0.14.21): Internal refactors of section merging, issue events, endpoints, Discord answers and hand-offs, README ingestion, task chat policy, retrieval passages, evaluation output and deployment definitions, with no change in behavior. (part of #151)
  • Templates (Release v1.8.5): Projects generated from the Cratis, Cratis Aspire, Chronicle console and Chronicle web templates now compile with the latest C# language version for the SDK in use
  • Screenplay (Release v6.19.0): Write action <Node> invokes <Command>, entering invokes <Command>, entering starts <Workflow> and then invokes <Command>. The old sends, entering send, entering start and then sends forms still compile but raise the deprecation warning PLAY0397, with a typed repair that migrates them. Printing a document writes the new forms.
  • Screenplay (Release v6.19.0): The C# and TypeScript compilers, the reference evaluator, Monaco completions and hover, the VS Code grammar, the samples and the documentation use the new forms. ESM bytes do not change for the verb.
  • cli (Release v3.128.0): New Cratis applications rendered with cratis render target .NET 11; existing applications keep their recorded profile and render unchanged (#579)
  • cli (Release v3.128.0): Rendering uses Stage 5.11.0 and Screenplay 6.18.0 (#579)
  • cli (Release v3.128.0): cratis render admits the Screenplay model versions Stage 5.11.0 supports, including the v34 models Screenplay 6 produces (#579)
  • Stage (Release v5.12.0): Generated shared policy runtime files now contain the identifier helper, so their bytes change for every application that has policies.
  • Screenplay.Generation (Release v0.21.2): Ordinal-compared sets and dictionaries and empty working lists in generation and .NET source placement use C# 15 collection expressions (#95)
  • Screenplay.CritterStack (Release v0.27.2): Marten projection discovery builds its symbol set with a C# 15 collection expression argument (#111)
  • AI (Release v7.153.5): Use the C# field keyword and collection expressions in Cratis.AI internals; no behavior or API change (#1135)
  • Prompter (Release v0.14.20): Internal refactors of markdown chunking, admission, usage pricing, documentation metadata and mentions handling, with no change in behavior. (part of #151)
  • Choreography (Release v2.4.2): Lookup sets, the grain contract manifest and the ForEach branch list are built with C# 15 collection expression arguments, and the branch list is pre-sized to the item count (#209)
  • cli (Release v3.127.1): Internal collections and the workbench refresh loop now use C# 15 collection expression arguments and System.Threading.Lock, with no change in behavior (#584)
  • Synopsis (Release v1.2.3): Restructured the C#, TypeScript, Gherkin and Screenplay specification parsers, the path classifier and the synopsis command-line entry point into smaller, focused types. Discovery results, generated reports, command-line output and exit codes are unchanged. (#28)
  • Chronicle (Release v19.155.1): Collection-expression and related modern C# simplifications are now reported as suggestions instead of being silenced, and kernel hot paths use collection expressions, Lock and single enumeration (#5811)
  • Chronicle (Release v19.155.1): Simplified projection property mapping, event value resolution, future resolution and SQL JSON column handling internals (part of #5767)
  • Chronicle (Release v19.155.1): Restructured observer fast-forward, webhook delivery, projection event context, read model serialization, client artifact discovery, read model scenarios, OAuth client and certificate loading into smaller units with no behavior change (part of #5767)
  • Chronicle (Release v19.155.1): Restructured constraint-index replay, event-sequence constraint-index handling and unique-constraint storage into smaller units with no behavior change (part of #5031)
  • Chronicle.Go (Release v0.15.0): Reactor and reducer observation streams now reconnect with a jittered wait that grows while a stream keeps ending without having worked (2 seconds doubling up to a minute, starting over once a stream delivered or stayed open for three minutes), instead of retrying on a fixed interval, so clients no longer return as one herd during a kernel rollout. The defaults match the .NET client (part of Cratis/Chronicle#5817)
  • Chronicle.Go (Release v0.15.0): When the kernel no longer knows the client’s session, for example after a kernel restart, the client drops the session once and reconnects with a new connection id, and its reactors and reducers register again, instead of retrying the stream against the lost session. Reports about an earlier session are ignored, and session reconnects also back off with jitter (part of Cratis/Chronicle#5817)
  • Chronicle.Go (Release v0.15.0): Errors thrown by your own reactor or reducer handlers no longer count as a lost stream or session
  • Chronicle.Elixir (Release v3.23.0): Reactor and reducer observation streams now reconnect with a jittered wait that grows while a stream keeps ending without having worked (2 seconds doubling up to a minute, starting over once a stream delivered or stayed open for three minutes), instead of retrying on a fixed interval, so clients no longer return as one herd during a kernel rollout. The defaults match the .NET client (part of Cratis/Chronicle#5817)
  • Chronicle.Elixir (Release v3.23.0): When the kernel no longer knows the client’s session, for example after a kernel restart, the client drops the session once and reconnects with a new connection id, and its reactors and reducers register again, instead of retrying the stream against the lost session. Reports about an earlier session are ignored, and session reconnects also back off with jitter (part of Cratis/Chronicle#5817)
  • Chronicle.Elixir (Release v3.23.0): Errors thrown by your own reactor or reducer handlers no longer count as a lost stream or session
  • Chronicle.TypeScript (Release v6.63.0): Reactor and reducer observation streams now reconnect with a jittered wait that grows while a stream keeps ending without having worked (2 seconds doubling up to a minute, starting over once a stream delivered or stayed open for three minutes), instead of retrying on a fixed interval, so clients no longer return as one herd during a kernel rollout. The defaults match the .NET client (part of Cratis/Chronicle#5817)
  • Chronicle.TypeScript (Release v6.63.0): When the kernel no longer knows the client’s session, for example after a kernel restart, the client drops the session once and reconnects with a new connection id, and its reactors and reducers register again, instead of retrying the stream against the lost session. Reports about an earlier session are ignored, and session reconnects also back off with jitter (part of Cratis/Chronicle#5817)
  • Chronicle.TypeScript (Release v6.63.0): Errors thrown by your own reactor or reducer handlers no longer count as a lost stream or session
  • Chronicle.Kotlin (Release v7.10.0): Reactor and reducer observation streams now reconnect with a jittered wait that grows while a stream keeps ending without having worked (2 seconds doubling up to a minute, starting over once a stream delivered or stayed open for three minutes), instead of retrying on a fixed interval, so clients no longer return as one herd during a kernel rollout. The defaults match the .NET client (part of Cratis/Chronicle#5817)
  • Chronicle.Kotlin (Release v7.10.0): When the kernel no longer knows the client’s session, for example after a kernel restart, the client drops the session once and reconnects with a new connection id, and its reactors and reducers register again, instead of retrying the stream against the lost session. Reports about an earlier session are ignored, and session reconnects also back off with jitter (part of Cratis/Chronicle#5817)
  • Chronicle.Kotlin (Release v7.10.0): Errors thrown by your own reactor or reducer handlers no longer count as a lost stream or session
  • Synopsis (Release v1.2.2): The C# specification parser uses C# 15 collection expression arguments for its case-insensitive lookup sets and reuses one empty attribute set instead of allocating one per scenario (#33)
  • Architecture (Release v1.0.4): The analyzers are built with the .NET 11 SDK, and the unused-interface rule uses C# 15 collection expression arguments for its symbol sets (#55)
  • AI (Release v7.153.4): Rules, agents, skills and the shipped quality gate now name -p:CratisProxiesSkip=true (Arc 22.185.1 or later) as the way to skip TypeScript proxy generation. Command lines that run against any Arc version pass it together with the empty -p:CratisProxiesOutputPath=, which still turns the generator off on older Arc versions. Run cratis ai update to pick up the new quality gate (#1132)
  • AI (Release v7.153.4): The cratis-arc-configuration evaluation recognizes DisableProxyGenerator as Arc’s alias for CratisProxiesSkip (#1132)
  • Arc (Release v22.186.0): Refactored internal command, query, proxy-generation and authorization code for maintainability with no behavior change. (part of #3767)
  • Arc (Release v22.186.0): Updated the specs to Cratis.Specifications 5.3.0. (#3795)
  • Arc (Release v22.186.0): Reading query string arguments no longer allocates a new set of reserved keys on every request. (#3798)
  • Showrunner (Release v1.21.3): Updated Cratis Arc to 22.185.1, Cratis Fundamentals to 7.34.0 and Cratis Chronicle to 19.155.0, including the @cratis/arc, @cratis/arc.react and @cratis/fundamentals frontend packages.
  • Showrunner (Release v1.21.3): Builds that do not need TypeScript proxies now skip proxy generation entirely, so only the frontend build generates proxies and checks them for drift.
  • Stage (Release v5.9.0): Stage targets .NET 11 as well as .NET 10: the packages ship both, and the Stage Host and SpecRunner images run on .NET 11 (#1047)
  • Stage (Release v5.9.0): Stage packages embed their Screenplay documents again.
  • Stage (Release v5.9.0): Stage builds on Screenplay 6.18.0.
  • Stage (Release v5.9.0): Documentation page descriptions are shorter, so search results show them in full.
  • cli (Release v3.127.0): The cratis tool now runs on .NET 11, and the published Cratis.Environments library targets .NET 10 and .NET 11. (#570)
  • cli (Release v3.127.0): cratis run lets Ante trust the identity that AuthProxy forwards, and keeps Ante reachable only through AuthProxy. (#571)
  • Chronicle (Release v19.155.0): The Chronicle Kernel server and its Docker images run on .NET 11 (part of #5763)
  • AI (Release v7.153.3): Pull request and verify CI builds no longer generate Arc TypeScript proxies, and the proxy drift gate is removed. The npm release build still regenerates them, and the docs say how to refresh the committed proxies locally with dotnet build Source/Cratis.AI/Cratis.AI.csproj. (#1130)
  • AI (Release v7.153.3): The C# rule now covers the .NET 11 SDK analyzers IDE0370, IDE0001 and IDE0002: fix the findings, keep warning severity, and the narrow multi-target exception for IDE0370. Run cratis ai update to pick it up. (#1129)
  • Eventmodelers-Build-Kit-CSharp (Release v0.1.1): The starter application and test projects use the latest C# version. (#41)
  • Eventmodelers-Build-Kit-CSharp (Release v0.1.1): The repository pins the .NET SDK to 11.0.100, matching the generated projects. (part of #41)
  • Arc (Release v22.185.0): Builds with the .NET 11 GA SDK and Microsoft.Extensions 11.0.0 packages on net11.0; libraries keep net10.0 support.
  • Arc (Release v22.185.0): Updated Cratis.Fundamentals to 7.34.0.
  • Arc (Release v22.185.0): The net11.0 target keeps the Entity Framework Core stack on 10.0.x until the PostgreSQL provider for EF Core 11 is published (#3794).
  • Screenplay.CritterStack (Release v0.27.1): Screenplay.CritterStack builds with the newest C# language version of the SDK in use instead of a fixed C# 14 pin. (#108)
  • Screenplay.Generation (Release v0.21.1): Screenplay.Generation builds with the newest C# language version of the SDK in use instead of a fixed C# 14 pin. (#92)
  • Ante (Release v1.13.0): Ante and its legacy consumer now build on .NET 11 (SDK 11.0.100); the contracts packages target net10.0 and net11.0
  • Ante (Release v1.13.0): Container images use the .NET 11 ASP.NET runtime
  • Ante (Release v1.13.0): CI no longer generates Arc proxies; the checked-in frontend proxies are used (#234)
  • Ante (Release v1.13.0): Improved the structure of the application host for maintainability (#229)
  • Prologue (Release v3.2.1): Prologue builds with the newest C# language version of the SDK in use instead of a fixed C# 14 pin. (#95)
  • Templates (Release v1.8.4): The cratis, cratis-aspire, cratis-chronicle-console and cratis-chronicle-web templates now target .NET 11 (SDK 11.0.100)
  • Chronicle (Release v19.154.1): The production image cratis/chronicle is based on mcr.microsoft.com/dotnet/runtime-deps:10.0-noble-chiseled-extra instead of aspnet:10.0-noble-chiseled-extra, which makes it about 170 MB smaller. The kernel was already self-contained, so it behaves the same, but an image built FROM cratis/chronicle no longer contains a shared .NET runtime or the dotnet host
  • Synopsis (Release v1.2.1): Synopsis builds with the newest C# language version of the SDK in use instead of a fixed C# 15 pin. (#31)
  • Showrunner (Release v1.21.2): Restructured support access, conversation access, issue state, forwarded request and session callback verification code into smaller named steps, keeping every check and its order unchanged (part of #110)
  • Showrunner (Release v1.21.2): Restructured on-behalf token verification and stage production and spec validation into smaller named steps, keeping the same checks, order and problem messages (part of #110)
  • Montage (Release v0.1.1): Montage builds with the latest C# language version, so C# 15 features are available on .NET 11. (#14)
  • AuthProxy (Release v2.60.4): Simplified tenant authentication state, user token storage, client credentials token protection, client principal building, link subject exchange, invite callback completion, identity endpoint calls and service routing validation into smaller, typed steps (part of #298)
  • AuthProxy (Release v2.60.4): Removed duplicated configuration code behind the Aspire AuthProxyExtensions methods; their public signatures are unchanged (part of #298)
  • Eventmodelers-Build-Kit-CSharp (Release v0.1.0): The C# starter targets .NET 11 (net11.0) and pins the .NET 11 SDK 11.0.100 in its global.json; install the .NET 11 SDK to build and run a generated app. (#39)
  • Chronicle (Release v19.154.0): cratis.chronicle.observer.successful_observations now also counts events delivered by catch-up, replay and retry jobs, tagged with cratis.replay, so dashboards show the throughput of replays and catch-ups as well as live delivery
  • Chronicle (Release v19.154.0): A required startup step whose calls time out against this silo or an active sibling that is busy catching up now waits with backoff, without counting attempts and while the kernel stays unready, instead of terminating the process after its retries. The wait is bounded by Startup:BusySiloWaitLimit, two hours by default (#5676)
  • Chronicle (Release v19.154.0): The store entitlements notice is given once the silo is active instead of before the kernel binds its ports, so a kernel enforcing store entitlements binds and reports liveness while it joins a cluster with a backlog (#4040)
  • AuthProxy (Release v2.60.3): Simplified invitation staging, identity account binding and reverse proxy route and cluster configuration without changing their behavior (part of #298)
  • AI (Release v7.153.0): Worker git commands run non-interactively, so a missing credential or prompt fails fast instead of hanging the worker (#1069)
  • Showrunner (Release v1.21.1): The code now builds with the latest C# language version and uses C# 15 collection expression arguments where they replace constructor calls, with no change in behavior (#108)
  • Choreography (Release v2.4.0): The grain compatibility tool runs on .NET 11 (#197)
  • Choreography (Release v2.4.0): The job engine, workflow runs, operations, serializers and job step storage are internally simplified, with no change in behavior (part of #198)
  • Choreography (Release v2.4.0): Shortened two collaboration page search descriptions
  • AuthProxy (Release v2.60.2): Simplified invitation completion, tenant selection, reverse proxy anonymous cluster resolution, bearer route profile selection, canonical identity binding, user access token refresh and canonical identity configuration validation without changing their behavior (part of #298)
  • Screenplay (Release v6.18.0): An action declared for item on a screen with several data blocks now binds to the one collection that a table in scope shows, instead of failing with PLAY0346. When the subject is still ambiguous, PLAY0346 names the candidate data. (#1209)
  • Screenplay (Release v6.18.0): Targets .NET 10 and .NET 11; .NET 8 and .NET 9, which reach end of support on 10 November 2026, are no longer targeted. The cratis tool and the container image run on .NET 11. (#1224)
  • Screenplay (Release v6.18.0): Decimal values in the executable semantic model are lowered identically on .NET 10 and .NET 11, so models produce the same results on both runtimes. (#1224)
  • AI (Release v7.152.2): The Claude Code provider, the provider-aware language model and the pooled chat client are restructured into smaller parts with the same behavior, with new specs for MCP request validation and structured output (part of #1080)
  • AI (Release v7.152.2): The score-fidelity.mjs script in the Screenplay reverse-engineering skill is split into smaller helpers with identical output (part of #1080)
  • AuthProxy (Release v2.60.1): Tenant resolution, identity details resolution, canonical identity resolution and tenancy handling are restructured into smaller, simpler steps with the same behavior (part of #298)
  • AuthProxy (Release v2.60.0): The AuthProxy service and its container image now run on .NET 11, using the mcr.microsoft.com/dotnet/aspnet:11.0 runtime image (#291)
  • AuthProxy (Release v2.60.0): The Aspire hosting integration package now targets both .NET 10 and .NET 11
  • AuthProxy (Release v2.60.0): ASP.NET Core and runtime package dependencies move to 11.0.0 on .NET 11; the .NET 10 target keeps the 10.0 packages
  • AI (Release v7.152.1): The C# rules now cover C# 15 and .NET 11: keep LangVersion at latest, put new .NET 11 runtime APIs in multi-targeted libraries behind #if NET11_0_OR_GREATER with a .NET 10 fallback, use collection expression arguments ([with(capacity: n), .. items]) and labeled break/continue, and keep IDE style rules at suggestion severity.
  • AI (Release v7.152.1): The C# rules now say not to adopt union types, runtime-async or the memory-safety preview, and not to add closed to existing public types.
  • AI (Release v7.152.1): The C# code-quality rules now prefer a sealed record hierarchy with an exhaustive switch for a closed set of outcomes, with closed allowed only on new types in .NET 11 code.
  • Prompter (Release v0.14.19): Prompter’s code style settings now suggest C# 15 collection expressions and labeled loop jumps, and two comparer-backed collections use the new collection-expression arguments, with no change in behavior.
  • Prompter (Release v0.14.18): Prompter now builds with the .NET 11 SDK (11.0.100) and runs on the .NET 11 runtime; the build and runtime container images move to the digest-pinned .NET 11 GA images. (#148)
  • AI (Release v7.152.0): The Cratis.AI package targets net10.0 and net11.0, so .NET 11 applications get a native .NET 11 build while .NET 10 applications keep working unchanged.
  • AI (Release v7.152.0): The repository builds with the .NET 11 GA SDK (11.0.100).
  • AI (Release v7.152.0): The agent harness base image is built on the .NET 11 GA SDK image and still includes the .NET 10 runtimes the Cratis CLI and the Roslyn language server need, so both tools keep starting inside the image.
  • Showrunner (Release v1.21.0): The Showrunner packages target net10.0 and net11.0, so .NET 11 applications get a native build while .NET 10 applications keep working (#106)
  • Showrunner (Release v1.21.0): Stage Manager targets net11.0 and its image uses the mcr.microsoft.com/dotnet/runtime:11.0 base (#106)
  • Showrunner (Release v1.21.0): The repository builds with the .NET 11 SDK (11.0.100) (#106)
  • Montage (Release v0.1.0): Montage runs on .NET 11: it targets net11.0, builds with the .NET 11 SDK, ships on the .NET 11 container images and uses Arc 22.184.0, Chronicle 19.153.2 and Choreography 2.3.1. The local Chronicle kernel image is 19.153.2. (#12)
  • Chronicle.Mcp (Release v2.2.0): The MCP server targets .NET 11 and its container image is based on the .NET 11 runtime image on Ubuntu 26.04 (mcr.microsoft.com/dotnet/runtime:11.0-resolute) (#66)
  • Chronicle.Mcp (Release v2.2.0): Building from source requires the .NET 11 SDK (11.0.100 or later) (#66)
  • Prologue (Release v3.2.0): Packages target .NET 10 and .NET 11, and the Receiver, Interpreter and Extractor applications and their container images run on .NET 11. (#92)
  • Prologue (Release v3.2.0): Agent responses are parsed with fewer allocations.
  • Stage (Release v5.8.0): Takes Screenplay 6.17.0.
  • Screenplay.Generation (Release v0.21.0): Targets .NET 10 and .NET 11. .NET 8 and .NET 9, which reach end of support on 10 November 2026, are no longer targeted. (#89)
  • Fundamentals (Release v7.34.0): Cratis.Fundamentals and Cratis.OpenTelemetry now target .NET 10 and .NET 11. .NET 8 and .NET 9, which reach end of support on 10 November 2026, are no longer targeted. (#1267)
  • Screenplay.CritterStack (Release v0.27.0): Targets .NET 10 and .NET 11. .NET 8 and .NET 9, which reach end of support on 10 November 2026, are no longer targeted. (#105)
  • Scene (Release v5.2.0): Targets .NET 10 and .NET 11. .NET 8 and .NET 9, which reach end of support on 10 November 2026, are no longer targeted. (#293)
  • Specifications (Release v5.3.0): Targets .NET 10 and .NET 11. Cratis.Specifications, Cratis.Specifications.XUnit, Cratis.Specifications.NUnit and the other packages now ship net10.0 and net11.0 builds; .NET 8 and 9 remain unsupported (they reached end of support on 10 November 2026). (#110)
  • Specifications (Release v5.3.0): Building the repository requires the .NET 11 SDK. (#110)
  • Synopsis (Release v1.2.0): Cratis.Synopsis now targets .NET 11 in addition to .NET 10. (#29)
  • Synopsis (Release v1.2.0): The synopsis .NET tool now runs on .NET 11; install the .NET 11 runtime to use it.
  • Stage (Release v5.7.0): Takes Screenplay 6.16.0.
  • Chronicle (Release v19.153.1): A failure that repeats with the same cause during a cold start is logged in full once per interval, followed by a summary of how many more occurred, instead of one stack trace per occurrence. This applies to every log provider, including suppressed unobserved task exceptions, and a failed event store subscription refresh is no longer logged twice (#5678)
  • Chronicle (Release v19.153.1): An observer no longer registers an alert reminder on every activation. Healthy observers hold no reminder, so a cold start after downtime no longer activates every observer at once. Reminders left by earlier versions are removed on their next tick, so the first start after upgrading still runs them once. The MongoDB storage documentation describes minPoolSize for warming the connection pool at start (#5677)
  • Stage (Release v5.6.0): Takes Arc 22.184.0, which carries the row narrowing contract.
  • AI (Release v7.151.1): Arc TypeScript proxies are generated and committed by the client that changes a command or query, never in CI. CI builds pass -p:CratisProxiesOutputPath= in every configuration, which is Arc’s off switch. DisableProxyGenerator works only in repositories that define it themselves. (#1112)
  • Chronicle.Elixir (Release v3.22.0): Ordinary appends honor an entry’s generation for the event type they send.
  • Chronicle.Elixir (Release v3.22.0): The client now depends on cratis_chronicle_contracts 19.153.
  • Stage (Release v5.5.0): Takes Screenplay 6.14.0.
  • Chronicle.TypeScript (Release v6.62.0): The client now depends on @cratis/chronicle.contracts 19.153.0.
  • Chronicle.Kotlin (Release v7.9.0): The client now depends on io.cratis:chronicle-contracts 19.153.0.
  • Chronicle.Go (Release v0.13.1): Generated contracts and decision-read admission now target Chronicle 19.153.0.
  • AI (Release v7.151.0): The worktree guidance names a writable location ($HOME/.worktrees/<name>) inside container workers, whose workspace parent is read-only. (#1099)
  • AI (Release v7.151.0): Event types use plain [EventType], so the type name is the id, including public contracts. An explicit id is only for keeping an already-persisted id or resolving a short-name collision between packages, and persisted ids are never changed. Decision 152 qualifies decisions 0007 and 0008. (#1108)
  • AI (Release v7.151.0): The shared corpus takes precedence over repository-local specs and existing code for house conventions unless an accepted decision record names the rule it replaces. It never relaxes contracts, security, authorization or quality gates. (#1108)
  • AuthProxy (Release v2.59.0): A DPoP-bound token sent as a plain Bearer credential, a DPoP proof on a token that is not bound, and DPoP proofs combined with cookies or other credentials are refused with invalid_token.
  • AuthProxy (Release v2.59.0): Introspection answers must carry a cnf that matches the access token’s own binding on DPoP routes.
  • AuthProxy (Release v2.59.0): The verified sender binding is carried into the forwarded identity.
  • Chronicle.Go (Release v0.13.0): Generated contracts and decision-read admission target Chronicle 19.150.1; a Chronicle Kernel 19.150.0 or later is required.
  • Chronicle (Release v19.152.0): The client event store name defaults to the program identifier or entry assembly name, normalized to a valid MongoDB database name; an explicit name is never changed. (part of #5778)
  • Chronicle (Release v19.152.0): The kernel hashes event source ids in traces by default; set Telemetry:EventSourceIdHashKey for hashes that are stable across restarts, or choose Raw/Omitted. (part of #4458) (part of #5778)
  • Chronicle (Release v19.152.0): OpenTelemetry OTLP export starts only when an OTLP endpoint is configured. (part of #4458) (part of #5778)
  • Chronicle (Release v19.152.0): Production kernel images require storage connection details and fail at startup with a clear message when none are configured; development images keep the embedded database as a last-resort default. (part of #5778)
  • Chronicle (Release v19.152.0): The kernel warns when the default admin password setting is ignored. (part of #5778)
  • AuthProxy (Release v2.58.1): Split invitation completion and identity resolution into smaller, intention-named steps with the same checks in the same order (part of #298).
  • AuthProxy (Release v2.58.1): Restructured bearer route, canonical identity, tenant resolution and tenant selection code into focused rules that keep fail-closed defaults and validator error order (part of #298).
  • AuthProxy (Release v2.58.1): Simplified token, on-behalf session, routing, authentication callback and Aspire environment code without changing observable behavior (part of #298).
  • Screenplay (Release v6.13.0): A default source such as asset AssetId from $context.asset parses, prints and round-trips, and is refused when bound until a trusted context can carry it.
  • Screenplay (Release v6.12.0): produces when, validate and reaction where keep refusing the text operators when bound; one boolean property per feature remains valid.
  • Screenplay (Release v6.11.0): Comparing a policy read with the caller identity or with a property of the authorized command is still refused when bound, until policy inputs arrive.
  • Screenplay (Release v6.10.0): Binding a state policy to the executable semantic model is refused with an unsupported-syntax diagnostic until it is admitted. Existing models serialize with the same bytes as before.
  • AuthProxy (Release v2.58.0): OAuth access tokens that carry a cnf (confirmation) claim are now refused with 401 invalid_token, on bearer routes and on the general JWT bearer path. AuthProxy does not verify DPoP proofs, so a sender-constrained token is never treated as an ordinary bearer token. Introspection answers that carry cnf are treated as inactive. (part of #256)
  • AuthProxy (Release v2.58.0): The pinned Identity authorization vectors (vectors/arc-mcp-authorization/v1.0.0) now run as executable specs; cases AuthProxy does not own are listed explicitly with reasons. (part of #256)
  • AI (Release v7.149.0): The reverse-engineering skill builds a high-level flow map first and takes intake flow by flow, and every slice, rule and rejection records the evidence it came from and the decision taken (part of #1056)
  • AI (Release v7.149.0): The reverse-engineering skill pairs every time-rule probe with its negative case, stamps $context.occurred fields with a given clock in specifications, and records state-reading authorization as a gap instead of inventing syntax (part of #1056)
  • AI (Release v7.149.0): The reverse-engineering skill counts a model as runnable only when Stage admits it with no unsupported artifacts and every specification passes, and writes cross-field rules as declarative require lines (part of #1056)
  • Stage (Release v6.2.0): The legacy EventModel engine refuses rules it cannot enforce, collection-path rules and nested enum inputs instead of silently accepting them (#1054)
  • AI (Release v7.168.3): A refreshed subscription credential is no longer reported as stored when recording it fails.
  • cli (Release v3.139.1): A builder run with --docker can push to GitHub over HTTPS: it signs in with the GITHUB_TOKEN or GH_TOKEN of the machine that started it.
  • Chronicle (Release v19.168.0): Chronicle now removes recommendations left behind for observers and projections that no longer exist when it starts (#5644)
  • Chronicle.Elixir (Release v3.24.1): Reactors and reducers reconnect when the server closes the client’s main connection while the session’s own connection stays up, such as when one kernel instance stops during a rollout. They no longer retry on the closed connection forever, logging FunctionClauseError in GRPC.Client.Adapters.Mint.send_data/3.
  • Chronicle.Elixir (Release v3.24.1): The client no longer leaks a process for every call that fails on a closed connection, every observation stream torn down for a reconnect and every dropped session. On a long-running node these accumulated into hundreds of thousands of processes and exhausted its memory.
  • Chronicle (Release v19.167.1): The Chronicle and dedicated health listeners reload the PKCS#12 file at tls:certificatePath when it changes (checked on a handshake, at most every 30 seconds). A file that cannot be loaded keeps the current certificate and is logged once.
  • Chronicle (Release v19.167.0): Observable queries on a parent read model now update when a child is removed through a join (RemoveWithJoin), and a parent’s cached state is correct after many children are removed at once. (part of #1896)
  • Stage (Release v6.1.1): Calls to an extension’s gRPC backend recover after the connection drops: Stage forgets the broken channel and connects again on the next attempt instead of failing every later call (#1132)
  • Chronicle (Release v19.166.3): A new definition change for a projection, reactor, reducer or webhook now replaces the replay recommendation still pending from an earlier change, so only the latest one is offered. Removing an observer also removes its recommendations, and an ignored recommendation no longer reappears when the same change is reported again. (#5644)
  • Chronicle (Release v19.166.3): Pull-request builds of the Workbench now reuse the yarn cache saved on main instead of downloading every package again. (#5918)
  • AI (Release v7.168.1): The secrets guard classifies protected paths consistently and refuses more recursive reads of mounted secrets (#1222)
  • Chronicle (Release v19.166.2): Event store subscriptions now report which constraints rejected a forwarded event and forward content whose property casing differs from the target event type’s schema (part of #5797)
  • Chronicle (Release v19.166.2): Protected values encrypted under an earlier key revision now decrypt after a key rotation instead of failing with an OAEP decoding error on every read (#5887)
  • Chronicle (Release v19.166.2): The implicit subscriptions tutorial now uses a published package version and targets .NET 10 (#5564)
  • Chronicle (Release v19.166.2): The .NET quickstart includes the namespace needed for the connection string (#5565)
  • Chronicle (Release v19.166.2): The short-lived processes guide gives correct subscription and manual registration guidance (#5572)
  • Chronicle (Release v19.166.2): The TypeScript gRPC contributor guide names the Node version the workflows use (#5592)
  • Chronicle (Release v19.166.2): The .NET client getting-started page names IEventLog (#5643)
  • Scene (Release v6.0.1): The Screenplay bridge converts nested sample-data rows into ordered JSON arrays of objects, recursively, so Scene previews show child collections; an empty collection stays an empty array, and an unknown value kind throws UnknownSampleDataValueKind
  • Scene (Release v6.0.1): @cratis/scene.editor builds on macOS and Windows: the design-system standard’s offStandard.ts collided with OffStandard.tsx on case-insensitive file systems, and is now offStandardEntries.ts
  • Stage (Release v5.30.0): Commands run through the endpoint spec harness no longer share one set of command context values, so values written while one command runs no longer leak into the next (#965)
  • Chronicle (Release v19.166.1): Constraint diagnostics and logs no longer include event source ids (#5692)
  • Chronicle (Release v19.166.1): Observers no longer stall when a catch-up finds no work while still behind the event log; they retry catch-up shortly instead (part of #5351)
  • Chronicle (Release v19.166.1): Disposing an in-process Chronicle connection in integration specs now ends its connection loop instead of pinging the disposed silo until the process exits (#5619)
  • Chronicle (Release v19.166.1): Decimal properties declared alongside an inherited schema are now stored as decimals instead of doubles (#5840)
  • Chronicle (Release v19.166.1): Retrying a failed partition from the operator tools now works after its automatic attempts are exhausted, and the partition stays quarantined when no retry job starts (#5715)
  • Chronicle (Release v19.166.1): Resolving two deferred events for the same new child together no longer creates duplicate child entries (#5662)
  • Chronicle (Release v19.166.1): Corrected documentation pages that no longer matched the code, and added reference pages for analyzer rules CHR0058–CHR0061 (#5931)
  • AI (Release v7.167.2): The Claude Code provider’s local MCP server now gives each tool call a 60-second deadline and returns the usual tool failure result when it expires, so stalled tools no longer hold request slots until the server stops (#1214)
  • AI (Release v7.167.2): A tool whose schema has a required value that is not an array of strings now gets a JSON-RPC invalid-params error instead of an HTTP 500 (#1214)
  • AI (Release v7.167.1): The secrets guard no longer refuses test runs whose filter values end in a wildcard, such as -method 'Namespace.should_run*'. (#1211)
  • AI (Release v7.165.6): The secrets guard no longer refuses reading files whose names merely contain the word environment, such as *.environment.txt and .environment.txt fixtures; every other .env-prefixed name stays protected. Run cratis ai update to get the updated hook. (#1203)
  • cli (Release v3.138.1): cratis env change-secrets-provider now cleans up correctly when secrets move between two stores of the same provider: moving between two Azure Key Vaults, or between HashiCorp Vault mounts or namespaces on the same server, removes the old entries; when the old and new stores might be the same (a vault alias, or a different Vault server address), the old entries are kept and a warning names each one, so a move can never delete the secrets it just wrote. The JSON output reports how many entries were removed and any warnings (#538)
  • AI (Release v7.165.4): Skill evaluations now stage every rule and skill a skill depends on, so evaluations no longer run against an incomplete corpus (#978)
  • AI (Release v7.165.4): The Pi plugin loads rules for composed profiles, including cratis/full, when no language is selected (#986)
  • Chronicle (Release v19.166.0): Date-time event properties appended with a non-UTC offset keep that offset when the event is read back through the API, gRPC, SQL storage and compliance release, instead of being shifted into the host’s local time; values written in UTC or without an offset, and previously stored events, read back exactly as before (#5907)
  • Chronicle (Release v19.166.0): Unique constraints treat two date-time values for the same instant as equal regardless of the offset they were written with (#5907)
  • Screenplay (Release v6.31.2): Lifecycle specifications no longer pick an unrelated read-model instance as the workflow subject when the subject’s key has no matching instance; the subject is now absent unless the key matches exactly (#1135)
  • Components (Release v4.41.6): Chat emoji and reaction pickers now open in the overlay container your provider supplies, layer above the dialog they are opened from, keep a scoped theme, and close on outside clicks in the document they are shown in, instead of always rendering on the page body. (#484)
  • Arc (Release v23.12.2): CommandContextValues.Empty now returns a new instance on each access, so values written to one command context’s empty values no longer leak into other contexts (#3880)
  • Components (Release v4.41.5): The presentation property editor in the component picker no longer reports or previews the previous component’s unsaved edits after you pick another component. (#483)
  • Arc (Release v23.12.1): Chronicle 19.162.1: Registering projections from a client older than the stored definitions no longer stalls registration
  • Stage (Release v5.29.1): Scene previews show nested sample-data rows as JSON arrays instead of losing rows within rows (#973)
  • Stage (Release v5.29.1): Documentation pages for extensions, inbound traffic, the spec runner, rendering references and URLs now match current behavior, and the body-worker profile version, STAGE_ROUTE_DIAGNOSTICS and STAGE_STATE_DIR settings are documented (#1149)
  • Stage (Release v5.29.1): Corrected the project-folder reference: supported cratis run commands, which declarations combine or are rejected as duplicates, and how to recover when Stage refuses a project (#940)
  • Components (Release v4.41.4): TagGroup treats each duplicate tag as its own item: removing one occurrence of a repeated value leaves the others in place, and duplicates supplied through value render and can be removed individually even when allowDuplicates is off. (#488)
  • cli (Release v3.138.0): A cancellation in the Direct MCP bridge that arrives while the request is completing no longer fails. (#537)
  • Arc (Release v23.12.0): WithChronicle() no longer fails at startup when the application does not supply a Chronicle connection explicitly (#3634)
  • Arc (Release v23.12.0): Model-bound commands are reachable in NativeAOT-published applications instead of returning 404 (part of #3595)
  • Arc (Release v23.12.0): Proxy generation now discovers validators in assemblies that reference ASP.NET Core (#3873)
  • Arc (Release v23.12.0): The forwarded identity header warnings now link to the secure defaults documentation (#3875)
  • Arc (Release v23.12.0): Corrected documentation for the HTTP contract, commands, queries, proxy generation, identity, validation and testing so it matches current behavior (#3875)
  • Arc (Release v23.12.0): Corrected query-binding, validation, response handling and React documentation (#3625)
  • Components (Release v4.41.3): DataTable rows keep their identity when the loaded data changes: rows are keyed by their dataKey value instead of their position, so selection, expansion and in-row state stay with the right row after updates. Rows without a unique key fall back to positional keys. (#492)
  • Fundamentals (Release v7.34.1): Generated type-discovery bindings no longer fail when a referenced Cratis package removes a type; the affected binding is skipped and registration order is preserved. (#1266)
  • Showrunner (Release v2.16.1): The Understudy backup fact is now UnderstudyBackupTaken (was BackupTaken), so its event type id no longer collides with an event type that Cratis Direct had already released. Consumers that mirror the Understudy contract must use the new name.
  • AI (Release v7.164.3): The C# specifications rule and patterns now show the ShouldContain overload the Specifications library actually declares (Func<T, bool>), with an adapter example for an existing Predicate<T>. (#980)
  • AI (Release v7.164.3): The README’s local verification steps now match the Yarn workspace setup and CI: one root install, the workspace check, verify, lint and test commands, package validation, and the .NET phase run separately. Paid model evaluation stays optional. (#981)
  • AI (Release v7.164.3): The TypeScript rule binds the paging setter at its real tuple position for plain queries and shows the shorter observable-query tuple separately. The Storybook checklist no longer asks for stories for live slice pages wired to Arc hooks. (#984)
  • AI (Release v7.164.3): The specification writer and the code-review checklist no longer ask for an extra race-policy proof. A rule that must hold under concurrent writers is proven from supplied read-model state, matching the scenario rule. (#989)
  • Screenplay (Release v6.31.1): Closing an event-model board in VS Code while it is still compiling no longer leaves a file watcher behind that keeps compiling the closed board when application files change (#1142)
  • Chronicle (Release v19.164.5): The ASP.NET Core namespace resolver no longer creates comma-joined namespaces such as tenant,tenant when the tenant header is sent more than once. Repeated or comma-separated header values that name the same namespace resolve to that namespace, and values naming different namespaces are rejected with an AmbiguousNamespaceHttpHeader error that names the header. (#5891)
  • AI (Release v7.164.2): The Screenplay skills now state that systems are admitted at ESM v50 once any system in the model declares an ability (only operations, and systems in models without abilities, stay unadmitted under PLAY0268), that remove via join reports PLAY0873 rather than PLAY0872, and that graphs accept a documentation block. (#1186)
  • Components (Release v4.41.2): PivotViewer no longer leaves a Pixi application and its canvas behind when React StrictMode replays the stage effect, including when the component unmounts before initialization finishes (#493)
  • cli (Release v3.136.3): cratis ai install and cratis new now exit with 5 (validation_error) for invalid options instead of 10 or -1, and still report what was wrong (#617)
  • Components (Release v4.41.1): The documentation, README and migration guide now give the supported Arc peer range as below 24, matching the published package, and the README’s Arc pin example uses 23.0.0 (#513)
  • Components (Release v4.41.1): Tabs, ToggleGroup and server-side sorting are documented as shipped components and features instead of being listed as missing
  • Components (Release v4.41.1): The chat and configuration editor examples now use the real component APIs
  • Components (Release v4.41.1): Previously undocumented props, helpers and options are now described, including the Canvas chat props, DataTableCore with local rows, ReadModelView used on its own, SchemaEditor labels, helpers and type-color tokens, and options for the pickers, icons, markdown and toasts
  • Components (Release v4.41.1): The README’s table of package subpaths now points to the package exports for the complete list
  • cli (Release v3.136.2): The Cratis CLI documentation, README and command help text now match how the commands behave, including options, defaults, exit codes and bundled component versions (#615)
  • Arc (Release v23.11.0): Events appended by response value handlers now carry the command on their causation chain, also when the transactional command scope completes after the command’s causation scope has ended. (#3735)
  • Arc (Release v23.11.0): Enumerable observable queries close the WebSocket connection again when a custom connection handler fails to send, instead of silently skipping each item (#3652)
  • Arc (Release v23.11.0): Subclasses of WebSocketConnectionHandler that re-implement SendMessage are now used for query data pushes, not only for error frames (#3652)
  • Arc (Release v23.11.0): Typed command results (Execute<TResult>) now keep the retryable flag from the underlying result. (part of #3869)
  • Stage (Release v5.28.1): Authored sidebar links now navigate correctly when the application uses pathname routing. (#946)
  • Stage (Release v5.28.1): Approval decisions are rejected for workflow nodes that are not approval nodes, instead of being acknowledged as accepted. (#948)
  • Stage (Release v5.28.1): State-entry commands now include the matching subject values in their payloads. (#949)
  • Stage (Release v5.28.1): Rendered state machines resume in their current state, read from the followed read model, instead of always starting in their initial state. (#1104)
  • Stage (Release v5.28.1): Body workers that do not use a reducer can materialize authored enum values whose generated member name differs from the authored name. (#943)
  • Stage (Release v5.28.1): Restarting a semantic world no longer refuses events with DateTime properties, and nullable protected DateTime values are stored correctly. (#1139)
  • Screenplay (Release v6.31.0): The screen composition acceptance audit now compares full recovered contract signatures, including member types and modifiers, and only accepts navigation reached by clicking the authored entry. (#1133)
  • Chronicle (Release v19.164.3): Read model JSON schemas describe dictionaries whose values are concepts, including nullable concept values, using the concept’s underlying type (#5899)
  • Chronicle (Release v19.164.3): Observer information returned by the kernel now comes from a single consistent snapshot instead of states read at different moments (#5606)
  • Chronicle (Release v19.164.3): Composite seed keys in read model scenarios reject lossy numeric conversions and accept valid large double keys (#5563)
  • Arc (Release v23.10.1): Documents generated from C# no longer fail to load on the embedded board because of incomplete projection coverage (PLAY0284); the coverage findings are shown as warnings instead, while hand-written embedded documents and any other compiler error are still refused (#3860)
  • AI (Release v7.160.3): Agent-harness image publishing now creates and verifies every version manifest (exactly linux/amd64 and linux/arm64) before moving any latest tag, retries each registry call, and builds the manifests from the digests the architecture builds pushed instead of mutable per-architecture tags (#1026)
  • Arc (Release v23.9.2): Screenplay generation now recovers exact generated query specifications (a substituted read model set, one call to an application query and a whole expected read model) as then query scenarios instead of leaving them out; scenarios that cannot be stated exactly are left out with a warning that says why (part of #3547)
  • Chronicle (Release v19.164.2): Event store subscription reminders now retry only namespace revocations that failed, and a subscription’s first add also revokes observers outside its source namespaces (#5904)
  • Chronicle (Release v19.164.2): SQL storage orders limited event sequence reads by sequence number before applying the limit (#5570)
  • Chronicle (Release v19.164.2): Read-protection refusal messages in the .NET client now point to the correct Handle() guidance (#5587)
  • Arc (Release v23.9.1): Restored the QueryResult.Unauthorized(CorrelationId) overload, so assemblies built against Arc 23.2 or earlier no longer fail with MissingMethodException when a query is refused as unauthorized (#3863)
  • cli (Release v3.136.1): A builder connecting through the hosted Studio is no longer refused right after it registers. The Studio proxy removes Authorization on the builder path, so the CLI now sends its credential in X-Studio-Builder-Credential as well. It needs a Studio release that reads that header.
  • Chronicle (Release v19.164.1): Releasing protected values no longer fails with EncryptionKeyFenceUnavailable when many encryption keys are tracked: the kernel now refreshes their release fences concurrently, in bounded batches, so the refresh fits within its time budget. A stale or unavailable fence still fails closed, and a timed-out release no longer affects later independent operations (#5912)
  • AI (Release v7.159.1): The Screenplay command-surface reference no longer carries a stale sentence about how described handler files are admitted (#945)
  • Arc (Release v23.8.2): Generated TypeScript query proxies, both normal and observable, now keep the validation severity from the server instead of dropping it. (#3636)
  • Arc (Release v23.8.2): A query cache entry that has been released keeps its retention timer when the connection reconnects, so it no longer stays in the cache forever. (#3644)
  • Arc (Release v23.8.2): Suspense query resources are keyed by a stable query identity rather than the class name, so different queries whose classes share a name (for example after minification) no longer share results. (#3645)
  • Arc (Release v23.8.2): Mounted Suspense observable queries subscribe again after reconnectQueries on a shared hub, so they keep receiving updates. (#3646)
  • Arc (Release v23.8.2): A command created with useCommand is removed from its command scope when the component unmounts, so a surviving scope no longer tracks commands from editors that are gone. (#3647)
  • Arc (Release v23.8.1): The Screenplay model generated from C# projections now keeps ToEventContextProperty(c => c.CausedBy.Subject) mappings, at the root and inside children, instead of dropping them (#3670)
  • Arc (Release v23.8.1): Joins declared inside Children(...) are now carried into the generated model, both with explicit Set mappings and with auto-mapping (#3670)
  • Arc (Release v23.8.1): Computed get-only properties on read models and child records are no longer emitted as stored fields in the generated model (#3670)
  • Scene (Release v5.4.2): Slot shape diagnostics name an action, button, toolbar element or stored presentation without an id as (no id) in both the C# and TypeScript engines, instead of null or undefined (#299)
  • Scene (Release v5.4.2): Navigation edits on a model that declares the same outlet more than once change only the first declaration in the C# engine, matching the TypeScript engine and how navigation is read (#300)
  • Scene (Release v5.4.2): The C# engine describes guard condition text the same way as the TypeScript engine: double quotes are written as \" and apostrophes are left as they are, and a negative zero is read and written as 0 (#301)
  • Components (Release v4.41.0): The calendar toggle button of DatePickerInput now has an accessible name and points to the calendar dialog it opens with aria-controls and aria-expanded (#505)
  • Components (Release v4.41.0): The Chat emoji picker and reaction picker are nonmodal button groups that move focus between options with the arrow keys, Home and End, and show emoji categories in their keyboard order (#485)
  • Showrunner (Release v2.11.1): Cue’s subtitles were drawn in the darkest surface colour, so on the dark theme the words almost vanished into the card behind them. They now use the theme’s text colour. A specification guards the stylesheet against any text being drawn in a surface colour. (part of #139)
  • Chronicle (Release v19.162.1): Registering projections from a client older than the stored definitions no longer stalls registration for the event store; the “ignored registration” recommendations are added concurrently, once per projection and version pair, and a failure adding one no longer fails the registration.
  • Chronicle (Release v19.161.0): Generated queries resolve namespace names with the stored casing, and removing a namespace invalidates its cached casing (#5701)
  • Chronicle (Release v19.160.0): Read models with dictionaries whose values are concepts (for example personal data marked [PII]) now keep the value’s type and compliance metadata in the generated schema, so the kernel can release them instead of failing because the property is missing from the schema (#5896)
  • Stage (Release v5.27.1): Semantic queries and read models against an external Chronicle kernel now include events appended outside Stage, instead of staying empty while status reports ready (#1059)
  • Stage (Release v5.27.1): Reconciling a stopped invocation now waits until reconciliation is ready, so it no longer times out intermittently while waiting for settlement (#1134)
  • Stage (Release v5.27.1): A standalone generated application waits for the Chronicle kernel to report ready before the host starts, so the Chronicle handshake no longer fails at startup (#1076)
  • Stage (Release v5.27.1): A semantic world now restarts over stored events with decimal properties: new event types keep decimals exact, existing event types keep their stored schema, and Stage reports the event types that cannot be rebuilt exactly (#1060)
  • Chronicle (Release v19.159.0): The kernel releases idle projection pipelines and their handle locks, so memory no longer grows with every namespace that has ever had an active projection observer. (#5870)
  • Chronicle (Release v19.159.0): Reducers keep observing after the client reconnects to the kernel instead of failing with a disposed-object error. (#5869)
  • Arc (Release v23.6.0): Tenant resolution from the tenant header no longer accepts a comma-joined value; conflicting values resolve to no tenant. On the HttpListener host repeated header lines cannot be detected by default; trusted ingress must strip all incoming tenant headers and inject exactly one value. (#3791)
  • Arc (Release v23.6.0): Observable queries over SSE, WebSockets and streamed enumerables now authorize every update against the user admitted when the subscription started, instead of whichever identity is current when the update is sent (#3728)
  • Arc (Release v23.6.0): <Arc> accepts any React children (strings, null, conditional and mixed children) without a type error (#3801)
  • Arc (Release v23.6.0): MongoDB observable queries fail with a clear MongoDBChangeStreamsNotSupported error when the server has no change streams, instead of hanging or returning an unexplained 500 (#3668)
  • Arc (Release v23.6.0): Exception-detail defaults follow the host environment and explicit options. (part of #3778)
  • Arc (Release v23.6.0): Missing MongoDB connection settings name the configuration keys to supply. (part of #3778)
  • Arc (Release v23.6.0): Proxy generation explains when an unset output path skips generation. (part of #3778)
  • AI (Release v7.157.0): The secrets guard no longer refuses Git commands on source files whose names merely contain words such as Credential, Secret or Token, while real secret files stay protected (#1153)
  • cli (Release v3.134.1): The Workbench applications and users lists now show the cratis chronicle login hint when Chronicle rejects the login token as unauthenticated, instead of an empty list (#593)
  • Chronicle (Release v19.156.7): The kernel keeps at most 256 compiled projection graphs in memory and evicts the least recently used ones. Live projection pipelines keep working independently of the cache, and read-model visibility checks read only metadata instead of loading the projection. A new metric reports the cache size (part of #5856)
  • Chronicle (Release v19.156.6): The kernel no longer keeps delivery correlation entries after a reactor or reducer delivery wait is abandoned, so memory no longer grows when client deliveries time out or are cancelled (part of #5856)
  • Chronicle (Release v19.156.5): The kernel’s encryption-key cache is now bounded: each cache map keeps at most 10,000 entries, evicting the oldest first. Expired entries for keys that were not found are swept periodically instead of staying in memory until the same key is requested again. Erased keys still cannot reappear through the cache, and a completed save always replaces what the cache held for that key (part of #5856)
  • Chronicle (Release v19.156.5): The hot-core gate for pull requests labeled run-integration now reports its result in the same workflow run as the requested integration, so it no longer waits for a separate refresh after each push. (part of #5560)
  • Stage (Release v5.23.1): The task dialog a toolbar slice button opens no longer shows the slice’s kind and model name (State Change · DraftProduct) under its title; people see the button’s title and the fields.
  • Stage (Release v5.21.1): A toolbar button for item on a list screen now acts on the row selected in the screen’s table: a button that runs its slice stays disabled until a row is selected, its enabled when reads that row, and the command is sent with the row’s values. Before, such a button never had a row to act on and could not be used.
  • Chronicle (Release v19.156.4): An observer catch-up or replay job step whose stored state lost its observer key now fails with a warning instead of failing repeatedly on every activation (part of #5855)
  • Chronicle (Release v19.156.4): Keys that are undefined, and keys that use an array indexer value, now survive JSON serialization (part of #5855)
  • AuthProxy (Release v2.63.0): A sign-in that AuthProxy refuses during the OIDC callback is now answered as a failed sign-in and no longer leaves a session behind. (#329)
  • AuthProxy (Release v2.62.2): Paths under /.cratis/ that AuthProxy does not serve itself, such as Arc’s /.cratis/queries/sse, /.cratis/queries/ws and /.cratis/commands, are forwarded to the service again instead of answering 404. Since v2.56.0 every unmatched /.cratis/ path was refused, which stopped observable queries from receiving data in Arc applications. Only AuthProxy’s own endpoints (identity, providers, login, token, tenant selection, logout, link and on-behalf) stay reserved.
  • Choreography (Release v2.6.1): SQL job storage now keeps the full state of job steps whose state type adds its own properties. Previously only the base step state was saved, so a step resumed after a restart came back prepared but without its own values. Step state is now saved with the host’s serializer options, including concept values and dictionaries keyed by concepts, and steps saved by earlier versions can still be read. (#217)
  • AuthProxy (Release v2.62.1): A whitespace-only tenant source identifier (from a header, claim, route or host) no longer resolves a tenant, and startup now rejects tenant configurations whose SourceIdentifiers or Domains entries are empty or whitespace-only (#303)
  • AI (Release v7.153.8): Worker launch no longer fails with “Could not find the file /run/agent-secrets in container” when the worker image does not pre-create the secrets directory. Secret delivery fails closed if file permissions cannot be verified, and secret-delivery execs ignore job-level environment overrides. (part of #1047)
  • AI (Release v7.153.8): Worker RTK initialization is bounded and never waits on an interactive prompt. (part of #1047)
  • Stage (Release v5.20.1): A toolbar button that issues a State Change slice whose own screen is a dialog (fits dialog, or a dialog template such as QuickCreateDialog) now opens that screen: the fields and labels of the form it declares for the command, without the identity the command creates, and the screen its action names with navigate to once the command succeeded. A slice without a dialog screen, or whose dialog screen declares neither a form nor a navigate to, still opens the task dialog made from the command’s schema. (#1097)
  • Chronicle (Release v19.156.3): A refused server stream ends with its refusal status and sends nothing further (#5834)
  • Chronicle (Release v19.156.2): .NET 11 byte array properties no longer make event type registration fail because of the generated contentEncoding schema keyword; the .NET client omits it and the kernel ignores it when comparing event type schemas (#5826)
  • Arc (Release v22.186.2): Cratis.Testing now ships a net11.0 build, so .NET 11 projects that reference it restore without NU1605 downgrade errors for System.Security.Cryptography.Pkcs and related packages (#3806)
  • Arc (Release v22.186.2): Startup decision reads no longer create an unnamed Chronicle event store and use the event store the client was configured with (#3807)
  • Arc (Release v22.186.2): The ARCCHR0002 analyzer no longer reports commands whose Handle returns OneOf of event-source-carrying outcomes and validation results. (#3808)
  • Stage (Release v5.14.0): A set-once mapping now counts as establishing the property it sets, so a projection that only sets a required property once is no longer rejected.
  • Chronicle (Release v19.156.1): Registering an [Obsolete] event type on .NET 11 no longer fails with EventTypeSchemaChanged when the type was registered from .NET 10; the deprecated annotation keyword is ignored when comparing event type schemas (part of #5826)
  • Chronicle (Release v19.156.1): A failing partition job step now reports its original failure instead of masking it with an Orleans activation-access violation (#5804)
  • Arc (Release v22.186.1): With resilience enabled (the default), the first use of each document type no longer generates a proxy type under a global lock, and calls no longer go through reflection. A host whose first requests read many read-model types used to stall for seconds after every start; a Studio event model that took 11-14 seconds to open on a fresh process now opens in about one second. Per-method concurrency limits, cancellation, and the empty results for a collection the server reports as missing work as before.
  • Chronicle (Release v19.156.0): A graceful stop of the kernel exits with code 0. A failed start, a stop that overruns the shutdown timeout, or a failure while stopping or releasing services exits with 70 and a Critical log naming the reason, and a lost single-writer lease exits with 1 as documented (#5813)
  • Stage (Release v5.12.0): A model that uses the caller’s identifier in a policy is no longer refused with STAGE-ESM-016.
  • Ante (Release v1.14.0): A host upgrading from Ante 1.9.0 no longer fails to start because Chronicle refuses the changed generation-1 schemas of the setup, legal terms and registration events; their generation 1 is restored and the identity provider key and issuer move to generation 2 with a migration that leaves them empty for earlier facts (#239)
  • Synopsis (Release v1.2.4): Repository URLs inferred from the git remote no longer include user info, query string or fragment, and only http, https and git@github.com: remotes are used.
  • Chronicle (Release v19.155.1): Stopped including event property values in conversion warning logs
  • Chronicle (Release v19.155.1): Stopped leaking a timer when enabling read-committed snapshot isolation on SQL Server completes before the diagnostics threshold (#5811)
  • Chronicle (Release v19.155.1): Debug builds of the solution succeed again with the .NET 11 SDK (#5818)
  • AuthProxy (Release v2.60.5): A person who had already completed an invitation and opened its link again got an empty “404 Not Found” page when the link had nowhere to lead (no lobby frontend configured, or a matching tenant returning to its application). They are now sent to the application root.
  • Stage (Release v5.9.0): Decimal values from floating-point numbers in seeds, specification values, executed bodies and generated capture state are the same on .NET 10 and .NET 11, so rendered applications behave identically on both runtimes (part of #1047)
  • Stage (Release v5.9.0): Rendering several applications at the same time no longer fails because their scaffolds shared one template engine settings location.
  • Stage (Release v5.9.0): Pure transition bodies are analyzed against the reference assemblies for the scaffold profile’s target framework, so .NET 11 applications are checked against .NET 11 (#1072)
  • cli (Release v3.127.0): Rewriting AI configuration files no longer corrupts them on .NET 11. (part of #570)
  • Choreography (Release v2.4.1): Collaboration session identifiers are now scoped to the participant who connects, so a reconnect only replaces that participant’s own earlier session, also across replicas
  • Arc (Release v22.185.0): Floating-point values read from MongoDB and Neo4j into decimal values keep their .NET 10 results on .NET 11.
  • Arc (Release v22.185.0): Fixed request handling on reused connections when a request is rejected early.
  • AI (Release v7.153.2): Prevent surviving git helpers from keeping workers waiting past the git deadline while checking the remote default branch (#1126)
  • Chronicle (Release v19.154.1): Publishing the kernel self-contained for a runtime other than the build machine’s, for example linux-arm64 from a Mac, no longer fails with NETSDK1047 in the code generators
  • AI (Release v7.153.1): The shell-writes guard no longer refuses routine read-only commands that carry pattern text: git branch --list and git tag --list patterns, grep --include/--exclude filename filters, ${var%%pattern} style parameter-expansion operators, and glob sources in cp, rsync and install. Only the copy destination is checked as a write, including the file a copy creates inside a destination directory, so writes to protected paths, globs that may match them and unknown options are still refused. Run cratis ai update in your session’s starting checkout to refresh its guards (#1119)
  • Chronicle (Release v19.154.0): A kernel rollout converges under load: a subscribe that times out against a busy observer is retried on the same stream instead of failing the client’s stream, reactor and reducer streams in the .NET client reconnect with a jittered back
  • Stage (Release v5.8.1): A specification for a command whose policy reads recorded state, such as the plan of the asset it acts on, no longer comes back as unsupported (“A mapping escaped semantic admission”). It now runs against the read models the specification gives and the ones the events project. A command is denied for an asset whose plan lacks the feature, admitted for one whose plan has it, and denied for an asset with no plan recorded or only another asset’s plan. Both engines agree on each case. (part of #1048)
  • AI (Release v7.151.3): The reverse-engineering skill no longer points readers at an answer fixture for an application used in blind evaluations; its drift-scope self-test now runs on a synthetic application. (#1115)
  • AI (Release v7.151.3): Stage admission reference: STAGE-ESM-017 now agrees with Stage’s key check (restating the key in a from is admitted, overwriting it with another value is refused, and join and every refuse any identifier mapping), and tells readers to key a from by the event’s identifier property instead of relying on no automap. (#1116)
  • AI (Release v7.151.2): Reduce false refusals for routine shell reads, quoted search patterns, read-only sed scripts, filename searches, shellcheck and GitHub CLI filters. Run cratis ai update in your session’s starting checkout to refresh its guards. (#1106)
  • AI (Release v7.151.2): Preserve sensitive-path checks for encoded GitHub API endpoints and recursive search options. (#1106)
  • Chronicle (Release v19.153.2): A kernel node on SQL Server no longer aborts startup when its first read of a database another node is still provisioning is refused with a login failure; the read now retries like the runtime connections do.
  • Chronicle (Release v19.153.1): A kernel with authentication disabled no longer maps the sign-in endpoints. /connect/token and /api/security/login answer 404 instead of failing with a 500 because the identity services are not registered, and clients carry on without a token (#5784)
  • Screenplay (Release v6.15.0): Projection specifications can assert the event source of a given event without a producing command when the view defines one unambiguous identity type. When the identity cannot be decided, PLAY0273 names the event and explains how to supply it. (#1225)
  • AI (Release v7.150.3): Credential-related source paths and non-secret Git path operations no longer trigger false refusals; real secret files and unresolved expansions remain protected. (#1105)
  • Chronicle (Release v19.152.2): Kernel nodes that start at the same time against a shared store no longer fail at startup with An item with the same key has already been added. The development client and the configured bootstrap clients get an application id derived from their client id, so concurrent nodes register the same application, and client records already duplicated by earlier versions are tolerated (#5751)
  • Chronicle (Release v19.152.1): Key lookup now honours key erasure for keys stored under legacy names.
  • Chronicle.Go (Release v0.13.0): Redaction markers and event values whose time offset the Kernel writes as an escaped + now decode instead of failing.
  • AI (Release v7.150.2): The shell write guard classifies only write-target words as protected references, so read-only awk, jq, cat, ls and similar commands with braces or brackets in their program text are no longer refused; commands it cannot parse stay fail-closed, and extended globs and quoted brace spans in write targets are refused (#1041)
  • AI (Release v7.150.2): ls *.csproj, git ls-files *.csproj and similar read-only glob arguments to cat, head, tail, wc, ls, grep and git ls-files are allowed again; writes to dotfile-shaped targets stay refused (#1083)
  • AI (Release v7.150.2): jq filters with [/] and {/}, for example jq '{a: .[0]}', no longer fail the guard’s parser (part of #1052)
  • AI (Release v7.150.2): node .cratis/ai/hooks/scripts/cratis-check-pr.mjs and bash .cratis/ai/hooks/scripts/cratis-cleanup-worktrees.sh with their documented options pass the shell write guard in consuming repositories, while writes to those files stay refused; paths built from variables are not resolved, as the hooks README now states (#1024)
  • AI (Release v7.150.2): The secrets guard treats .env as a protected file only as a whole file stem, so names such as Org.DS.EnvironmentalReporting, Cratis.Environments.Specs and *.environment.txt are no longer refused; .env, .env.local, app.env and .envrc stay protected (#1019)
  • AI (Release v7.150.2): The pinned Screenplay contract is updated to 6.11.0, and the MCP tools reference now lists all 48 tools, including list-storylines.
  • Chronicle (Release v19.150.1): Erasing personal data no longer times out when a kernel hosts many event stores; every event store is now erased concurrently instead of one after another (#5781)
  • AI (Release v7.150.1): The secrets guard treats file names built from command substitutions, including those inside parameter defaults and search patterns, as unresolved, the same way it treats globs. Ordinary substitutions keep working. Run cratis ai update to get the updated hook (#1095)
  • AI (Release v7.150.0): The secrets guard no longer refuses staging or reading ordinary source files whose names contain words such as credential, secret or token (for example Credentials.cs), while real credential files, including credential-named JSON files, stay protected. Run cratis ai update to get the updated hook (#1092)
  • cli (Release v3.126.0): cratis build run no longer refuses a kit installed with cratis build init with “/scaffold/path: ./scaffold is not in the kit”: the installed copy keeps no scaffold, and is now loaded as installed.
  • cli (Release v3.126.0): Agents that connect to MCP servers over HTTP, such as Copilot CLI, now get the Screenplay tools in a build session: local tools are served to them on a loopback address guarded by a per-session token. Before, Copilot CLI refused the tools and built without checking the model or running the slice’s specifications.
  • cli (Release v3.126.0): An agent that ends its turn without writing its outcome, as Copilot CLI does when one of its actions is refused, is asked to go on up to twice instead of the build failing at once.
  • cli (Release v3.126.0): Claude Code build sessions no longer load the user’s own Claude Code settings. A user hook that rewrites shell commands made every command the kit permits fail its permission match, so the agent never built or tested its work; user plugins and the default model no longer change how a slice is built either.
  • Stage (Release v6.0.0): The Scene conversion types that moved to Cratis.Scene.Screenplay are no longer in Cratis.Stage.Contracts
  • Stage (Release v6.0.0): themesWithAccent in @cratis/stage.runtime: the brand color comes from the design system
  • Scene (Release v6.0.0): The fixed theme token vocabulary (themeTokenProperty, applyThemeTokens): components read their look from the design system’s anatomy
  • cli (Release v3.139.0): The CLI no longer builds or publishes a builder image; the images are versioned with and released by Studio.
  • Chronicle.Kotlin (Release v7.10.0): The REOBSERVE_DELAY_MS constant, which leaked into the public Java API from a private companion object, is gone
  • Chronicle (Release v19.155.0): The net8.0 and net9.0 targets of the client packages, as .NET 8 and .NET 9 reach end of support (part of #5763)
  • Choreography (Release v2.4.0): .NET 8 and .NET 9 targets; both reach end of support on November 10, 2026 (#197)
  • Chronicle.Mcp (Release v2.2.0): The .NET 10 build of the MCP server; it is an executable, so it ships only for the latest .NET (#66)
  • AI (Release v7.168.3): Provider, agent, usage and decision management commands and queries now require the Cratis.AI.Management authorization policy. Callers are admitted only when the host’s IAIAdministrators admits them; the default denies everyone.
  • Chronicle (Release v19.169.0): Creating and revoking enrollments and changing subject policies are now refused for a caller that is neither an administrator nor a listed application, also when administrator operations are in audit mode. Before, such a caller was only logged.
  • AI (Release v7.165.1): The agent worker keeps the credential files it writes (MCP service credentials, the cluster kubeconfig and the Pi OAuth login) on in-memory storage instead of the container’s home directory, and writes none of them when no in-memory storage is available (#1065)
  • Screenplay (Release v6.29.1): VS Code event model board: “show source” opens only the .play files the board compiled, including files reached through ../ imports, and ignores any other path the board view sends (#1144)
  • AI (Release v7.159.1): Skills no longer show MongoDB connection-URI examples that resemble credentials (part of #956)
  • Arc (Release v23.5.1): Observable query connections over server-sent events now identify callers by their verified subject, so subscriptions are managed only by the caller that owns the connection
  • AuthProxy (Release v2.64.0): Session context claims arriving from bearer tokens, invite metadata or upstream identity providers are discarded, so callers cannot spoof session start or sign-in provider (#327)
  • Arc.Go (Release v0.1.3): Bump the indirect dependency github.com/klauspost/compress in the MongoDB integration module from v1.19.2 to v1.20.2, fixing a reachable panic vulnerability (GO-2026-6865) in the Zstandard decoder used by the MongoDB driver.
  • Stage.Axon (Release v0.11.0): State, typed, read-dependent and input-mapped policies, and query row narrowing, now deny access (denyAll()) on both the HTTP endpoint and the handler instead of rendering a weaker check (#90)
  • Stage (Release v5.9.0): Updated Aspire to 13.6.5 to address GHSA-f7vh-h5g3-7jrh: rendered multi-service repositories pin the Aspire application host at 13.6.5.
  • Chronicle (Release v19.155.0): Updated Aspire to 13.6.5 to address GHSA-f7vh-h5g3-7jrh.
  • Templates (Release v1.8.4): Updated Aspire to 13.6.5 to address GHSA-f7vh-h5g3-7jrh.
  • Montage (Release v0.1.1): Updated Aspire to 13.6.5 to address GHSA-f7vh-h5g3-7jrh. (#15)
  • AuthProxy (Release v2.60.4): Updated Aspire to 13.6.5 to address GHSA-f7vh-h5g3-7jrh.
  • AuthProxy (Release v2.59.1): Tenant selection redirects now always stay on the proxy’s origin.
  • AI (Release v7.150.2): The secrets guard refuses jq, yq, gojq, jaq and awk-family commands when any word holds an environment-access identifier (env, $ENV, ENVIRON, strenv, envsubst, getenv, PROCINFO) as a whole token, as it already refuses env, printenv and export -p; names such as environment stay readable.
  • AI (Release v7.150.2): The secrets guard protects backup and variant copies of env files such as app.env.old, prod.env.local and config/app.env~; .env.example-style templates, source, project and markup files, and names such as Org.DS.EnvironmentalReporting stay readable.
  • AI (Release v7.150.2): The shell write guard judges a write-target word that carries $, backticks, ~ or parentheses by every suffix after a slash, so $PWD/.cratis/..., $(pwd -P)/.mcp.json and ~+/.mcp.json are treated like the protected relative path; the hooks README states the remaining limits.
  • Arc (Release v23.6.0): Legacy tenant-id, introspection header-trust and redundant section-path aliases, in favor of their supported equivalents. (part of #3778)