@cratis/pi 7.111.0 → 7.113.0

package/package/corpus/harnesses/copilot/instructions/application-profile.instructions.md

@@ -67,7 +67,7 @@ Tagged **[contract]** (framework-enforced) or **[convention]** (house default).
 
 ## Implementation Workflow
 
-- **Starting a brand-new application:** scaffold it instead of hand-writing the skeleton: `dotnet new install Cratis.Templates`, then `dotnet new cratis -n MyApp -o MyApp` (`--language Kotlin|Java`, `--Database MongoDB|PostgreSQL|MsSql|SQLite`; `cratis-aspire` for Aspire; `cratis-chronicle-console` or `cratis-chronicle-web` for a Chronicle client only). Non-interactive runs need `--allow-scripts yes`; the .NET templates target `net10.0`. The template writes `.cratis/ai.json`; run `cratis ai update` afterwards. Its `SomeModule/SomeFeature/Registration/` slice is the house shape. There is no Go, Python or Elixir template (verified at Cratis.Templates `v1.7.4`).
+- **Starting a brand-new application:** scaffold it instead of hand-writing the skeleton: `dotnet new install Cratis.Templates`, then `dotnet new cratis -n MyApp -o MyApp` (`--language Kotlin|Java`, `--Database MongoDB|PostgreSQL|MsSql|SQLite`; `cratis-aspire` for Aspire; `cratis-chronicle-console` or `cratis-chronicle-web` for a Chronicle client only). Non-interactive runs need `--allow-scripts yes`; the .NET templates target `net10.0`. The template writes `.cratis/ai.json`; run `cratis ai update` afterwards. Its `SomeModule/SomeFeature/Registration/` slice is the house shape. There is no Go, Python or Elixir template (verified at Cratis.Templates `v1.8.1`). Since 1.8.0 the `cratis` and `cratis-aspire` .NET app projects emit `<CratisReadProtection>On</CratisReadProtection>`: read models supplied to commands and validators guard the append. Existing apps are not changed by reinstalling the templates.
 - **Phase 0 — Find the contract / choose the level.** Before writing slice code, find what the code must match, and choose the level once for the whole scope.
   1. **Look for a Screenplay model** under the model root (opted in per `general.md` "Model first"; where `cratis-screenplay-modeling-lifecycle` is installed, run its `scripts/model-first-status.mjs` for the decision, root and drafts) for the slice, command, event and read-model names.
   2. **Model level** — an accepted model under the root covers the scope, or the repository is opted in and this scope has no model yet. The `.play` slice and its specs are the contract: change the model first (new behavior starts in discovery), verify it (V1–V3), get an independent review, then render with Stage or gap-fill by hand only what the renderer rejects. Hand-written code stays checked against the model (**cratis-application-slice-conformance**). Never edit Stage-managed output, never implement behavior the model does not state, never change the model to match existing code, never weaken protection to make it compile or render. Start with **cratis-screenplay-event-modeling** (decision rule), then **cratis-screenplay-modeling-lifecycle**. If the Screenplay skills are not installed, say so; do not author `.play` from memory.

package/package/corpus/harnesses/copilot/instructions/pull-requests.instructions.md

@@ -155,6 +155,13 @@ The test is **outward-facing effect, not file location**. A change under `Source
 
 A non-release pull request must satisfy the relevant required checks like any other. Confirm label acceptance and publication suppression against the current workflow contract; do not assume external CI or API state.
 
+### Release-action windows and workflow drift
+
+Batching is opt-in; success with `batched` or `nothing-pending` is not publication.
+Read **cratis-release-notes** before configuring windows, handling a pending-major
+hotfix, or recovering a workflow-drift 403. Major confirmation remains required;
+a workflow-drift recovery differs from the concurrent-tag retry above.
+
 ### Group small related changes into one pull request
 
 Do not open a pull request per task when the tasks belong to the same body of work. Several small merged PRs become several releases, and a stream of near-empty patch releases makes the release history useless for the people it is written for. Collect related work — a set of CI gates, a group of fixes in one area, the steps of one refactor — onto **one branch, as separate commits**, and open **one** pull request. Commits stay one-logical-unit-each; the pull request is the release boundary, and the release boundary should be a coherent, describable change. Joining an open candidate, folding superseded PRs and the cut are in `cratis-engineering-release-trains`.

package/package/corpus/harnesses/copilot/instructions/specs.csharp.instructions.md

@@ -46,13 +46,13 @@ public class when_combining_parts : Specification
 | `void Establish()` | setup, before `Because()` | each class in the chain has its own, run base-first — never call `base.Establish()` |
 | `void Because()` | the single action under test | only in concrete spec files, never in a reusable context |
 | `[Fact] void should_*()` | one assertion per fact | use the `ShouldXxx()` extension methods |
-| `void Destroy()` | teardown after each fact by default | once per eligible class with shared lifecycle opt-in |
+| `void Destroy()` | teardown once per eligible class by default | after each fact when per-fact lifecycle is selected |
 
-The shared lifecycle is the default on xUnit v2 and v3 since 5.0; the package registers the framework, so delete any hand-written `[assembly: Xunit.TestFramework(...)]` (it fails with `CS0579`). Eligible classes derive from `Specification`, have one public parameterless constructor and contain only plain facts. Construction, Establish/Because and Destroy run once; all facts share the instance and must not mutate it. `IDisposable` specifications also share the lifecycle since Cratis.Specifications 4.4.0: one construction and one `Dispose` after the last fact. Initialization failure fails every fact. Theories and `ITestOutputHelper` constructors keep per-fact execution; `[PerFactSpecificationLifecycle]` opts a class out. `CRSPEC0008` (a fact modifies the shared context) is an error by default: move the change into `Establish` or `Because`. See the **cratis-specifications-csharp** skill's shared-lifecycle reference.
+The shared lifecycle is the default on xUnit v2 and v3 since 5.0; the package registers the framework, so delete any hand-written `[assembly: Xunit.TestFramework(...)]` (it fails with `CS0579`). Eligible classes derive from `Specification`, have one public constructor with no arguments or only framework-managed fixture arguments, and contain only plain facts. Construction, Establish/Because and Destroy run once; all facts share the instance and must not mutate it. `IDisposable` specifications also share the lifecycle since Cratis.Specifications 4.4.0: one construction and one `Dispose` after the last fact. Initialization failure fails every fact. Theories and `ITestOutputHelper` constructors keep per-fact execution; `[PerFactSpecificationLifecycle]` opts a class out. `CRSPEC0008` (a fact modifies the shared context) is an error by default: move the change into `Establish` or `Because`. See the **cratis-specifications-csharp** skill's shared-lifecycle reference.
 
 Run specifications as the built executable, not `dotnet test`: restore and build once, then run `bin/<Config>/net10.0/<Project>.Specs`. In a solution that mixes Microsoft.Testing.Platform and VSTest projects, run each project on its own; `dotnet test` on the whole solution does not work there. Filters and the 4.x → 5.0 checklist are in the **cratis-specifications-csharp** skill's [running-specs reference](../../../skills/cratis-specifications-csharp/references/running-specs.md).
 
-CRSPEC0001–CRSPEC0007 are warnings bundled in `.Specifications`, `.XUnit`, `.XUnit.v3`, and `.NUnit`. With warnings as errors, a non-`should_` fact, multiple specs per file (given contexts exempt), a fact on a given context, a `should_` without a test attribute, explicit base lifecycle calls, non-public specs with facts, or `Because` on a given context fail the build. Follow **cratis-specification-by-example**; do not suppress these diagnostics.
+CRSPEC0001–CRSPEC0007 are warnings. Since 4.5 the analyzers ship only in `Cratis.Specifications`, transitively used by the framework packages; excluding analyzers on a framework package does not remove them. Derived xUnit/NUnit test attributes are recognized since 4.1.2. `Given`/`When` are aliases since 4.4 (declaring both aliases for one phase is CRSPEC0009), but house style stays `Establish`/`Because`. With warnings as errors, a non-`should_` fact, multiple specs per file (given contexts exempt), a fact on a given context, a `should_` without a test attribute, explicit base lifecycle calls, non-public specs with facts, or `Because` on a given context fail the build. Follow **cratis-specification-by-example**; do not suppress these diagnostics.
 
 ## Reusable layered contexts
 
@@ -95,7 +95,7 @@ async Task Because() => _error = await Catch.Exception(_sut.DoSomething);
 
 ## Assertion extension methods
 
-From the `Cratis.Specifications.XUnit` package (namespace `Cratis.Specifications`): `.ShouldEqual(expected)`, `.ShouldBeTrue()`, `.ShouldBeFalse()`, `.ShouldBeNull()`, `.ShouldNotBeNull()`, `.ShouldBeEmpty()`, `.ShouldNotBeEmpty()`, `.ShouldContain(item)`, `.ShouldNotContain(item)`, `.ShouldContainOnly(items)`, `.ShouldBeOfExactType<T>()`, `.ShouldBeGreaterThan(n)`, `.ShouldBeLessThan(n)`.
+Since 5.0 assertions live in `Cratis.Specifications`, with types forwarded by each framework package (namespace `Cratis.Specifications`); recompile and keep core/framework packages on the same version: `.ShouldEqual(expected)`, `.ShouldBeTrue()`, `.ShouldBeFalse()`, `.ShouldBeNull()`, `.ShouldNotBeNull()`, `.ShouldBeEmpty()`, `.ShouldNotBeEmpty()`, `.ShouldContain(item)`, `.ShouldNotContain(item)`, `.ShouldContainOnly(items)`, `.ShouldBeOfExactType<T>()`, `.ShouldBeGreaterThan(n)`, `.ShouldBeLessThan(n)`.
 
 Additional helpers include `ShouldNotEqual`, `ShouldBeSame`/`ShouldNotBeSame`, `ShouldMatch(Func<T, bool>)`, `ShouldBeInRange`, inclusive comparisons `ShouldBeGreaterThanOrEqual`/`ShouldBeLessThanOrEqual`, `ShouldContainSingleItem`, `ShouldEachConformTo`, ordered collection `ShouldEqual(IEnumerable<T>)`, collection `ShouldContain(Predicate<T>)`, `ShouldBeAssignableFrom<T>`, and string `ShouldContain(substring, StringComparison)`. `Catch.Exception` accepts `Action` or `Func<Task>`; `Catch.Exception<T>(Action)` catches only T.
 

package/package/corpus/product-sync.json

@@ -171,9 +171,9 @@
         }
       ],
       "synced": {
-        "version": "4.244.0",
-        "date": "2026-10-20",
-        "by": "Cratis/AI#891"
+        "version": "4.245.0",
+        "date": "2026-10-25",
+        "by": "Cratis/AI#820"
       },
       "covers": {
         "skills": [
@@ -201,7 +201,7 @@
         ],
         "rules": []
       },
-      "notes": "Cratis/AI#779: reference-runner capability refusals taught as scoped per specification (introduced in v4.213.2, Cratis/Screenplay#897) from the v4.216.0 tool and MCP documentation and plan source: an unadmitted projection (UnsupportedEventContext, UnsupportedProjectionBlock) marks unsupported only the specifications that reach it or its read model, the others run and planIssues lists deferred issues; application-level issues still block every selected specification; no new render/runtime probe. Prior: Cratis/AI#776: PLAY0802 ReservedStoredName (introduced in v4.213.3, Cratis/Screenplay#893) taught from the v4.216.0 compilers and documentation: stored event source `Default` and stored event stream `All` (ordinal, name or `id` pin) refused at authoring time, a pin away from the reserved name valid, PLAY0273 kept as the binding backstop; no new render/runtime probe. Prior: Cratis/AI#784: standalone Screenplay 4.216.0 pinned; compiler contract replaced by the v4.216.0 release asset (adds the propose-repair destinationIntent v1 schema and PLAY0802 ReservedStoredName). Source-checked decision 0096 and the MCP reference for the explicit author-intent PLAY0470 repair: repair-intents discovery, intentActions feature detection, complete per-production selections, retained production-destination report and identity views, explicit apply and refusals. No new render/runtime probe. Prior: Cratis/AI#771: standalone Screenplay 4.213.0 pinned; regenerated compiler contract is byte-identical to the v4.213.0 release asset and unchanged from 4.212.4. Reviewed the full v4.212.4-v4.213.0 delta against tagged decision 0093 and MCP reference: pre-binding container identities and stable binding/migration continuity, own-slice member substitutions, containerIdentities completeness/ambiguity/collision refusals, retained ambiguous notes, explicit semanticRenames/retirements, binding fixes through MCP, exact reopen exception, notes/identity rollback and exact-ID re-add anchoring. No grammar, binder, ESM or diagnostic-code changes; no new render/runtime probe. Prior: Cratis/AI#772: standalone Screenplay 4.212.4 pinned; regenerated compiler contract is byte-identical to the v4.212.4 release asset. Source-checked joined-event automap/no automap overrides and level fallback in executable binding; PLAY0380 covers only all inside children/nested. No new render/runtime probe. Prior: Cratis/AI#769: standalone Screenplay 4.212.3 pinned; regenerated compiler contract is byte-identical to the v4.212.3 release asset. Source-checked both compilers and projection documentation for PLAY0801 DuplicateEventInProjectionScope: shared from/removal/clear set, separate join set, fresh sets per children/nested/variant level, and no two-row update through repeated from blocks with different keys. No new render/runtime probe. Prior: Cratis/AI#768: standalone Screenplay 4.212.2 pinned; regenerated compiler contract is byte-identical to the v4.212.2 release asset (unchanged from the previous contract). Source-checked v4.212.0 split-model dotted note targets, open-workspace applicationIdentity and complete add/reanchor substitutions; unbound container identities are not claimed. v4.212.1 aligns PLAY0535 collection fields, optional parameters and single-result identity inference. v4.212.2 counts read-only query denials for SPEC004, not SPEC006. No new render/runtime probe. Prior: Cratis/AI#762 and #761: source-checked v4.210.0 and v4.211.0 contracts for PLAY0800 CommandHandlerRequiresAttachment (required typed subject, permanent code-attachment requirement, other PLAY0268 families unchanged), independent reference remove/add batches, located same-text ambiguity conflicts and string MCP conflict/move-report document fields. v4.211.1 mapping changes inspected but excluded from this guidance update at the user's request; no typed PLAY0273 property/type arguments are claimed. Standalone Screenplay 4.211.1 and its compiler contract pinned; the contract is a byte-identical copy of the v4.211.1 release asset. No new render/runtime probe. Prior: Standalone 4.205.0 and byte-identical compiler contract pinned. Cratis/AI#746: Uuid ==/!= in command require and produces when (ESM v28): same-concept rule, bare Uuid against a concept, canonical literals, protected read paths in require only; PLAY0268 (different concepts, ordering, Uuid validation and concept rules, read paths in produces when) and PLAY0273 (non-canonical literal) checked against the 4.205.0 compiler, v28 selection read from the MCP executable-model view; Stage admits exact v1-v21 and v23-v26 pairs so v28 is refused STAGE-ESM-016, not probed against a Stage image; CLI 3.74.0 renders through v26. Prior: Standalone 4.204.0 and byte-identical compiler contract pinned. Cratis/AI#702 and #691: PLAY0690 reducer identity (Screenplay 4.170.0, native compiler only) and the screenplay.json validation gate (Screenplay 4.165.0; cratis screenplay validate reads it from CLI 3.65.0) are taught and probed against the 4.204.0 compiler. Cratis/AI#743: flat composite read-model keys (ESM v27): untyped projection key blocks on root from and remove with, equality-filter lists, single-instance by blocks and per-part fixtures, with PLAY0661/PLAY0662/PLAY0268 refusals checked against the 4.204.0 compiler; Stage origin/main still refuses v27 with STAGE-ESM-016 (stage-rendering.md); Stage v4.135.0 v26 admission (Host and executor run date comparisons; renderer STAGE-ESM-046) was source-checked for this sync; no render or runtime probe. Prior: Standalone 4.201.0 and byte-identical compiler contract pinned. Cratis/AI#733: the ui profile root template, shell options, appearance and new screens default (PLAY0788-PLAY0799, quick fix for the legacy layout line, ui-profiles MCP tool, 44 tools). Cratis/AI#735: chronological Date/DateTime ordering in command conditions and command/property literal validation (ESM v26), UTC tick precision and pre-rule offset validation; then matching remains ordinal. Source-checked Screenplay v4.199.0 commands, diagnostics, interoperability and specifications documentation plus decision 0087. Stage v4.127.1 still refuses v26 with STAGE-ESM-016 (stage-rendering.md and SemanticVersionFeatures.Supports); no render/runtime probe. Cratis/AI#576: prior mechanical compiler catch-up. Language batch #717/#722/#723/#724/#720/#728/#734 teaches atomic reaction batches (v22), described payload handlers (v23), portable linear matching, ordinal text rules (v24), protected command reads (v25), diagnostic arguments and event-source invokes mappings. Facts read at Screenplay v4.198.0 and introducing tags; Stage v4.127.0 admits exact v1-v21 and v23-v25 pairs but refuses v22/v26 and mixed pairs (STAGE-ESM-016), protected reads (044), atomic mode (043) and described handlers (STAGE-IMPL-002), even Stub mode. Stage text rules execute/render; no new renderer/runtime probe or Stage pin uplift. Cratis/AI#706: application navigation regions (module inherit, extend or override), toolbar slice buttons, blueprint template references and sample data packs in cratis-screenplay-ui-composition (references/application-shell.md), with the canonical shell vector and the rejection codes PLAY0710-PLAY0722 and PLAY0740-PLAY0765. Examples moved to the executable-state rules since 4.164: translator reactions in an Automation slice beside the Translate slice (PLAY0694) and the first record of a capture key appended with `when added`. Earlier: Standalone 4.164.0 and byte-identical compiler contract pinned. Cratis/AI#663: one origin per capture (PLAY0687). #668: executable no-event/redelivery v17. #684: concept query-argument validation in every version and query-error assertions v18. #681: executable refusal branches and refusal values v19. #666: proposal summary/severity counts and exact structural source proposals. Generated-concept rules select v20 with PLAY0688/0689 proofs and derived-matches repair; generated secrets and preview strategies remain refused. Release-baseline from-esm admission reads storedName. Standalone binding is not renderer admission: Stage 4.103.0 admits v1-v17 and v19; CLI 3.62.0 bundles Screenplay 4.159.0 / Stage 4.99.0 and renders through v16. Prior evidence remains unless superseded; no new renderer, Docker or browser probe."
+      "notes": "Cratis/AI#820: reviewed v4.245.0 release; protected-read constraint precedence preserved. Review correction: removed unsupported parser-repair and inbound-public refusal release attributions and the incorrect PLAY0136 event-key claim, restoring prior teaching. Published contract asset is byte-identical to the previous snapshot; pin and compatibility entry advanced together. Prior: Cratis/AI#779: reference-runner capability refusals taught as scoped per specification (introduced in v4.213.2, Cratis/Screenplay#897) from the v4.216.0 tool and MCP documentation and plan source: an unadmitted projection (UnsupportedEventContext, UnsupportedProjectionBlock) marks unsupported only the specifications that reach it or its read model, the others run and planIssues lists deferred issues; application-level issues still block every selected specification; no new render/runtime probe. Prior: Cratis/AI#776: PLAY0802 ReservedStoredName (introduced in v4.213.3, Cratis/Screenplay#893) taught from the v4.216.0 compilers and documentation: stored event source `Default` and stored event stream `All` (ordinal, name or `id` pin) refused at authoring time, a pin away from the reserved name valid, PLAY0273 kept as the binding backstop; no new render/runtime probe. Prior: Cratis/AI#784: standalone Screenplay 4.216.0 pinned; compiler contract replaced by the v4.216.0 release asset (adds the propose-repair destinationIntent v1 schema and PLAY0802 ReservedStoredName). Source-checked decision 0096 and the MCP reference for the explicit author-intent PLAY0470 repair: repair-intents discovery, intentActions feature detection, complete per-production selections, retained production-destination report and identity views, explicit apply and refusals. No new render/runtime probe. Prior: Cratis/AI#771: standalone Screenplay 4.213.0 pinned; regenerated compiler contract is byte-identical to the v4.213.0 release asset and unchanged from 4.212.4. Reviewed the full v4.212.4-v4.213.0 delta against tagged decision 0093 and MCP reference: pre-binding container identities and stable binding/migration continuity, own-slice member substitutions, containerIdentities completeness/ambiguity/collision refusals, retained ambiguous notes, explicit semanticRenames/retirements, binding fixes through MCP, exact reopen exception, notes/identity rollback and exact-ID re-add anchoring. No grammar, binder, ESM or diagnostic-code changes; no new render/runtime probe. Prior: Cratis/AI#772: standalone Screenplay 4.212.4 pinned; regenerated compiler contract is byte-identical to the v4.212.4 release asset. Source-checked joined-event automap/no automap overrides and level fallback in executable binding; PLAY0380 covers only all inside children/nested. No new render/runtime probe. Prior: Cratis/AI#769: standalone Screenplay 4.212.3 pinned; regenerated compiler contract is byte-identical to the v4.212.3 release asset. Source-checked both compilers and projection documentation for PLAY0801 DuplicateEventInProjectionScope: shared from/removal/clear set, separate join set, fresh sets per children/nested/variant level, and no two-row update through repeated from blocks with different keys. No new render/runtime probe. Prior: Cratis/AI#768: standalone Screenplay 4.212.2 pinned; regenerated compiler contract is byte-identical to the v4.212.2 release asset (unchanged from the previous contract). Source-checked v4.212.0 split-model dotted note targets, open-workspace applicationIdentity and complete add/reanchor substitutions; unbound container identities are not claimed. v4.212.1 aligns PLAY0535 collection fields, optional parameters and single-result identity inference. v4.212.2 counts read-only query denials for SPEC004, not SPEC006. No new render/runtime probe. Prior: Cratis/AI#762 and #761: source-checked v4.210.0 and v4.211.0 contracts for PLAY0800 CommandHandlerRequiresAttachment (required typed subject, permanent code-attachment requirement, other PLAY0268 families unchanged), independent reference remove/add batches, located same-text ambiguity conflicts and string MCP conflict/move-report document fields. v4.211.1 mapping changes inspected but excluded from this guidance update at the user's request; no typed PLAY0273 property/type arguments are claimed. Standalone Screenplay 4.211.1 and its compiler contract pinned; the contract is a byte-identical copy of the v4.211.1 release asset. No new render/runtime probe. Prior: Standalone 4.205.0 and byte-identical compiler contract pinned. Cratis/AI#746: Uuid ==/!= in command require and produces when (ESM v28): same-concept rule, bare Uuid against a concept, canonical literals, protected read paths in require only; PLAY0268 (different concepts, ordering, Uuid validation and concept rules, read paths in produces when) and PLAY0273 (non-canonical literal) checked against the 4.205.0 compiler, v28 selection read from the MCP executable-model view; Stage admits exact v1-v21 and v23-v26 pairs so v28 is refused STAGE-ESM-016, not probed against a Stage image; CLI 3.74.0 renders through v26. Prior: Standalone 4.204.0 and byte-identical compiler contract pinned. Cratis/AI#702 and #691: PLAY0690 reducer identity (Screenplay 4.170.0, native compiler only) and the screenplay.json validation gate (Screenplay 4.165.0; cratis screenplay validate reads it from CLI 3.65.0) are taught and probed against the 4.204.0 compiler. Cratis/AI#743: flat composite read-model keys (ESM v27): untyped projection key blocks on root from and remove with, equality-filter lists, single-instance by blocks and per-part fixtures, with PLAY0661/PLAY0662/PLAY0268 refusals checked against the 4.204.0 compiler; Stage origin/main still refuses v27 with STAGE-ESM-016 (stage-rendering.md); Stage v4.135.0 v26 admission (Host and executor run date comparisons; renderer STAGE-ESM-046) was source-checked for this sync; no render or runtime probe. Prior: Standalone 4.201.0 and byte-identical compiler contract pinned. Cratis/AI#733: the ui profile root template, shell options, appearance and new screens default (PLAY0788-PLAY0799, quick fix for the legacy layout line, ui-profiles MCP tool, 44 tools). Cratis/AI#735: chronological Date/DateTime ordering in command conditions and command/property literal validation (ESM v26), UTC tick precision and pre-rule offset validation; then matching remains ordinal. Source-checked Screenplay v4.199.0 commands, diagnostics, interoperability and specifications documentation plus decision 0087. Stage v4.127.1 still refuses v26 with STAGE-ESM-016 (stage-rendering.md and SemanticVersionFeatures.Supports); no render/runtime probe. Cratis/AI#576: prior mechanical compiler catch-up. Language batch #717/#722/#723/#724/#720/#728/#734 teaches atomic reaction batches (v22), described payload handlers (v23), portable linear matching, ordinal text rules (v24), protected command reads (v25), diagnostic arguments and event-source invokes mappings. Facts read at Screenplay v4.198.0 and introducing tags; Stage v4.127.0 admits exact v1-v21 and v23-v25 pairs but refuses v22/v26 and mixed pairs (STAGE-ESM-016), protected reads (044), atomic mode (043) and described handlers (STAGE-IMPL-002), even Stub mode. Stage text rules execute/render; no new renderer/runtime probe or Stage pin uplift. Cratis/AI#706: application navigation regions (module inherit, extend or override), toolbar slice buttons, blueprint template references and sample data packs in cratis-screenplay-ui-composition (references/application-shell.md), with the canonical shell vector and the rejection codes PLAY0710-PLAY0722 and PLAY0740-PLAY0765. Examples moved to the executable-state rules since 4.164: translator reactions in an Automation slice beside the Translate slice (PLAY0694) and the first record of a capture key appended with `when added`. Earlier: Standalone 4.164.0 and byte-identical compiler contract pinned. Cratis/AI#663: one origin per capture (PLAY0687). #668: executable no-event/redelivery v17. #684: concept query-argument validation in every version and query-error assertions v18. #681: executable refusal branches and refusal values v19. #666: proposal summary/severity counts and exact structural source proposals. Generated-concept rules select v20 with PLAY0688/0689 proofs and derived-matches repair; generated secrets and preview strategies remain refused. Release-baseline from-esm admission reads storedName. Standalone binding is not renderer admission: Stage 4.103.0 admits v1-v17 and v19; CLI 3.62.0 bundles Screenplay 4.159.0 / Stage 4.99.0 and renders through v16. Prior evidence remains unless superseded; no new renderer, Docker or browser probe."
     },
     {
       "id": "scene",
@@ -331,9 +331,9 @@
       "repository": "Cratis/Arc.Go",
       "packages": [],
       "synced": {
-        "version": "0.1.1",
-        "date": "2026-10-12",
-        "by": "Cratis/AI#620"
+        "version": "0.1.2",
+        "date": "2026-10-25",
+        "by": "Cratis/AI#820"
       },
       "covers": {
         "skills": [
@@ -345,7 +345,7 @@
         ]
       },
       "coverage": "tracked",
-      "notes": "First synced in Cratis/AI#620 at 0.1.1."
+      "notes": "Cratis/AI#820: reviewed v0.1.2 release. Snapshot HEAD handling no longer enumerates bodies; existing root-module guidance promises no HEAD conformance and teaches no body enumeration on HEAD. No teaching update needed; packaging/runtime fix only, no new Go execution evidence."
     },
     {
       "id": "templates",
@@ -353,9 +353,9 @@
       "repository": "Cratis/Templates",
       "packages": [],
       "synced": {
-        "version": "1.7.4",
-        "date": "2026-10-12",
-        "by": "Cratis/AI#620"
+        "version": "1.8.1",
+        "date": "2026-10-25",
+        "by": "Cratis/AI#820"
       },
       "covers": {
         "skills": [],
@@ -364,7 +364,7 @@
         ]
       },
       "coverage": "tracked",
-      "notes": "First synced in Cratis/AI#620 at 1.7.4."
+      "notes": "Cratis/AI#820: reviewed v1.8.0-v1.8.1. Tagged Cratis and CratisAspire app csproj sources enable CratisReadProtection On; application-profile now distinguishes new scaffolds from existing apps. 1.8.1 package metadata has no teaching impact. No scaffold execution claimed."
     },
     {
       "id": "fundamentals",
@@ -381,9 +381,9 @@
         }
       ],
       "synced": {
-        "version": "7.25.0",
-        "date": "2026-10-15",
-        "by": "Cratis/AI#576"
+        "version": "7.26.1",
+        "date": "2026-10-25",
+        "by": "Cratis/AI#820"
       },
       "covers": {
         "skills": [
@@ -399,7 +399,7 @@
           "concepts.md"
         ]
       },
-      "notes": "Source-checked v7.25.0: IGeneratable/IGeneratableInContext, GenerationContext, UUID/ULID/TypeID/NanoID/bytes and finite GenerateValue.Pattern overloads with optional Checksum, inclusive Int64 Integer, and HasValidChecksum. Pattern date segments use captured UTC time; check digits add no entropy or authorization and do not automatically add validation. No Stage version uplift or generated-secret admission is implied."
+      "notes": "Cratis/AI#820: reviewed v7.25.1-v7.26.1, all four releases. Tagged DerivedTypes.For(ITypes) weak per-universe caching and generator build fixes taught in type-discovery; logo and test-package packing are metadata-only. No runtime probe. Prior: Source-checked v7.25.0: IGeneratable/IGeneratableInContext, GenerationContext, UUID/ULID/TypeID/NanoID/bytes and finite GenerateValue.Pattern overloads with optional Checksum, inclusive Int64 Integer, and HasValidChecksum. Pattern date segments use captured UTC time; check digits add no entropy or authorization and do not automatically add validation. No Stage version uplift or generated-secret admission is implied."
     },
     {
       "id": "components",
@@ -412,9 +412,9 @@
         }
       ],
       "synced": {
-        "version": "4.26.4",
-        "date": "2026-10-12",
-        "by": "Cratis/AI#620"
+        "version": "4.38.0",
+        "date": "2026-10-25",
+        "by": "Cratis/AI#820"
       },
       "covers": {
         "skills": [
@@ -432,7 +432,7 @@
           "components.md"
         ]
       },
-      "notes": "Initial historical floor recorded on 2026-10-12 by Cratis/AI#619; date records this inventory, not a new product verification."
+      "notes": "Cratis/AI#820: reviewed all 15 stable releases v4.27.0-v4.38.0. Tagged docs/source and release notes inform serverQuery, paginator localization, query-state/selection, schema preservation/generated/UUID, GuidField, dialog focus/dismissal, non-modal dates and router integration. Adapter unchecked rendering is a runtime fix; package metadata requires no teaching update. Source review only; prior browser evidence not extended."
     },
     {
       "id": "chronicle-go",
@@ -440,9 +440,9 @@
       "repository": "Cratis/Chronicle.Go",
       "packages": [],
       "synced": {
-        "version": "0.9.1",
-        "date": "2026-10-12",
-        "by": "Cratis/AI#620"
+        "version": "0.11.1",
+        "date": "2026-10-25",
+        "by": "Cratis/AI#820"
       },
       "covers": {
         "skills": [
@@ -454,7 +454,7 @@
         ]
       },
       "coverage": "tracked",
-      "notes": "First synced in Cratis/AI#620 at 0.9.1."
+      "notes": "Cratis/AI#820: reviewed v0.10.0, v0.11.0 and v0.11.1. Teach FastForward, first-registration StartAtTail and kernel-first upgrade to the verified 19.70.0 decision-guard profile. Documentation metadata needs no teaching update; generated occurrences contracts do not establish a new public workflow. No Go execution probe."
     },
     {
       "id": "ante",
@@ -493,9 +493,9 @@
       "repository": "Cratis/Screenplay.CritterStack",
       "packages": [],
       "synced": {
-        "version": "0.26.0",
-        "date": "2026-10-12",
-        "by": "Cratis/AI#620"
+        "version": "0.26.1",
+        "date": "2026-10-25",
+        "by": "Cratis/AI#820"
       },
       "covers": {
         "skills": [
@@ -504,7 +504,7 @@
         "rules": []
       },
       "coverage": "tracked",
-      "notes": "First synced in Cratis/AI#620 at 0.26.0."
+      "notes": "Cratis/AI#820: reviewed v0.26.1. No teaching update needed: NuGet metadata and the repository's Specifications 5/xUnit v3 test runner migration do not change the CritterStack renderer/toolchain contract taught by this family. No backend parity or new execution claim."
     },
     {
       "id": "chronicle-typescript",
@@ -517,9 +517,9 @@
         }
       ],
       "synced": {
-        "version": "6.51.0",
-        "date": "2026-10-12",
-        "by": "Cratis/AI#620"
+        "version": "6.53.1",
+        "date": "2026-10-25",
+        "by": "Cratis/AI#820"
       },
       "covers": {
         "skills": [
@@ -527,7 +527,7 @@
         ],
         "rules": []
       },
-      "notes": "Initial historical floor recorded on 2026-10-12 by Cratis/AI#619; date records this inventory, not a new product verification."
+      "notes": "Cratis/AI#820: reviewed all five releases v6.51.1-v6.53.1. Teach gRPC limits, FastForward, first-registration StartAtTail, class defaults and child all-event projection fixes with explicit kernel/Fundamentals requirements and replay action. Release review only; no new TypeScript execution evidence."
     },
     {
       "id": "release-action",
@@ -535,9 +535,9 @@
       "repository": "Cratis/release-action",
       "packages": [],
       "synced": {
-        "version": "1.4.2",
-        "date": "2026-10-12",
-        "by": "Cratis/AI#620"
+        "version": "1.5.1",
+        "date": "2026-10-25",
+        "by": "Cratis/AI#820"
       },
       "covers": {
         "skills": [
@@ -548,7 +548,7 @@
         ]
       },
       "coverage": "tracked",
-      "notes": "First synced in Cratis/AI#620 at 1.4.2."
+      "notes": "Cratis/AI#820: reviewed v1.4.3, v1.5.0 and v1.5.1. Skill and PR policy now distinguish workflow-drift 403 recovery from stale-tag retry, opt-in batching/defaults/outputs, combined summaries and corrected pending-major hotfix behavior. No workflow activation or release execution claimed."
     },
     {
       "id": "screenplay-generation",
@@ -556,9 +556,9 @@
       "repository": "Cratis/Screenplay.Generation",
       "packages": [],
       "synced": {
-        "version": "0.18.1",
-        "date": "2026-10-12",
-        "by": "Cratis/AI#620"
+        "version": "0.18.2",
+        "date": "2026-10-25",
+        "by": "Cratis/AI#820"
       },
       "covers": {
         "skills": [
@@ -567,7 +567,7 @@
         "rules": []
       },
       "coverage": "tracked",
-      "notes": "First synced in Cratis/AI#620 at 0.18.1."
+      "notes": "Cratis/AI#820: reviewed v0.18.2. No teaching update needed: package metadata and native .NET 10 Specifications 5 test execution do not change generation APIs or the retained .NET 8/9/10 library targets. No renderer parity or execution uplift inferred."
     },
     {
       "id": "chronicle-elixir",
@@ -580,9 +580,9 @@
         }
       ],
       "synced": {
-        "version": "3.13.0",
-        "date": "2026-10-15",
-        "by": "Cratis/AI#719"
+        "version": "3.14.3",
+        "date": "2026-10-25",
+        "by": "Cratis/AI#820"
       },
       "covers": {
         "skills": [
@@ -592,7 +592,7 @@
           "elixir.md"
         ]
       },
-      "notes": "Synced to the v3.13.0 tag: decision reads, Chronicle.Testing, captures, discovery drift, standalone constraints, children collections, concurrency scopes and observability."
+      "notes": "Cratis/AI#820: reviewed all four releases v3.14.0-v3.14.3. Teach first-registration start_at_tail/kernel floor, client crash-report redaction and decide callback rejection/cleanup. Hex metadata and shared-doc language tabs need no additional API teaching. Tagged reactor/event/testing docs inspected; retained in-memory projection limits still apply. No new execution evidence. Prior: Synced to the v3.13.0 tag: decision reads, Chronicle.Testing, captures, discovery drift, standalone constraints, children collections, concurrency scopes and observability."
     },
     {
       "id": "authproxy",
@@ -600,9 +600,9 @@
       "repository": "Cratis/AuthProxy",
       "packages": [],
       "synced": {
-        "version": "2.30.5",
-        "date": "2026-10-12",
-        "by": "Cratis/AI#620"
+        "version": "2.32.4",
+        "date": "2026-10-25",
+        "by": "Cratis/AI#820"
       },
       "covers": {
         "skills": [
@@ -611,7 +611,7 @@
         "rules": []
       },
       "coverage": "tracked",
-      "notes": "First synced in Cratis/AI#620 at 2.30.5."
+      "notes": "Cratis/AI#820: reviewed all eight releases v2.31.0-v2.32.4. Teach opt-in multi-host session/callback boundaries, search-index exclusion and invitation placeholders. Existing canonical tenant header guidance remains correct for bearer routes; registration/cookie fixes need no workaround. Package/tooling/test-runner updates have no further identity API teaching delta. Release review, not a deployed ingress probe."
     },
     {
       "id": "fundamentals-go",
@@ -619,9 +619,9 @@
       "repository": "Cratis/Fundamentals.Go",
       "packages": [],
       "synced": {
-        "version": "0.3.2",
-        "date": "2026-10-12",
-        "by": "Cratis/AI#620"
+        "version": "0.3.3",
+        "date": "2026-10-25",
+        "by": "Cratis/AI#820"
       },
       "covers": {
         "skills": [
@@ -633,7 +633,7 @@
         ]
       },
       "coverage": "tracked",
-      "notes": "First synced in Cratis/AI#620 at 0.3.2."
+      "notes": "Cratis/AI#820: reviewed v0.3.3. No teaching update needed: pkg.go.dev summary and documentation links change no concept, serialization, validation or Go engineering API. Existing runtime verification remains historical."
     },
     {
       "id": "chronicle-kotlin",
@@ -646,9 +646,9 @@
         }
       ],
       "synced": {
-        "version": "6.13.0",
-        "date": "2026-10-12",
-        "by": "Cratis/AI#620"
+        "version": "7.1.0",
+        "date": "2026-10-25",
+        "by": "Cratis/AI#820"
       },
       "covers": {
         "skills": [
@@ -656,7 +656,7 @@
         ],
         "rules": []
       },
-      "notes": "Initial historical floor recorded on 2026-10-12 by Cratis/AI#619; date records this inventory, not a new product verification."
+      "notes": "Cratis/AI#820: reviewed all seven releases v6.13.1-v7.1.0 and tagged concept/correlation/annotation sources. Teach breaking Fundamentals imports/value() and CorrelationId migration, shared thread-bound context, enum ordinals, StartAtTail/FastForward kernel floors and message limits. Maven metadata has no teaching delta. Earlier compile/runtime evidence remains historical."
     },
     {
       "id": "arc-kotlin",
@@ -669,9 +669,9 @@
         }
       ],
       "synced": {
-        "version": "7.7.0",
-        "date": "2026-10-12",
-        "by": "Cratis/AI#620"
+        "version": "7.8.1",
+        "date": "2026-10-25",
+        "by": "Cratis/AI#820"
       },
       "covers": {
         "skills": [
@@ -684,7 +684,7 @@
         ],
         "rules": []
       },
-      "notes": "Initial historical floor recorded on 2026-10-12 by Cratis/AI#619; date records this inventory, not a new product verification."
+      "notes": "Cratis/AI#820: reviewed v7.7.1, v7.8.0 and v7.8.1 with tagged ConceptAs and validator sources. Teach shared Fundamentals concepts/value(), compatible legacy Arc validators and fixed FundamentalsConceptValidator exclusions. Maven metadata/build dependencies need no further teaching update. No Kotlin execution uplift."
     },
     {
       "id": "prompter",
@@ -755,9 +755,9 @@
         }
       ],
       "synced": {
-        "version": "4.1.1",
-        "date": "2026-10-12",
-        "by": "Cratis/AI#620"
+        "version": "5.0.3",
+        "date": "2026-10-25",
+        "by": "Cratis/AI#820"
       },
       "covers": {
         "skills": [
@@ -771,7 +771,7 @@
           "specs.md"
         ]
       },
-      "notes": "The C# skill states 4.1.1; other skills use 4.x or unversioned test-framework evidence, not an exact older release. Initial historical floor recorded on 2026-10-12 by Cratis/AI#619; date records this inventory, not a new product verification."
+      "notes": "Cratis/AI#820: reviewed all ten stable releases v4.1.2-v5.0.3 and tagged 5.0.2 upgrade/README. The final REST drift check found newly released 5.0.3; teach its separate native-runner class teardown failure outcome. Existing 5.x executable guidance retained; repair contradictory teardown/fixture/analyzer teaching, document ValueTask and aliases, assertion migration and Received.InOrder exception. New runner/resources remain experimental/opt-in. NuGet logo and XML-registration fix need no workflow workaround; TypeScript/scenario families have no API change from this product. No new .NET execution claim."
     },
     {
       "id": "narrator",
@@ -779,9 +779,9 @@
       "repository": "Cratis/Narrator",
       "packages": [],
       "synced": {
-        "version": "3.0.2",
-        "date": "2026-10-12",
-        "by": "Cratis/AI#620"
+        "version": "3.0.3",
+        "date": "2026-10-25",
+        "by": "Cratis/AI#820"
       },
       "covers": {
         "skills": [
@@ -790,7 +790,7 @@
         "rules": []
       },
       "coverage": "tracked",
-      "notes": "First synced in Cratis/AI#620 at 3.0.2."
+      "notes": "Cratis/AI#820: reviewed v3.0.3. No teaching update needed: the Marketplace documentation link changes neither Narrator capture behavior nor the Chronicle CLI operations taught by this family. No new CLI or extension execution evidence."
     },
     {
       "id": "ai-distribution",
@@ -817,9 +817,9 @@
       "repository": "Cratis/Prologue",
       "packages": [],
       "synced": {
-        "version": "2.0.0",
-        "date": "2026-10-12",
-        "by": "Cratis/AI#620"
+        "version": "2.0.5",
+        "date": "2026-10-25",
+        "by": "Cratis/AI#820"
       },
       "covers": {
         "skills": [
@@ -827,7 +827,7 @@
         ],
         "rules": []
       },
-      "notes": "Initial historical floor recorded on 2026-10-12 by Cratis/AI#619; date records this inventory, not a new product verification."
+      "notes": "Cratis/AI#820: reviewed all five releases v2.0.1-v2.0.5. Teach security upgrade, native arm64 images and repaired no-LLM emission while retaining executable model validation and disclosure safeguards. Package metadata, Fundamentals runtime bump and repository spec migration require no further extraction recipe. No new capture/interpret execution evidence."
     },
     {
       "id": "lens",
@@ -853,9 +853,9 @@
       "repository": "Cratis/Architecture",
       "packages": [],
       "synced": {
-        "version": "1.0.2",
-        "date": "2026-10-12",
-        "by": "Cratis/AI#620"
+        "version": "1.0.3",
+        "date": "2026-10-25",
+        "by": "Cratis/AI#820"
       },
       "covers": {
         "skills": [],
@@ -864,7 +864,7 @@
         ]
       },
       "coverage": "tracked",
-      "notes": "First synced in Cratis/AI#620 at 1.0.2; analyzer guidance lives in rules/csharp.md."
+      "notes": "Analyzer guidance lives in rules/csharp.md. Cratis/AI#820: reviewed v1.0.3. No teaching update needed: NuGet author, icon, tags, README and documentation link changes alter no Architecture attributes, analyzer rules or C# conventions. No new analyzer execution evidence."
     },
     {
       "id": "dockerfiles",

package/package/corpus/rules/application-profile.md

@@ -66,7 +66,7 @@ Tagged **[contract]** (framework-enforced) or **[convention]** (house default).
 
 ## Implementation Workflow
 
-- **Starting a brand-new application:** scaffold it instead of hand-writing the skeleton: `dotnet new install Cratis.Templates`, then `dotnet new cratis -n MyApp -o MyApp` (`--language Kotlin|Java`, `--Database MongoDB|PostgreSQL|MsSql|SQLite`; `cratis-aspire` for Aspire; `cratis-chronicle-console` or `cratis-chronicle-web` for a Chronicle client only). Non-interactive runs need `--allow-scripts yes`; the .NET templates target `net10.0`. The template writes `.cratis/ai.json`; run `cratis ai update` afterwards. Its `SomeModule/SomeFeature/Registration/` slice is the house shape. There is no Go, Python or Elixir template (verified at Cratis.Templates `v1.7.4`).
+- **Starting a brand-new application:** scaffold it instead of hand-writing the skeleton: `dotnet new install Cratis.Templates`, then `dotnet new cratis -n MyApp -o MyApp` (`--language Kotlin|Java`, `--Database MongoDB|PostgreSQL|MsSql|SQLite`; `cratis-aspire` for Aspire; `cratis-chronicle-console` or `cratis-chronicle-web` for a Chronicle client only). Non-interactive runs need `--allow-scripts yes`; the .NET templates target `net10.0`. The template writes `.cratis/ai.json`; run `cratis ai update` afterwards. Its `SomeModule/SomeFeature/Registration/` slice is the house shape. There is no Go, Python or Elixir template (verified at Cratis.Templates `v1.8.1`). Since 1.8.0 the `cratis` and `cratis-aspire` .NET app projects emit `<CratisReadProtection>On</CratisReadProtection>`: read models supplied to commands and validators guard the append. Existing apps are not changed by reinstalling the templates.
 - **Phase 0 — Find the contract / choose the level.** Before writing slice code, find what the code must match, and choose the level once for the whole scope.
   1. **Look for a Screenplay model** under the model root (opted in per `general.md` "Model first"; where `cratis-screenplay-modeling-lifecycle` is installed, run its `scripts/model-first-status.mjs` for the decision, root and drafts) for the slice, command, event and read-model names.
   2. **Model level** — an accepted model under the root covers the scope, or the repository is opted in and this scope has no model yet. The `.play` slice and its specs are the contract: change the model first (new behavior starts in discovery), verify it (V1–V3), get an independent review, then render with Stage or gap-fill by hand only what the renderer rejects. Hand-written code stays checked against the model (**cratis-application-slice-conformance**). Never edit Stage-managed output, never implement behavior the model does not state, never change the model to match existing code, never weaken protection to make it compile or render. Start with **cratis-screenplay-event-modeling** (decision rule), then **cratis-screenplay-modeling-lifecycle**. If the Screenplay skills are not installed, say so; do not author `.play` from memory.

package/package/corpus/rules/pull-requests.md

@@ -154,6 +154,13 @@ The test is **outward-facing effect, not file location**. A change under `Source
 
 A non-release pull request must satisfy the relevant required checks like any other. Confirm label acceptance and publication suppression against the current workflow contract; do not assume external CI or API state.
 
+### Release-action windows and workflow drift
+
+Batching is opt-in; success with `batched` or `nothing-pending` is not publication.
+Read **cratis-release-notes** before configuring windows, handling a pending-major
+hotfix, or recovering a workflow-drift 403. Major confirmation remains required;
+a workflow-drift recovery differs from the concurrent-tag retry above.
+
 ### Group small related changes into one pull request
 
 Do not open a pull request per task when the tasks belong to the same body of work. Several small merged PRs become several releases, and a stream of near-empty patch releases makes the release history useless for the people it is written for. Collect related work — a set of CI gates, a group of fixes in one area, the steps of one refactor — onto **one branch, as separate commits**, and open **one** pull request. Commits stay one-logical-unit-each; the pull request is the release boundary, and the release boundary should be a coherent, describable change. Joining an open candidate, folding superseded PRs and the cut are in `cratis-engineering-release-trains`.

package/package/corpus/rules/specs.csharp.md

@@ -45,13 +45,13 @@ public class when_combining_parts : Specification
 | `void Establish()` | setup, before `Because()` | each class in the chain has its own, run base-first — never call `base.Establish()` |
 | `void Because()` | the single action under test | only in concrete spec files, never in a reusable context |
 | `[Fact] void should_*()` | one assertion per fact | use the `ShouldXxx()` extension methods |
-| `void Destroy()` | teardown after each fact by default | once per eligible class with shared lifecycle opt-in |
+| `void Destroy()` | teardown once per eligible class by default | after each fact when per-fact lifecycle is selected |
 
-The shared lifecycle is the default on xUnit v2 and v3 since 5.0; the package registers the framework, so delete any hand-written `[assembly: Xunit.TestFramework(...)]` (it fails with `CS0579`). Eligible classes derive from `Specification`, have one public parameterless constructor and contain only plain facts. Construction, Establish/Because and Destroy run once; all facts share the instance and must not mutate it. `IDisposable` specifications also share the lifecycle since Cratis.Specifications 4.4.0: one construction and one `Dispose` after the last fact. Initialization failure fails every fact. Theories and `ITestOutputHelper` constructors keep per-fact execution; `[PerFactSpecificationLifecycle]` opts a class out. `CRSPEC0008` (a fact modifies the shared context) is an error by default: move the change into `Establish` or `Because`. See the **cratis-specifications-csharp** skill's shared-lifecycle reference.
+The shared lifecycle is the default on xUnit v2 and v3 since 5.0; the package registers the framework, so delete any hand-written `[assembly: Xunit.TestFramework(...)]` (it fails with `CS0579`). Eligible classes derive from `Specification`, have one public constructor with no arguments or only framework-managed fixture arguments, and contain only plain facts. Construction, Establish/Because and Destroy run once; all facts share the instance and must not mutate it. `IDisposable` specifications also share the lifecycle since Cratis.Specifications 4.4.0: one construction and one `Dispose` after the last fact. Initialization failure fails every fact. Theories and `ITestOutputHelper` constructors keep per-fact execution; `[PerFactSpecificationLifecycle]` opts a class out. `CRSPEC0008` (a fact modifies the shared context) is an error by default: move the change into `Establish` or `Because`. See the **cratis-specifications-csharp** skill's shared-lifecycle reference.
 
 Run specifications as the built executable, not `dotnet test`: restore and build once, then run `bin/<Config>/net10.0/<Project>.Specs`. In a solution that mixes Microsoft.Testing.Platform and VSTest projects, run each project on its own; `dotnet test` on the whole solution does not work there. Filters and the 4.x → 5.0 checklist are in the **cratis-specifications-csharp** skill's [running-specs reference](../skills/cratis-specifications-csharp/references/running-specs.md).
 
-CRSPEC0001–CRSPEC0007 are warnings bundled in `.Specifications`, `.XUnit`, `.XUnit.v3`, and `.NUnit`. With warnings as errors, a non-`should_` fact, multiple specs per file (given contexts exempt), a fact on a given context, a `should_` without a test attribute, explicit base lifecycle calls, non-public specs with facts, or `Because` on a given context fail the build. Follow **cratis-specification-by-example**; do not suppress these diagnostics.
+CRSPEC0001–CRSPEC0007 are warnings. Since 4.5 the analyzers ship only in `Cratis.Specifications`, transitively used by the framework packages; excluding analyzers on a framework package does not remove them. Derived xUnit/NUnit test attributes are recognized since 4.1.2. `Given`/`When` are aliases since 4.4 (declaring both aliases for one phase is CRSPEC0009), but house style stays `Establish`/`Because`. With warnings as errors, a non-`should_` fact, multiple specs per file (given contexts exempt), a fact on a given context, a `should_` without a test attribute, explicit base lifecycle calls, non-public specs with facts, or `Because` on a given context fail the build. Follow **cratis-specification-by-example**; do not suppress these diagnostics.
 
 ## Reusable layered contexts
 
@@ -94,7 +94,7 @@ async Task Because() => _error = await Catch.Exception(_sut.DoSomething);
 
 ## Assertion extension methods
 
-From the `Cratis.Specifications.XUnit` package (namespace `Cratis.Specifications`): `.ShouldEqual(expected)`, `.ShouldBeTrue()`, `.ShouldBeFalse()`, `.ShouldBeNull()`, `.ShouldNotBeNull()`, `.ShouldBeEmpty()`, `.ShouldNotBeEmpty()`, `.ShouldContain(item)`, `.ShouldNotContain(item)`, `.ShouldContainOnly(items)`, `.ShouldBeOfExactType<T>()`, `.ShouldBeGreaterThan(n)`, `.ShouldBeLessThan(n)`.
+Since 5.0 assertions live in `Cratis.Specifications`, with types forwarded by each framework package (namespace `Cratis.Specifications`); recompile and keep core/framework packages on the same version: `.ShouldEqual(expected)`, `.ShouldBeTrue()`, `.ShouldBeFalse()`, `.ShouldBeNull()`, `.ShouldNotBeNull()`, `.ShouldBeEmpty()`, `.ShouldNotBeEmpty()`, `.ShouldContain(item)`, `.ShouldNotContain(item)`, `.ShouldContainOnly(items)`, `.ShouldBeOfExactType<T>()`, `.ShouldBeGreaterThan(n)`, `.ShouldBeLessThan(n)`.
 
 Additional helpers include `ShouldNotEqual`, `ShouldBeSame`/`ShouldNotBeSame`, `ShouldMatch(Func<T, bool>)`, `ShouldBeInRange`, inclusive comparisons `ShouldBeGreaterThanOrEqual`/`ShouldBeLessThanOrEqual`, `ShouldContainSingleItem`, `ShouldEachConformTo`, ordered collection `ShouldEqual(IEnumerable<T>)`, collection `ShouldContain(Predicate<T>)`, `ShouldBeAssignableFrom<T>`, and string `ShouldContain(substring, StringComparison)`. `Catch.Exception` accepts `Action` or `Func<Task>`; `Catch.Exception<T>(Action)` catches only T.
 

package/package/corpus/skills/cratis-arc-authentication-authorization-and-identity/references/authproxy.md

@@ -23,6 +23,32 @@ The headers are **not signed**. A backend cannot tell a request that came throug
 
 `IdentityVerification` on an AuthProxy service defaults to `Required` (fail closed). Only a `2xx` with `"isAuthorized": true` admits the caller. A `404`, an unreachable backend, a timeout (default ten seconds), any other non-`2xx`, an empty or unparseable body, a missing verdict, or `isAuthorized: false` all deny. The earlier `BestEffort` mode denied only on `403`. Consequently your `IProvideIdentityDetails` result is the admission verdict at the proxy, not only display data: return `IsUserAuthorized = false` deliberately, and keep the endpoint reachable and fast. A service can opt back into `BestEffort` explicitly; do not do that to hide a broken identity endpoint.
 
+## Multi-host sessions are opt-in
+
+Requires AuthProxy 2.32.4 for the multi-host/crawler/invitation contract below; check the deployed version, or retain host-only sessions and the older error-page contract.
+
+Defaults stay host-only with cookie name
+`.Cratis.AuthProxy.Auth.v2`, per-host handshakes and relative return URLs.
+`Session:CookieDomain` shares sessions beneath a parent domain;
+`Session:CookieName` isolates independent deployments. `SignIn:CallbackHost`
+centralizes OAuth/OIDC handshakes and requires the cookie domain. Restrict
+`AllowedHosts`; never broaden hosts merely to make shared cookies work.
+
+The callback and declared service hosts must lie inside the cookie domain;
+`SubHost` tenant resolution cannot be combined with it. Absolute returns require
+the callback host and an allowed origin inside that domain on the request's
+scheme; otherwise they reduce to a local path. Invitations, credential links and
+registration still start on their original host and need provider callbacks
+there. Use the product's one-proxy/several-hosts migration guide, not an inferred
+cross-domain cookie recipe.
+
+`AuthProxy:SearchIndexing:Exclude` optionally serves anonymous
+`robots.txt` and adds `X-Robots-Tag: noindex, nofollow`. It is off by default and
+is a crawler policy, not authorization. Invitation error-page tokens
+`{{invitedEmail}}` and `{{assertedEmail}}` are blank for addresses outside ASCII
+letters, digits and `._+-@`; do not assume these placeholders always contain text.
+Signed-in `/register` forwarding needs no host workaround.
+
 ## Tenants and services
 
 AuthProxy resolves the tenant through ordered strategies under `Cratis:AuthProxy:TenantResolutions` (`Host`, `Claim`, `Route`, `Specified`, `Default`, `SubHost`, `Selection`). The result reaches the backend as `x-cratis-tenant-id`, which is Arc's default tenant header, so an Arc application behind AuthProxy needs no tenancy configuration and the `UseHeaderTenancy("Tenant-ID")` workaround seen in older applications can be removed.

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

@@ -45,6 +45,17 @@ import { Dialog } from '@cratis/components/Dialogs';
 import { DialogProps, DialogResult, useDialog } from '@cratis/arc.react/dialogs';
 ```
 
+## Guid command fields
+
+Requires Components 4.31.0 and matching Arc/Arc React 22.19.1 for GuidField invalid-draft execution blocking; check `yarn why @cratis/components` and `yarn why @cratis/arc.react`, or keep a host-validated field.
+
+Opt into `GuidField` from `@cratis/components/CommandForm`. It binds native
+Fundamentals `Guid` values, accepts partial text drafts and never generates an
+identifier. Register it once through `registerFieldTypeProvider` for
+`AutoCommandForm`; it is not a built-in provider. Invalid drafts clear the bound
+value. Preserve host-set errors and use `resetKey` to discard an unchanged empty
+value's draft.
+
 ## Initial focus
 
 `DialogInitialFocus.Confirm` is the default and arms the confirm button, so a destructive dialog uses `DialogInitialFocus.Cancel`. Read [dialogs.md](references/dialogs.md) for the three options.

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

@@ -183,6 +183,21 @@ when omission is invalid for the selected query.
 
 ### `ConceptValidator<TConcept>`
 
+Requires Arc.Kotlin 7.8.0 for shared Fundamentals concepts and their validators; check `./gradlew dependencies`, or retain the legacy Arc concepts and validators until upgrading.
+
+Prefer `io.cratis.fundamentals.concepts.ConceptAs` for new concepts and
+`FundamentalsConceptValidator<TConcept>` for their rules. It implements
+`ModelValidator<TConcept>` and exposes `conceptType` plus
+`validate(concept): List<ValidationResult>`; read the primitive via `value()`.
+JSON, validation, proxy generation, Spring conversion, Chronicle bridging and
+testing recognize the shared concept type. The old Arc `ConceptAs` extends it
+and is deprecated, as is `ArcCamelCase` (use Fundamentals `toCamelCase`).
+Existing Arc concepts/validators keep compiling and linking unchanged.
+
+The legacy Arc concept example below remains valid with `ConceptValidator` and
+its `value` property; do not copy that property shape to a new Fundamentals-only
+concept, whose interface method is `value()`.
+
 A reusable invariant on a `ConceptAs<T>` concept type, walked automatically
 wherever that concept type appears — command, nested model, collection,
 array, or map — without each owner repeating the rule. Matching uses
@@ -206,9 +221,11 @@ Jakarta `Validator` bean. Exclude one direct edge deliberately with
 Java record component/field) whose *declared* type implements `ConceptAs`. A
 scalar root, a collection element, or a nested path cannot be excluded this
 way — register the nested owner type and its direct member instead. Excluding
-an edge suppresses only `ConceptValidator` execution there; owner rules, exact
-`ModelValidator` rules, Jakarta constraints, and root typed validators still
-run.
+an edge suppresses concept-rule execution there, including
+`FundamentalsConceptValidator`; owner rules, exact `ModelValidator` rules,
+Jakarta constraints, and root typed validators still run.
+
+Requires Arc.Kotlin 7.8.1 for exclusions to suppress FundamentalsConceptValidator; check `./gradlew dependencies`, or upgrade before relying on a shared-concept exclusion.
 
 ### `ModelValidator<T>`
 

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

@@ -103,6 +103,12 @@ channel exists return `{:error, :not_connected}`.
 
 ## Authentication and TLS
 
+Requires Chronicle.Elixir 3.14.1 for client crash-report redaction; check `mix deps`, or treat older crash reports as potentially secret-bearing and upgrade before sharing them.
+
+The client Logger filter redacts authentication secrets and gRPC/Mint request-header
+state from crash reports; no application-level filter is needed for those client
+reports. This does not authorize logging credentials in your own code.
+
 Use `ConnectionString.development()` locally: `default()` supplies **no
 credentials**, so an authentication-required development kernel never lets it
 reach `:registered`. Production uses URL userinfo `client-id:secret@host` or
@@ -196,6 +202,12 @@ failure.
 
 ### Reactors
 
+Requires Chronicle.Elixir 3.14.0, contracts 19.70 and kernel 19.70.0 for start_at_tail; check `mix deps` and the server version, or retain initial catch-up until upgraded.
+
+`use Chronicle.Reactors.Reactor, start_at_tail: true` skips history only on first
+registration; an existing reactor keeps its position. `once_only` does not skip
+initial catch-up. An older server ignores the flag and catches up from the beginning.
+
 Read [references/reactor-example.md](references/reactor-example.md) when you need a worked reactor module.
 
 - **`@handles` is an accumulating module attribute** declaring the subscription;

package/package/corpus/skills/cratis-chronicle-client-elixir/references/decision-reads.md

@@ -3,6 +3,16 @@
 
 # Decision reads and the dynamic consistency boundary
 
+Requires Chronicle.Elixir 3.14.2 for the rejection/cleanup behavior below; check `mix deps`, or upgrade before relying on a rejected callback to discard buffered events.
+
+A `Chronicle.decide/2` callback returning `{:error, reason}` rejects all buffered
+appends and returns that tuple unchanged.
+Migrate matches on `{:ok, {:error, _}}` to `{:error, _}`. A failed commit rolls
+back the unit of work, and both `decide/2` and `with_unit_of_work/2` stop their
+unit-of-work process on return, so later appends from long-lived GenServers or
+Phoenix connections are not trapped in a failed buffer. Spec the rejection and
+failed-commit paths, not only successful decisions.
+
 Source: `Cratis/Chronicle.Elixir`: `Source/chronicle/lib/chronicle/read_models/decision_reads.ex`, `decision_read_refused.ex`, `decision_conflict.ex`, `transactions/unit_of_work.ex`, and `Documentation/dynamic-consistency-boundary.md`.
 
 Requires `cratis_chronicle` 3.13.0.

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

@@ -128,7 +128,15 @@ identity. `delivery.ID()` can key an external idempotency record; it is not an
 exactly-once guarantee. Return supported follow-up events rather than manually
 recreating effect dispatch; use projections for materialization, reactors for effects.
 
-`reactors.OnceOnly` excludes replay; it does **not** deduplicate failed-partition
+Requires Chronicle.Go 0.11.0 and kernel 19.70.0 for StartAtTail; check `go list -m github.com/Cratis/Chronicle.Go` and the server version, or retain catch-up behavior until both are upgraded.
+
+Opt into `reactors.StartAtTail()` for a new side-effect reactor that must skip
+history. It only changes first registration: existing positions are retained and
+explicit replay still starts at the beginning. Older kernels ignore this option
+and catch up history. `observation.Service.FastForward` and `FastForwardResult`
+move an observer to the tail; this deliberate administrative skip is not recovery.
+
+`reactors.OnceOnly()` excludes replay; it does **not** deduplicate failed-partition
 recovery. Effects may repeat after errors, cleanup failures or reconnect. Keep them
 idempotent. The kernel owns recovery/quarantine and progress; do not invent resume
 positions or acknowledge before successful processing and cleanup. Read the
@@ -137,7 +145,9 @@ for exact effect, replay and registration-readiness limits.
 
 ## Unsupported does not mean success
 
-Requires Chronicle kernel 19.32.3 for decision guards, with compatibility preflight;
+Requires Chronicle kernel 19.70.0 for the current Go decision-guard profile; check the server version or postpone the client upgrade.
+
+Decision guards include compatibility preflight;
 unsupported kernels return `ErrUnsupported`. Protected operations have their own
 kernel capability gates; the client supports qualified protected revisions and
 classified read-model replay routes, not every protected watch/profile.

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

@@ -11,6 +11,10 @@ ordinary JVM application that happens to talk to a Chronicle server over gRPC.
 There is no framework to inherit from and no application architecture imposed:
 you construct a client, ask it for an event store, and append or observe.
 
+For Chronicle.Kotlin 7.x, first read the
+[Fundamentals migration and upgrade notes](references/fundamentals-migration.md):
+`ConceptAs.value()` and the shared correlation type are breaking changes.
+
 ## Verified product sources
 
 Source: `Cratis/Chronicle.Kotlin`, by source symbols and signatures.

package/package/corpus/skills/cratis-chronicle-client-kotlin/references/annotations-and-handlers.md

@@ -13,7 +13,12 @@ This reference holds the observer annotations, their arguments, filtering annota
 | `@Constraint` | `id = ""` | `constraints/Constraint.kt` |
 | `@Seeder` | none | `seeding/Seeder.kt` |
 
-Handler-level: `@Replay`, `@OnceOnly`. Observer filtering: `@Tag`/`@Tags`,
+Requires Chronicle.Kotlin 6.15.0 and kernel 19.70.0 for StartAtTail; check Gradle dependencies and the server version, or retain initial catch-up.
+
+`@StartAtTail` on a reactor class skips initial history only. Existing positions
+are unchanged.
+`@OnceOnly` targets both classes and functions: it skips replay, not initial
+catch-up or redelivery. Handler-level replay override: `@Replay`. Observer filtering: `@Tag`/`@Tags`,
 `@FilterEventsByTag`/`@FilterEventsByTags`, `@EventSequence`,
 `@EventSourceType`, `@EventStreamType`.
 

package/package/corpus/skills/cratis-chronicle-client-kotlin/references/fundamentals-migration.md

@@ -0,0 +1,48 @@
+<!-- Copyright (c) Cratis. All rights reserved. -->
+<!-- Licensed under the MIT license. See LICENSE file in the project root for full license information. -->
+
+# Shared concepts, correlation and observer upgrades
+
+## Shared concepts and correlation
+
+Requires Chronicle.Kotlin 7.0.0 for the shared concept and correlation type migration below; check Gradle dependencies, or retain the earlier client API until deliberately migrating and recompiling.
+
+Import `ConceptAs` from `io.cratis.fundamentals.concepts` and implement `value()`,
+not a property/getter. Java record accessors satisfy this interface directly.
+Import `CorrelationId` from `io.cratis.fundamentals.execution`, use `NOT_SET` and
+`value()`, and recompile consumers. The old Chronicle names are warning-level
+Kotlin typealiases for this major version, not a permanent alternative API.
+Typed source-id overloads consume Fundamentals concepts. Follow the product's
+[migration guide](https://github.com/Cratis/Chronicle.Kotlin/blob/main/Documentation/guides/migrate-to-fundamentals.md).
+
+Requires Chronicle.Kotlin 7.1.0 and Fundamentals 0.6.0 for shared ambient correlation context; check Gradle dependencies, or pass correlation explicitly instead of relying on shared ambient state.
+
+The module-level `correlationIdManager` delegates to Fundamentals' shared
+`CorrelationIdContext`. Its own API still takes/returns UUIDs; separately
+constructed managers remain independent. State is thread-bound, not
+coroutine-bound: pass correlation explicitly for suspending/thread-hopping work
+and clear ambient context at the boundary. Never assume a pooled thread is a
+request or tenant scope.
+
+Event/read-model enum values are written as ordinal numbers to match their
+schemas. Stored names remain readable; undefined ordinals, including numeric
+strings, are rejected. Do not rearrange persisted enum ordinals casually.
+
+## Observer and transport upgrades
+
+Requires contracts and kernel 19.70.0 for StartAtTail; check the server version, or retain initial catch-up until it is upgraded.
+
+`@StartAtTail` applies to reactor classes in Kotlin and Java. It skips history
+only on first registration; existing positions remain. `@OnceOnly` excludes
+replay, not initial catch-up or redelivery. Older servers ignore the tail flag.
+
+Requires Chronicle.Kotlin 6.14.0 and kernel 19.56.0 for fastForward; check Gradle dependencies and the server version, or do not offer this administrative operation.
+
+`store.observers.fastForward(...)` accepts an identifier or reactor/reducer class
+and returns `FastForwardResult`, with a Java bridge. It deliberately skips work;
+it is not recovery or deduplication.
+
+`ChronicleOptions.maxReceiveMessageSize` and `withMaxReceiveMessageSize()` default
+to 100 MB; `null` retains grpc-java's own default. The constructor and `copy()`
+have a trailing parameter; earlier constructor overloads remain. Recompile affected
+calls rather than treating transport capacity as a query bound.

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

@@ -186,6 +186,24 @@ before enrollment.
 
 ## Observing
 
+Requires Chronicle.TypeScript 6.53.0 and kernel 19.70.0 for startAtTail; check `yarn why @cratis/chronicle` and the server version, or retain catch-up until both are upgraded.
+
+`@startAtTail()` skips history only on first registration; existing positions
+stay intact. `@onceOnly()` does not skip initial catch-up. Older servers ignore
+the new flag.
+
+Requires Chronicle.TypeScript 6.52.0 and kernel 19.56.0 for fastForward; check the client/server versions, or do not offer the operation.
+
+`observers.fastForward(observerId)` returns `FastForwardResult`; it deliberately
+skips to the tail, not a retry mechanism.
+
+Requires Chronicle.TypeScript 6.53.1, kernel 19.78.1 and Fundamentals 7.24.1 for the child/default-value behavior below; check installed packages and server version, or upgrade before relying on it.
+
+Child/nested `@fromAllEvents` and `@fromEvery` keep root-only mappings off new
+children. Replay affected projections to rebuild already-materialized child
+values. Unset read-model fields retain their class defaults; absent arrays stay
+empty.
+
 ### Handlers use camelCase names or `@handles(EventType)`
 
 The default is the camelCase event class name, **not** parameter-type dispatch.

package/package/corpus/skills/cratis-chronicle-client-typescript/references/lifecycle.md

@@ -1,5 +1,12 @@
 # Connection lifecycle
 
+Requires Chronicle.TypeScript 6.51.1 for message-size options; check `yarn why @cratis/chronicle`, or keep gRPC defaults until upgrading.
+
+`ChronicleOptions` and its factory methods accept `maxReceiveMessageSize` and
+`maxSendMessageSize`. Both default to 100 MB; pass `null` to keep gRPC's own
+default. Check payload bounds before increasing limits; a transport allowance is
+not an unbounded-query policy.
+
 This reference holds the watchdog, reconnect, keepalive, compatibility check and telemetry behavior.
 
 ## Lifecycle

package/package/corpus/skills/cratis-components-common-controls/SKILL.md

@@ -20,6 +20,17 @@ All claims and prop shapes are from **Cratis/Components** source rather than unc
 
 Imports are exported by `Source/Common/index.ts`; `Source/package.json` exposes the `Common` subpath. Use **cratis-components-styling** for the provider and CSS setup and **cratis-components-accessibility** for naming/focus. These controls do not replace Arc's generated `InputTextField`/other command fields; use **cratis-arc-react-page** for those bindings.
 
+Requires Components 4.38.0 for provider routing and forwarded non-modal calendar fields; check `yarn why @cratis/components`, or retain host navigation and modal dates.
+
+Set `CratisComponentsProvider.router` with `navigate` and optional `useHref` to
+integrate `Breadcrumbs` and other link components with the app router. Plain
+clicks navigate client-side; modifier and middle clicks retain native behavior.
+Do not intercept every click in a host `onNavigate`.
+
+`DatePickerInput.isNonModal` defaults to `false`; opting in lets an outside click
+both close the calendar and reach the clicked control. The command form's
+`CalendarField` forwards the same prop.
+
 ## Choose the semantic control first
 
 | Need | Control | Controlled contract |

package/package/corpus/skills/cratis-components-data-surfaces/SKILL.md

@@ -132,6 +132,11 @@ Camera/controls contract (`Canvas.tsx`, `CanvasHandle.ts`):
 
 Persist item edits in the host, not in camera callbacks. Browser-test gestures and dimensions. For jsdom tests provide a `ResizeObserver` substitute where required; Pixi integration still needs a real browser signal.
 
+For bound-table server filtering, query-state isolation, refreshed selection and
+localized numbered pagination, read
+[Query table updates](references/query-table-updates.md). Page-local filtering is
+still the default; `serverQuery` is opt-in.
+
 ## 4. Public Chat: bind the host's messages and outcomes
 
 The public `@cratis/components/Chat` exports **`ChatConversation`**, **`ChatSidebar`**, **`ChatSidebarForObservableQueries`**, **`ChatTopicList`** and their types. It does **not** export the Kit `Chat` component or expose a `Chat/Kit` package subpath (`Source/Chat/index.ts`, `Source/package.json`). **`Chat` is exported through `@cratis/components/Canvas`** via the Kit barrel (`Source/Canvas/index.ts`, `Source/Chat/Kit/index.ts`). Prefer the non-spatial Chat subpath for ordinary host-data conversations; importing Canvas brings its Pixi edge.

package/package/corpus/skills/cratis-components-data-surfaces/references/query-table-updates.md

@@ -0,0 +1,51 @@
+<!-- Copyright (c) Cratis. All rights reserved. -->
+<!-- Licensed under the MIT license. See LICENSE file in the project root for full license information. -->
+
+# Query tables: server state, selection and pagination
+
+Requires Components 4.35.1 for all table features described here, including serverQuery, filteredEmptyMessage, pageLinks and refreshed selection; check `yarn why @cratis/components`, or retain the older table API and host-owned filtering, pagination and selection reconciliation.
+
+## Server sorting and filtering are opt-in
+
+`DataTableForQuery`, `DataTableForObservableQuery` and `DataPage` accept
+`serverQuery`. Without it, sorting and filtering affect only the
+loaded page, not the complete result set.
+
+- Supply `toArguments` to translate search text and column filters to query
+  arguments. The backend must apply those arguments itself.
+- Sorting uses Arc `sortBy`/`sortDirection`; `sortFields` maps column names to
+  server fields when necessary.
+- Return `IQueryable` or use MongoDB `Observe` so sorting precedes paging.
+- State changes return to page one; search is debounced by 300 ms by default.
+  Rows are rendered as the server returns them, not filtered a second time.
+
+Do not present a page-local search as a complete-dataset search.
+`filteredEmptyMessage` replaces `emptyMessage` when a search/filter has no rows.
+Provider messages distinguish `filteredEmpty` (this page) from
+`filteredEmptyServer` (server result). `onGlobalFilterChange` reports search text
+as the user types; it does not implement backend search.
+
+## Query state and selection
+
+With Arc and Arc React 22.122 or later, changing bound query arguments shows
+loading instead of the previous arguments' rows, failure or access-denied state.
+Returning to cached arguments avoids a loading flash. A completed
+unsuccessful result is a failure, not an empty success; unauthorized stays access
+denied. The query-bound chat sidebar also distinguishes these outcomes.
+
+Bound tables and `DataPage` reconcile selection against refreshed
+rows by `dataKey`, clearing it when the selected row disappears. A controlled
+selection is reported through `onSelectionChange`, never forcibly overridden.
+Use stable keys and exercise argument changes and removed selections in specs.
+
+## Pagination and localization
+
+`pageLinks` is off by default. Set it to `true` or `{ siblings, boundaries }` on
+`TablePaginator`, a bound table or `DataPage` for numbered links with ellipses.
+The current button has `aria-current="page"`; the old page-count info is hidden.
+The `pages`, `page`, `ellipsis` parts support styling; `page(n)` and `pages`
+messages name the controls. Provider paginator messages or
+`ariaLabels.range(start, end, total)` localize the range text too.
+
+For a custom pager, `paginatorPages` and `PaginatorPageItem` export the same
+windowing logic. Do not hard-code English accessible names in a localized host.

package/package/corpus/skills/cratis-components-schema-editor/references/tree-layout.md

@@ -36,6 +36,7 @@ the controlled host applies and reports its own changes.
 | --- | --- |
 | `concepts: PropertyConcept[]` | Named types with a `PropertyType`; saved as `x-concept`. Overrides a surrounding `PropertyConceptsProvider` |
 | `allowRequired` | Toggle membership in the object's `required` names |
+| `allowGeneratedProperty` | Boolean or per-property predicate; offers the `x-generated` toggle |
 | `allowKeyProperty` | Boolean or `(property, context) => boolean`; `x-key`, one per object |
 | `isPropertyProtected` | Prevent rename/removal, not every possible edit |
 | `validatePropertyName` | `(name, property, siblings) => string \| undefined`, after built-in checks |
@@ -60,3 +61,20 @@ The subpath exports `PropertyType`, `PropertyConceptsProvider`,
 Use the typed property-tree helpers for a controlled host, rather than treating
 `required` as a property boolean. Schema keywords are `x-concept`, `x-key`, and
 the parent object's `required: string[]`.
+
+Requires Components 4.35.0 for generated-property preservation, schema keyword bags and unique identifiers; check `yarn why @cratis/components`, or retain the older tree contract.
+
+Controlled hosts handle `onSetGeneratedProperty` and carry
+`Property.isGenerated`, `vendorKeywords` and `itemVendorKeywords`; the exported
+`GENERATED_KEYWORD` names `x-generated`. Without an offered toggle, including
+read-only mode, generated properties show a marker styled through `generated`.
+Also carry `schemaKeywords` and `itemSchemaKeywords` for unmodeled
+standard JSON Schema keywords. Dropping these bags in a host loses constraints
+and annotations even though the editor preserves them. Untouched properties now
+round-trip their original shape and order; a type change drops only keywords
+inapplicable to the new type (including old array-item annotations).
+
+`PropertyType.UniqueIdentifier` writes a string with `format: uuid`
+and reads either `uuid` or `guid`. Localize it with `typeUniqueIdentifier`.
+`GlyphMenu` and `PropertyTypeGlyph` are exported for host-owned single-choice
+type lists.

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

@@ -10,6 +10,17 @@ license: MIT
 user moves with Previous and Next; Submit appears on the last step once every
 field across every step is valid.
 
+## Dialog dismissal and refusal
+
+Requires Components 4.36.0 for independent dismissal controls; check `yarn why @cratis/components`, or use the older `dismissable` contract.
+
+`Dialog` and `CommandDialog` accept independent `dismissOnOutsideClick`,
+`closeOnEscape` and `showCloseButton`; each falls back to `dismissable`. Busy
+dialogs cannot be dismissed. The busy confirm remains focusable as
+`aria-disabled` and ignores duplicate activation; a refused confirm restores
+focus and announces the provider's `refused` message. Do not replace it with a
+disabled button that loses focus or close the dialog on validation refusal.
+
 ## Verified product sources
 
 | Package | Verified from |

package/package/corpus/skills/cratis-fundamentals-type-discovery/SKILL.md

@@ -146,6 +146,19 @@ services.AddSingleton<IReportFormatters, ReportFormatters>();
 Search for every remaining reference before deleting, so nothing else was
 relying on a registration for a different reason.
 
+## Reuse derived-type discovery
+
+Requires Fundamentals and its generator 7.26.1 for per-universe caching plus nested-generic/experimental-type generator fixes; check `dotnet list package`, or keep the older construction path until upgrading.
+
+Use `Cratis.Serialization.DerivedTypes.For(types)` when several service
+collections share the same `ITypes` instance. It returns one shared `DerivedTypes`
+per universe, held weakly; distinct universes stay isolated. Do not construct one
+per scope or replace a host's explicit universe with `DerivedTypes.Instance`.
+
+The generator omits nested open-generic types from referenced Cratis packages
+and handles referenced `[Experimental]` diagnostic IDs. Upgrade the generator
+rather than editing its output to bypass those build failures.
+
 ## What breaks
 
 - **`[Singleton]` does not resolve.** The using directive is

package/package/corpus/skills/cratis-release-notes/SKILL.md

@@ -111,6 +111,29 @@ Only when asked to fix a release that violates the contract:
    only when the request covers closing issues; otherwise list the issues as a
    proposal. Leave an issue open when the release only partly delivered it.
 
+## Release-action batching and recovery
+
+Requires release-action 1.5.1 for corrected pending-major hotfix handling; check the workflow's `uses` pin, or keep immediate releases on the older contract.
+
+`release-window` defaults to `0` (one
+release per PR); a positive minute window batches pending merges once the oldest
+is old enough. The highest intent wins, notes merge by section with one combined
+`## Summary`, and delivered `(#n)` issues still close. Reference definitions are
+preserved; duplicate labels keep the first definition and warn. Missing intent
+labels warn but are not permission to omit required PR labels.
+
+`hotfix-labels` defaults to `hotfix` and bypasses the window. With a pending major,
+only the merge run for the hotfix fails; scheduled/other merge runs warn and leave
+the batch pending. A manual run without a version releases everything pending;
+obtain the required human major confirmation first. Inspect `pull-requests` and
+`reason` (`batched` or `nothing-pending`) rather than assuming every successful
+run released. Never turn on batching just to clear a queue without authorization.
+
+A release-creation 403 caused by workflow drift names the recovery:
+dispatch the publish workflow from the current default branch with the PR's
+release notes. Re-running the stale commit does not fix this. Other 403s keep
+their original cause; do not treat every permission failure as workflow drift.
+
 ## Verify before handing over
 
 1. Reconcile every version, affected range, capability and API against the

package/package/corpus/skills/cratis-screenplay-command-surface/references/protected-reads.md

@@ -117,8 +117,9 @@ which is one more reason to keep refused shapes out of read keys.
 
 Decide records the unfiltered fact-log boundary, read key and handled event types.
 A matching fact after that boundary makes commit return Conflict /
-DecisionStateChanged with no command facts, including publications. Irrelevant
-facts do not conflict and remain in the committed world. Even a no-fact command is
+DecisionStateChanged with no command facts, including publications. Append constraints
+are checked first: if the same candidate violates a constraint and a protected read,
+the constraint rejection wins. Irrelevant facts do not conflict and remain in the committed world. Even a no-fact command is
 checked. Race cases are evaluator vectors, not a new `.play` specification construct.
 
 Specify present/absent state, rule refusal and denial. Assert no new facts and

package/package/corpus/skills/cratis-screenplay-legacy-extraction/references/prologue-safety.md

@@ -151,6 +151,20 @@ Record in the evidence table: who ran which statements, when, and the verificati
 summary.
 
 ## 5. Capture verification before interpreting
+
+Requires Prologue 2.0.5 for the emission/image behavior below; check pinned package/image versions and `cratis --version` against its bundle, or upgrade before relying on it.
+
+Upgrade older Extractor installations for the PKCS denial-of-service dependency
+fixes. Extractor, Interpreter and Receiver images support linux/amd64 and
+linux/arm64; Apple Silicon does not need a forced amd64 platform.
+
+Heuristics-only interpretation retains each command's own correlated events
+when routes merge, declares shared events once, treats insert-plus-update in one
+transaction as creation, omits text-only `not empty` rules for required numbers
+and declares/key-identifies referenced read models. Do not retain manual
+workarounds for old emitter defects. These repairs do not prove intent or compile
+the output for you: still run executable validation on the emitted model, not
+only parsing, and record remaining diagnostics.
 - Capture files exist for every enabled source.
 - Commands per route match the scenario script; status-code mix matches expected rejections.
 - Fraction of DB transactions correlated to a command (low: concurrency or jobs).

package/package/corpus/skills/cratis-screenplay-toolchain/references/screenplay-contract.version

@@ -1 +1 @@
-4.244.0
+4.245.0

package/package/corpus/skills/cratis-specifications-csharp/SKILL.md

@@ -44,6 +44,17 @@ Requires `Cratis.Arc.Testing` 22.67.0 for generated-value scenario pinning.
 Check the owning product repository before claiming support for
 another version. Never translate an assertion or helper name from memory.
 
+Requires Specifications 4.4.0 for Given/When lifecycle aliases across framework packages; check `dotnet list package`, or keep Establish/Because on older packages.
+
+`Given`/`When` are lifecycle aliases, but house style remains `Establish`/`Because`;
+declaring both forms of a phase produces CRSPEC0009. Inherited phases execute
+once and preserve the original exception; `ValueTask` is awaited. The native
+runner remains experimental: CRSPEC0010 rejects `async void`, CRSPEC0011 warns
+about trim/AOT-unsafe reflective lifecycle calls. Shared resources/leases, phase
+timings, runtime defaults and parallel NUnit fixtures are opt-ins, not blanket
+recommendations to parallelize a stateful suite. Read the product upgrade guide
+before changing runner or package family.
+
 ## Route near misses
 
 - The specification is TypeScript, React, or a view model: use
@@ -202,8 +213,9 @@ public class when_<behavior> : Specification
   leave no blank line between `should_` methods.
 - Fields are `private` in a concrete specification and `protected` in a `given/`
   context, named `_camelCase`.
-- Any phase may be `async Task`. `void Destroy()` is optional teardown, after
-  once per eligible class by default (shared lifecycle); after each fact in a
+- Any phase may return `Task` or `ValueTask`; both are awaited. Never use `async void`.
+  `void Destroy()` is optional teardown, once per eligible class by default
+  (shared lifecycle); after each fact in a
   `[PerFactSpecificationLifecycle]` class.
 
 `Cratis.Specifications.XUnit.v3` discovers `Establish`, `Because`, and `Destroy` by

package/package/corpus/skills/cratis-specifications-csharp/references/running-specs.md

@@ -82,7 +82,14 @@ and record the spec count and outcomes first.
    Specifications.
 5. Fix each `CRSPEC0008` error by moving the change into `Establish` or `Because`; use
    `[PerFactSpecificationLifecycle]` only when the fact genuinely needs a fresh instance.
-6. Rebuild with warnings as errors and fix new nullable warnings.
+6. Change assertion delegates typed as `Predicate<T>` to `Func<T, bool>`; for
+   NUnit 4 comparisons that relied on unordered `ShouldEqual(params)`, use
+   `ShouldEqualInAnyOrder`. Null actual values now fail, including nullable
+   `ShouldNotContain` strings. Assertions live in core with forwarded types;
+   rebuild with warnings as errors and fix new nullable warnings. Delete
+   `CratisSpecificationsWarnOnSharedContextMutation` (it has no effect in 5).
+   Native-runner `async void` facts/phases must return `Task` or `ValueTask`
+   instead (CRSPEC0010 is an error).
 7. Run the executable and require the same total, the same passed count and the same
    classes and methods as the baseline (display names may become more readable),
    with no new skips. A different count means a spec was

package/package/corpus/skills/cratis-specifications-csharp/references/shared-lifecycle.md

@@ -32,18 +32,35 @@ implementations, custom fact test cases and plain xUnit classes keep the per-fac
 
 Requires Cratis.Specifications 4.4.0 or later for `IDisposable` specifications to share
 the lifecycle; earlier versions use per-fact construction. With shared lifecycle enabled,
-construction happens once and `Dispose` runs once after the last fact. Use
+construction happens once, and `Destroy` runs followed by
+one `Dispose` after the last fact, even when `Destroy` fails. Class/collection fixtures remain owned by xUnit,
+with assembly fixtures also supported on v3. Use
 `[PerFactSpecificationLifecycle]` when a fresh instance per fact is needed.
 
 `Specification.InitializeAsync()` is idempotent for a single instance. It does not make
 an ineligible class shared or cache instances across classes.
 
+## Native runner teardown outcomes
+
+Requires Cratis.Specifications.Runner 5.0.3 for separate class teardown results; check `dotnet list package`, or expect the older runner to mark every fact failed after teardown fails.
+
+A failing `Destroy`, disposal or scope end produces one separate failed result
+for the specification class and fails the run. Completed facts keep their own
+outcomes, as on xUnit/NUnit. Select the teardown result to rerun its class; passing
+facts do not imply the class or run passed.
+
 ## CRSPEC0008
 
 `CRSPEC0008` is an error by default: a `should_` fact that assigns to or increments an
 instance field or property of the specification, or calls `Add`, `AddRange`, `Remove`,
 `RemoveAt`, `Clear` or `Insert` on one, would make the result depend on fact order.
-Move the change into `Establish` or `Because`:
+Requires Specifications 5.0.2 for Received.InOrder verification recognition; check `dotnet list package`, or upgrade before relying on this diagnostic exception.
+
+Calls inside NSubstitute `Received.InOrder(...)` delegates are recognized as
+verification, but assignments and increments there still mutate state and are
+reported. Theories, per-fact classes/assemblies, immutable collection calls and
+collection calls whose return value is used are excluded. Move actual mutations
+into `Establish` or `Because`:
 
 ```csharp
 public class when_registering : Specification

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cratis/pi",
-  "version": "7.111.0",
+  "version": "7.113.0",
   "description": "Configuration-aware Cratis AI integration for Pi",
   "type": "module",
   "files": [