@cratis/pi 7.27.3 → 7.28.0

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

@@ -75,8 +75,9 @@ Rules the framework actually enforces:
   operation collections, and `ARC0018` checks generated-invoker accessibility.
 - Name the command as the action — `OpenDebitAccount`, not
   `OpenDebitAccountCommand`.
-- `Handle` parameters are resolved from DI, so ask for services there rather
-  than through a constructor.
+- Unmarked `Handle` parameters resolve from `Provide()` or DI; ask for services
+  there rather than through a constructor. Server-owned new values use
+  `[GeneratedValue]` instead (below).
 - Never inject `IEventLog` into `Handle` to append the command's own events —
   `ARCCHR0007` warns, and it bypasses Arc's append pipeline. Express the append
   through the return type.
@@ -137,8 +138,8 @@ Two consequences worth knowing before writing the first command:
   the events in that same tuple are appended to. Returning more than one
   unhandleable element throws `MultipleUnhandledTupleValues`. When the command
   also returns an operation keyed by that id, have the caller supply the id
-  instead of calling `New()` in `Handle()`, so a retried request reuses the same
-  ownership key.
+  instead of generating a new value, so a retried request reuses the same
+  ownership key. A generated value alone does not provide idempotency.
 - **Events never carry their own event source.** Cross-stream writes use
   `EventForEventSourceId`; they are not expressed by a property on the event.
 
@@ -146,11 +147,8 @@ Two consequences worth knowing before writing the first command:
 [Command]
 public record Register<Thing>(<ConceptType> <Name>)
 {
-    public (<ThingId>, <ThingRegistered>) Handle()
-    {
-        var id = <ThingId>.New();
-        return (id, new(<Name>));
-    }
+    public (<ThingId>, <ThingRegistered>) Handle([GeneratedValue("thing")] <ThingId> id) =>
+        (id, new(<Name>));
 }
 ```
 
@@ -166,6 +164,28 @@ public record Transfer(<AccountId> From, <AccountId> To, <Money> Amount)
 }
 ```
 
+## Generate a server-owned new identifier
+
+**Arc 22.66.0+**, verified at **v22.68.0**: the create-command example above
+requires `<ThingId>` to implement `IGeneratable<ThingId>` with a static `New()`
+strategy (Fundamentals 7.23.0+; see `cratis-fundamentals-concept`). Replace
+`Guid.NewGuid()` or `<ThingId>.New()` inside `Handle()` with a generated parameter,
+not a new request property. Return the id as the ordinary response or in the
+id/event tuple so the caller receives it.
+
+`[GeneratedValue]` is in `Cratis.Arc.Commands.ModelBound` and applies only to
+parameters of a non-static command `Handle()`. Arc generates after `Provide()`
+control results permit execution, validates the concept, then invokes `Handle`.
+`Provide()` and DI cannot override it. Use a non-nullable self-generatable type,
+not raw `Guid`; names default to the parameter name or an explicit attribute name
+and are case-sensitive, non-empty and unique within the command.
+
+Keep client-chosen ids/references as inputs and services/read models as ordinary
+dependencies. A UUID is not a secret, token, authorization proof, idempotency key,
+or a gapless/sequential invoice number. For validation failures, captures,
+ARC0022–ARC0025, migration and the pinned-spec workflow, read
+[generated values](references/generated-values.md).
+
 ## Where the event source id comes from
 
 Chronicle resolves the command's event source id in this order:
@@ -330,8 +350,11 @@ Components guidance, not to this skill.
 - The event source id resolves from exactly one place; `ARCCHR0002` is silent.
 - `[Key]`, where used, is `Cratis.Chronicle.Keys.KeyAttribute`.
 - No `IEventLog` is injected into `Handle`.
-- Every value `Provide` returns is consumed by `Handle`.
-- Rejections are validation results, never thrown exceptions.
+- Every value `Provide` returns is consumed by an unmarked `Handle` parameter.
+- Generated parameters follow [generated values](references/generated-values.md)
+  and are pinned before scenario execution (`cratis-specifications-csharp`).
+- User-correctable rejections are validation results, never thrown exceptions;
+  `GeneratedValueRejected` instead signals a defective server generation strategy.
 - Every secret or personal value is marked before it can reach the event log.
 - `dotnet build` is clean in Debug and Release, with no suppressed `ARC*` or
   `ARCCHR*` diagnostic left unjustified.

package/package/corpus/skills/cratis-arc-command/references/generated-values.md

@@ -0,0 +1,166 @@
+# Server-generated Handle values
+
+## Contents
+
+- Declare the value and command
+- Resolution, validation and captures
+- Analyzer diagnostics
+- Migrate generation inside Handle
+- Pin generated values in specifications
+- Verified sources and release boundary
+
+<!-- Copyright (c) Cratis. All rights reserved. -->
+<!-- Licensed under the MIT license. See LICENSE file in the project root for full license information. -->
+
+## Declare the value and command
+
+Generated parameters arrived in Arc **22.66.0**, scenario pinning in **22.67.0**,
+and analyzers in **22.68.0**. The examples and behavior here are verified at
+**v22.68.0**, which pins Fundamentals **7.23.0**.
+
+Use a concept for a server-owned new identifier. This standalone Arc example
+allocates an id; it does not append an event or persist a cart:
+
+```csharp
+// Copyright (c) Cratis. All rights reserved.
+// Licensed under the MIT license. See LICENSE file in the project root for full license information.
+
+using Cratis.Arc.Commands.ModelBound;
+using Cratis.Concepts;
+
+namespace Shopping.Carts;
+
+/// <summary>
+/// Represents a cart identifier.
+/// </summary>
+/// <param name="Value">The underlying identifier.</param>
+public record CartId(Guid Value) : ConceptAs<Guid>(Value), IGeneratable<CartId>
+{
+    /// <summary>
+    /// Creates a new cart identifier.
+    /// </summary>
+    /// <returns>A new cart identifier.</returns>
+    public static CartId New() => new(GenerateValue.Uuid());
+}
+
+/// <summary>
+/// Allocates a server-owned cart identifier.
+/// </summary>
+[Command]
+public record AllocateCartId
+{
+    /// <summary>
+    /// Returns the allocated identifier to the caller.
+    /// </summary>
+    /// <param name="cartId">The server-generated identifier.</param>
+    /// <returns>The allocated identifier.</returns>
+    public CartId Handle([GeneratedValue("cart")] CartId cartId) => cartId;
+}
+```
+
+For a Chronicle stream identity, derive `CartId` from `EventSourceId<Guid>`
+instead; see `cratis-fundamentals-concept`. Return `(id, event)` to both append
+and give the caller the new stream id, as in SKILL.md. An identifier is not an
+event, and generation alone does not persist anything.
+
+Keep existing/client-chosen identifiers and references on command properties.
+Services and read models remain ordinary dependencies, not generated values.
+UUID generation does not establish authorization, secrecy, idempotency, storage
+freshness, or gapless/sequential numbering. Use the domain's authoritative
+allocation mechanism for invoice numbers, not a random UUID strategy.
+
+## Resolution, validation and captures
+
+`GeneratedValueAttribute` targets parameters only. Use it on a command's public
+instance `Handle()`, not a property, constructor or `Provide()` parameter.
+The type must be non-nullable and implement `IGeneratable<TSelf>` for itself;
+a raw `Guid`, nullable concept or by-reference parameter is invalid. Use domain
+concepts; the runtime's type check is the self-generatable interface contract.
+
+`[GeneratedValue]` uses the parameter name. `[GeneratedValue("cart")]` keeps the
+pin/capture name stable across a parameter rename. Names are case-sensitive,
+non-whitespace and unique within the command.
+
+Arc first runs `Provide()` and checks its control results. Only if execution may
+continue does it call the concept's `New()` strategy and validate the value before
+invoking `Handle()`. Neither a provided value nor a DI registration overrides a
+generated parameter. Unmarked parameters retain their normal resolution.
+
+Discoverable concept validators run with the command's scoped provider and
+cancellation token. Errors produce `GeneratedValueRejected`, an exception
+outcome in `CommandResult`: a server-generation defect, not a request-validation
+400. Warnings/information allow execution. Fix the strategy or invariant; do not
+turn the defect into a user rejection or disable validation to make it pass.
+
+Validated values enter `CommandContext.GeneratedValues` in parameter-resolution
+order. Each capture has zero-based `Order`, `Name`, declared `Type` and `Value`;
+`Get<CartId>("cart")` retrieves the latest matching capture. Rejected values are
+not captured. A Handle parameter is not a request property and is not audited
+as command input. Do not log or trace captures or validator failure text, which
+can contain values. Returning a value or putting it in an event still follows the
+ordinary response, event and compliance contracts.
+
+## Analyzer diagnostics
+
+Arc v22.68.0 reports these at compile time; none has a code fix. Runtime
+handler-construction checks remain for declarations compiled without analyzers.
+
+| Diagnostic | Severity | Fix |
+| --- | --- | --- |
+| ARC0022 | Error | Use a non-nullable type implementing `IGeneratable<TSelf>` for itself; no raw `Guid` or by-reference parameter. |
+| ARC0023 | Error | Move the attribute to a non-static command `Handle()` parameter, not `Provide()`, a read model or controller. |
+| ARC0024 | Error | Give each generated parameter a non-empty unique name; comparison is case-sensitive. |
+| ARC0025 | Warning | Remove a redundant provided value of the generated type, or remove the attribute if `Provide()` should supply it. An unmarked parameter can still consume that provided type. |
+
+## Migrate generation inside Handle
+
+For `var id = new CartId(Guid.NewGuid());` or `var id = CartId.New();` in
+`Handle()`, keep the request contract unchanged:
+
+1. Make the concept implement `IGeneratable<CartId>` with static `New()` using
+   `GenerateValue.Uuid()` or `GenerateValue.UuidV7()`.
+2. Replace the local allocation with `[GeneratedValue("cart")] CartId cartId`
+   on `Handle()`, then use that parameter in the existing return/operation shape.
+3. Return the id if the caller needs it; a capture is not an automatic response.
+4. Pin the concept by generated name in pipeline specifications. For a pure
+   direct-call specification, pass the known concept to `Handle()` yourself.
+
+Do not migrate caller-owned inputs into server generation. A retried request
+would otherwise allocate a different value; random generation is not an
+idempotency mechanism. UUIDv7 reveals creation time and is not monotonic within
+a millisecond; choose it for index locality only after checking storage ordering.
+
+## Pin generated values in specifications
+
+Use `cratis-specifications-csharp` and its `references/application-scenarios.md`
+for the complete pinned example. `Cratis.Arc.Testing.Commands` supplies
+`PinGeneratedValue(name, concept)`, `AllowGeneration()` and the `GeneratedValues`
+capture helpers on `CommandScenario<TCommand>`.
+
+Scenarios default to strict: an unpinned generated parameter yields
+`GeneratedValueNotPinned` in the command result, not a throw from `Execute`.
+Configure before execution. Nested pins use both generic arguments at the call
+site: `PinGeneratedValue<TCommand, TOtherCommand>(name, concept)`.
+
+## Verified sources and release boundary
+
+Published guides:
+
+- [Generated values](/arc/backend/csharp/commands/generated-values/)
+- [Pin generated values in command specs](/arc/backend/csharp/testing/generated-values/)
+- [Migrate generated identifiers](/arc/upgrading/generated-values/)
+- Analyzer pages: [ARC0022](/arc/backend/csharp/code-analysis/arc0022/),
+  [ARC0023](/arc/backend/csharp/code-analysis/arc0023/),
+  [ARC0024](/arc/backend/csharp/code-analysis/arc0024/),
+  [ARC0025](/arc/backend/csharp/code-analysis/arc0025/).
+
+Source at **Arc v22.68.0**: `Source/DotNET/Arc.Core/Commands/ModelBound/GeneratedValueAttribute.cs`,
+`Commands/GeneratedValueParameters.cs`, `GeneratedValueFactories.cs`,
+`CommandHandlerArgumentResolver.cs`, `GeneratedValueResolution.cs`;
+`Source/DotNET/Arc.Core.CodeAnalysis/DiagnosticDescriptors.cs`; and
+`Source/DotNET/Testing/Commands/CommandScenarioGeneratedValueExtensions.cs`.
+
+This release has no freshness/collision guard, contextual clock/tenant/pattern
+generation, or additional built-in strategies beyond Fundamentals' UUID/UUIDv7
+helpers. Do not teach proposals as available APIs or invent Screenplay `generate`
+syntax for this feature.

package/package/corpus/skills/cratis-fundamentals-concept/SKILL.md

@@ -78,10 +78,14 @@ Do not assume `string.Empty`, `0`, or `Guid.Empty` is universally invalid.
 
 ## Let a concept generate its own value
 
-Check the Cratis.Fundamentals version the project resolves first. Arc and
-Chronicle can bring an older one; when it is below 7.23.0, add a direct
-`Cratis.Fundamentals` 7.23.0 or later package reference, or keep the existing
-`static New()` (without the interface) until you can.
+Check the Cratis.Fundamentals version the project resolves first. Arc first
+pinned **7.23.0 in v22.66.0** (also verified at v22.68.0); the older-version
+caveat is not a reason to add a direct reference for Arc 22.66.0+ when it already
+resolves 7.23.0 or later. Chronicle **v19.43.0** still pins **7.22.0** in
+`Directory.Packages.props`. For older Arc or Chronicle-only applications, when
+the resolved version is below 7.23.0, add a direct `Cratis.Fundamentals` 7.23.0
+or later package reference, or keep the existing `static New()` (without the
+interface) until you can.
 
 When the system, not the caller, creates a value, the concept declares how by
 implementing `IGeneratable<TSelf>` (`Cratis.Concepts`, Cratis.Fundamentals
@@ -123,7 +127,11 @@ Do not generate when:
 
 In specifications, construct the concept from a known value
 (`new <ConceptName>(Guid.Parse("…"))`) and assert against it. Do not seed or
-replace the generator. Guide: `/fundamentals/csharp/generating-values/`.
+replace the generator. In Arc **22.66.0+**, let a server-owned new identifier
+reach `Handle()` through `[GeneratedValue]` rather than calling `New()` inside
+it; see `cratis-arc-command` for declaration and migration, and
+`cratis-specifications-csharp` for named scenario pins (Arc **22.67.0+**).
+Guide: `/fundamentals/csharp/generating-values/`.
 
 ## Create a Guid-backed Chronicle stream identity
 

package/package/corpus/skills/cratis-screenplay-automations-and-translations/SKILL.md

@@ -34,8 +34,9 @@ identity, effect and pending-work contract at that point; do not postpone it to
   planner audits through v7. Deliver that scope as authorized gap-fill
   (`references/realization-and-gap-fill.md`).
 - Reaction `runs as system role "<Role>"` declares an invocation actor (ESM v10).
-  Without it the invoke has no caller. CLI 3.41.0's 4.114.0 compiler rejects the
-  new syntax (PLAY0137). Checked model/diagnostics: captures-and-reactions
+  Without it the invoke has no caller. Historical CLI 3.41.0's 4.114.0 compiler
+  rejected the syntax (PLAY0137); current CLI 3.46.1 instead refuses ESM v10
+  at render admission (CLI-RENDER-004). Checked model/diagnostics: captures-and-reactions
   `references/invocation-identity.md`.
 
 ## Effect guarantees and recovery traps

package/package/corpus/skills/cratis-screenplay-automations-and-translations/references/audit-format.md

@@ -11,8 +11,8 @@ technique: partial work stays visible and nothing is skipped because it looked r
 
 Result is `complete` only when every column is filled or says why it does not apply (for example
 "direct effect: immediate, internal, cannot fail"). `open` names the unresolved decision and who
-answers. `blocked` names the actual capability gap (for example CLI 3.41.0's
-older compiler cannot parse a declared ESM v10 reaction actor) with intended behavior.
+answers. `blocked` names the actual capability gap (for example current CLI
+3.46.1 refuses ESM v10 at render admission with CLI-RENDER-004) with intended behavior.
 
 ## Per translation (capture or translator reaction)
 | Source and type | Location | Correlation | Field dispositions | Target fields traced | Dedup and ordering | Trust boundary | Recovery owner | Named cases | Result |

package/package/corpus/skills/cratis-screenplay-automations-and-translations/references/automation-patterns.md

@@ -71,8 +71,10 @@ When a todo list is not needed: the effect is immediate, internal and cannot fai
 Screenplay 4.125.0 declares the actor with reaction-level `runs as system role
 "<Role>"` (ESM v10); without it a gated invocation has no caller and denies.
 `given caller` is not an invocation actor. Role requirements remain enforced;
-claim conditions for this system principal remain unknown. CLI 3.41.0's older
-compiler rejects the syntax (PLAY0137), and Stage 4.51.3 admits through v7 only.
+claim conditions for this system principal remain unknown. Historical CLI 3.41.0's
+older compiler rejected the syntax (PLAY0137). Current CLI 3.46.1 bundles
+Screenplay 4.130.0 / Stage 4.52.0 and refuses v10 at render admission
+(CLI-RENDER-004; toolchain `references/versions.md`).
 Use the checked model in captures-and-reactions `references/invocation-identity.md`.
 Arc gap-fill uses `[ExecuteCommandsAsSystem("<role>")]` for returned commands,
 not identity inferred from prose or an imperative pipeline call.

package/package/corpus/skills/cratis-screenplay-automations-and-translations/references/provenance.md

@@ -40,7 +40,9 @@ Changes in this version: the examples are complete fenced documents that compile
 example's anonymous-booking spec gained the `given caller` PLAY0389 requires; the todo-list
 example's list query, `reads` and retry sweep moved to marked design-only excerpts so the core
 binds); tool-qualified verdict text; the trusted-actor text now names `[ExecuteCommandsAsSystem]`
-(Arc v20.56.0). Current actor syntax was reverified at Screenplay v4.125.0
+(Arc v20.56.0). Actor syntax was reverified at Screenplay v4.125.0
 `reactions.md`, `ReactionIdentityParser.cs`, `ReactionRefusalValidator.cs` and the
-binder's v10 selection; the checked scenario passes reference execution. CLI
-3.41.0's older parser and Stage 4.51.3's v7 planner remain target limits.
+binder's v10 selection; the checked scenario passed reference execution. CLI
+3.41.0's older parser and Stage 4.51.3's v7 planner were historical target limits.
+Current CLI 3.46.1 bundles Screenplay 4.130.0 / Stage 4.52.0 and still refuses
+v10 at render admission (CLI-RENDER-004; toolchain `references/versions.md`).

package/package/corpus/skills/cratis-screenplay-captures-and-reactions/SKILL.md

@@ -75,8 +75,9 @@ reference invocation's authenticated system principal with exactly those roles;
 Read [invocation identity](references/invocation-identity.md) for the checked
 scenario, claim/unknown semantics and PLAY0647–0652/0557 diagnostics.
 
-CLI 3.41.0's 4.114.0 compiler rejects this source with PLAY0137; its version gate
-and Stage 4.51.3 planner admit only through v7. Target realization is gap-fill,
+Historical CLI 3.41.0's 4.114.0 compiler rejected this source with PLAY0137.
+Current CLI 3.46.1 bundles Screenplay 4.130.0 / Stage 4.52.0; its render version
+gate still admits only through v7 (CLI-RENDER-004 for v10). Target realization is gap-fill,
 using Arc `[ExecuteCommandsAsSystem]` for returned commands. Without that attribute
 Arc supplies no principal and `[Authorize]`/`[Roles]` deny. Each invoked command
 is atomic, not the whole cascade; earlier accepted facts remain after a later refusal.

package/package/corpus/skills/cratis-screenplay-captures-and-reactions/references/invocation-identity.md

@@ -69,11 +69,12 @@ module Work
   denial; opaque/unknown cases are not guessed. `--check privilege` (PLAY0652)
   reviews whether event producers require every elevated role, not runtime safety.
 
-CLI 3.41.0 bundles Screenplay 4.114.0, which does not parse `runs as`: the example's
-`cratis screenplay validate --executable --warnings-as-errors` returns PLAY0137,
-exit 5. It cannot render this source. Its render version gate separately admits
-only through v7 (CLI-RENDER-004 for newer admitted compiler output), while Stage
-4.51.3's direct planner audits through v7 and refuses v10 with STAGE-ESM-016.
+Historical CLI 3.41.0 bundled Screenplay 4.114.0, which did not parse `runs as`:
+the example's `cratis screenplay validate --executable --warnings-as-errors`
+returned PLAY0137, exit 5. This is not a current parser claim. Current CLI 3.46.1
+bundles Screenplay 4.130.0 but its render gate still admits only through v7
+(CLI-RENDER-004 for v10); bundled Stage 4.52.0's direct planner audits through
+v7 and refuses v10 with STAGE-ESM-016 (`references/versions.md` in toolchain).
 Clock/application-trigger identities have no Stage Arc realization either.
 Use authorized gap-fill with the model as contract; returned-command Arc identity
 uses `[ExecuteCommandsAsSystem]`, never permission inferred from a model header.

package/package/corpus/skills/cratis-screenplay-captures-and-reactions/references/specifying-triggers-and-clock.md

@@ -19,7 +19,7 @@ specification IssuingTheWeeklyDigest
 
 Under `cratis` before 3.28.2 these actions parsed and were checked against the application
 but bound to nothing (`PLAY0268` names ESM v6, decision 0022); on 3.28.2 they bind.
-Current standalone 4.125.0 executes admitted scenarios through `screenplay test`
+Standalone 4.125.0 (checked; current pins in the toolchain `versions.md`) executes admitted scenarios through `screenplay test`
 or MCP `run-specifications`; source compilation alone is authored evidence.
 Clock rules: the clock is UTC and exact; an
 occurrence fires once when it is **due after `given clock` and at or before

package/package/corpus/skills/cratis-screenplay-command-surface/SKILL.md

@@ -32,7 +32,7 @@ source is the single flow model.
 | `Cratis.Screenplay` | main `fd18129` | Inline events, repairs and canonical `optional`; changed examples compiled |
 | `Cratis.Screenplay` | `4.66.0` (`c89198b`) | Binding behaviour of `handler`, code attachments, `persona` and compliance attributes: `Semantics/SemanticModelBinder*.cs`, `Diagnostics/DiagnosticCodes.cs` |
 | `Cratis.Screenplay` | `4.68.0` (`79801bf`) | Historical generated-value/response rule probes (ESM v7) |
-| `Cratis.Screenplay` | `4.127.0` | Current identity and compliance guidance: released `identity.md`, `context.md`, `concepts.md`, `purposes.md`, `events.md`, `diagnostics.md`; changed examples compiled |
+| `Cratis.Screenplay` (historical check) | `4.127.0` | Identity and compliance guidance checked at this release: released `identity.md`, `context.md`, `concepts.md`, `purposes.md`, `events.md`, `diagnostics.md`; changed examples compiled |
 
 Historical examples/probes retain the table's original versions; current source
 guidance is not a relabeled old execution result. Compilation checks syntax and
@@ -261,7 +261,7 @@ produces when isProForma == true
 ## Routes and external operations
 
 Named event sources/streams and command routes bind as ESM v8 (verified at 4.125.0);
-CLI 3.41.0 render rejects models above v7. A routed command's identifier and
+CLI 3.46.1 render rejects models above v7. A routed command's identifier and
 known event destinations must match the source's nominal identifier type
 (PLAY0504, error). Allocation uses the generated identifier's type, or without
 one requires a UUID-based source. Composite `streamId` routes map every named
@@ -297,7 +297,7 @@ to the routed scope. This does not make command `reads` protected.
 ## Generated values and responses (ESM v7)
 
 Generated values/responses bind as ESM v7, including in the current CLI bundle.
-CLI 3.41.0 admits v7 to Stage planning; its canonical corpus gets generated-value
+The historical CLI 3.41.0 check admitted v7 to Stage planning; its canonical corpus got generated-value
 and response refusals STAGE-ESM-028/029. Binding is not a render claim.
 Read [references/generated-values-and-responses.md](references/generated-values-and-responses.md) when adding or
 reviewing `generated` properties, `returns` responses, or decision 0023 constructs.
@@ -369,7 +369,7 @@ Four contexts, and **what each omits is load-bearing** — when writing a code b
 ## Verify
 
 - [ ] Validate the complete model root with warnings as errors; name the tool,
-      version and result. Current pins: standalone 4.127.0 / CLI 3.41.0; bundle
+      version and result. Current pins: standalone 4.131.0 / CLI 3.46.1; bundle
       compatibility and execution are separate checks.
 - [ ] No unintended `PLAY0478` or `PLAY0479` information remains.
 - [ ] At most one command property carries `identifier`, and no event property does.

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

@@ -100,12 +100,13 @@ An unknown `$context.` path is reported, so a typo does not silently become null
 
 ## Caller paths and identity details
 
-At Screenplay 4.127.0, `$identity.<property>` is the same caller value as
+Checked at Screenplay 4.127.0: `$identity.<property>` is the same caller value as
 `$context.identity.<property>`. Prefer `$identity` in new mappings; the older root
-is supported, not deprecated. The `cratis` CLI 3.41.0 bundles Screenplay 4.114.0, which predates both:
-its parser rejects a top-level `identity` block (`PLAY0001`), and with `--executable` it reads a
-`$identity.<property>` mapping as a raw expression (`PLAY0268`). Check these with standalone 4.127.0,
-and keep `$context.identity.<property>` where a model must go through `cratis render` today. Built-ins are `id`, `name`, `userName`,
+is supported, not deprecated. Historical `cratis` CLI 3.41.0 bundled Screenplay 4.114.0, which predated both:
+its parser rejected a top-level `identity` block (`PLAY0001`), and with `--executable` it read a
+`$identity.<property>` mapping as a raw expression (`PLAY0268`). Those checks used standalone 4.127.0;
+they are not current CLI 3.46.1/Screenplay 4.130.0 parser claims. Check current renderer
+admission separately before choosing caller mappings. Built-ins are `id`, `name`, `userName`,
 `isAuthenticated`, `roles`, `claims.<name>` (everything after `claims.` is opaque).
 Bare `$identity` reports PLAY0152; unknown properties report PLAY0155. Only
 `$identity.id`/`.name`/`.userName` bind in portable `produces` mappings, exactly

package/package/corpus/skills/cratis-screenplay-command-surface/references/generated-values-and-responses.md

@@ -1,11 +1,11 @@
 ## Generated values and responses (ESM v7)
 
 A `generated` command property and `returns` response bind and reference-execute
-as ESM v7. Current pins are standalone Screenplay 4.127.0 and CLI 3.41.0
-(bundled Screenplay 4.114.0/Stage 4.51.3); `cratis-screenplay-toolchain`
+as ESM v7 (checked at 4.68.0). Current pins are standalone Screenplay 4.131.0
+and CLI 3.46.1 (bundled Screenplay 4.130.0/Stage 4.52.0); `cratis-screenplay-toolchain`
 `references/versions.md` owns the table. CLI#261 is closed: CLI now admits v7
-to Stage planning, but its v7 canonical corpus receives Stage generated-value
-and response refusals STAGE-ESM-028/029. Do not turn this into a blanket compiler
+to Stage planning. The historical CLI 3.41.0 v7 canonical corpus received Stage
+generated-value and response refusals STAGE-ESM-028/029. Do not turn this into a blanket compiler
 refusal or promise a render from binding alone. Preserve the contract for gap-fill
 where admission refuses. Historical rules below were read at 4.68.0. Complete compiled example:
 `cratis-screenplay-toolchain` `references/generated-responses-example.md`.
@@ -45,7 +45,7 @@ Rules (all read at `v4.68.0`):
 
 Operations remain authorable/unadmitted (PLAY0268). Named event sources,
 streams and command/specification routes instead bind and reference-execute as
-ESM v8 at 4.125.0; CLI 3.41.0 render refuses versions above v7 before planning
+ESM v8 at 4.125.0; CLI 3.46.1 render refuses versions above v7 before planning
 (CLI-RENDER-004). Syntax/MCP acceptance alone is not execution. Source/stream
 forms and realization boundary: `cratis-screenplay-toolchain`
 `references/sources-and-streams.md`. Do not infer further syntax or provider

package/package/corpus/skills/cratis-screenplay-event-modeling/SKILL.md

@@ -138,8 +138,9 @@ What binds depends on **which tool** you ask, so name the tool and its version:
   and command/specification routes as v8; reaction `runs as` identity as v10 on
   standalone 4.125.0. Use `screenplay test` or MCP `run-specifications` for V4.
   Operations/systems, exact numbers and refusal/redelivery remain unadmitted.
-  CLI 3.41.0 bundles older syntax and renders through v7 only: its parser rejects
-  `runs as`, and Stage refuses generated values/responses with STAGE-ESM-028/029.
+  Historical CLI 3.41.0 rejected `runs as` syntax and its Stage 4.51.3 check
+  refused generated values/responses with STAGE-ESM-028/029. Current CLI 3.46.1
+  bundles Screenplay 4.130.0 / Stage 4.52.0 but still renders through v7 only.
   Source/binding admission and target realization are separate gates.
 
 The ESM versions, the full disposition table and the Step 7 clock example's binding
@@ -170,7 +171,7 @@ source is the single flow model.
 | `Cratis.Screenplay` | `4.31.0` | Compiler: parser, validator, diagnostics, folder merge, semantic binder |
 | `Cratis.Screenplay.Tool` | `4.31.0` | The `screenplay` dotnet tool |
 | `Cratis.Screenplay` | main `fd18129` | Inline contracts and event context; changed nine-step examples compiled |
-| `Cratis.Screenplay.Tool` | `4.68.0` (`79801bf`) | Current pin: the nine-step examples compile and their specifications run in the reference runner; generated values and responses (ESM v7) were read at this tag |
+| `Cratis.Screenplay.Tool` | `4.68.0` (`79801bf`) | Checked at 4.68.0 (current pins in `cratis-screenplay-toolchain` `references/versions.md`): the nine-step examples compile and their specifications run in the reference runner; generated values and responses (ESM v7) were read at this tag |
 | `Cratis.Screenplay.Tool` | `4.66.0` (`c89198b`) | Persona, operation and stream dispositions below were read at this tag, and the Step 7 clock example was probed through MCP on it |
 
 The pin set for the whole Screenplay family, and which tool reports what, lives only in

package/package/corpus/skills/cratis-screenplay-event-modeling/references/parsed-not-runnable.md

@@ -1,6 +1,6 @@
 # Parsed is not runnable: ESM versions and dispositions
 
-Current evidence: Screenplay v4.125.0 `SemanticModelBinder.cs`, `Versions.cs`,
+Checked at Screenplay v4.125.0: `SemanticModelBinder.cs`, `Versions.cs`,
 `Documentation/screenplay/{commands,operations,event-sources,reactions,tool}.md`.
 The binder selects v8 for event routes and v10 for declared reaction identity.
 Pins and consumer boundaries: toolchain `references/versions.md`.
@@ -19,7 +19,7 @@ Pins and consumer boundaries: toolchain `references/versions.md`.
 
 ## Dispositions to keep apart
 
-| Construct | Current standalone disposition |
+| Construct | Standalone disposition (checked at v4.125.0) |
 | --- | --- |
 | `persona`, domain/authentication metadata | Report-only; unknown named policies remain source defects |
 | Compliance concepts | Bare `pii`/`secret` (4.127.0); binding still refuses PLAY0268, never remove protection |
@@ -27,8 +27,8 @@ Pins and consumer boundaries: toolchain `references/versions.md`.
 | Composite stream ids | v8 routing; complete named parts/canonical comparisons, PLAY0515 refuses protected keys/sources; not a legacy text split |
 | Command reads/concurrency | Legacy unprotected decisions, PLAY0271 |
 | Invokes-only trigger reads | Report-only, not protected state; direct production with reads refuses |
-| Generated values/responses | v7 binding/reference execution; Stage 4.51.3 member refusals STAGE-ESM-028/029 |
-| Sources/streams and command/specification routes | v8 binding/reference execution; CLI 3.41.0 render boundary is v7 |
+| Generated values/responses | v7 binding/reference execution; historical Stage 4.51.3 check: member refusals STAGE-ESM-028/029 |
+| Sources/streams and command/specification routes | v8 binding/reference execution; current CLI 3.46.1 render boundary is v7 |
 | Declared reaction invocation actor | v10 binding/reference execution; older CLI parser PLAY0137; Stage planner refuses v10 |
 | Operations/systems, exact numbers, refusal/redelivery | Source accepted; whole binding refuses PLAY0268 |
 | UI | Authoring/deferred metadata; runtime support is a separate consumer contract |

package/package/corpus/skills/cratis-screenplay-legacy-extraction/references/generate-notes.md

@@ -17,8 +17,10 @@ cratis-screenplay-toolchain `references/versions.md`; behaviour from the cratis
 Screenplay.CritterStack `v0.24.0`. Version-specific capability facts belong in cratis-screenplay-toolchain
 `references/versions.md`.
 
-Current CLI is 3.41.0, with Arc.Screenplay 22.54.0 (`references/versions.md` in
-the toolchain). Current option/admission evidence: CLI released
+Current CLI is 3.46.1, with Screenplay 4.130.0 / Stage 4.52.0 /
+Arc.Screenplay 22.54.0 / Chronicle 19.32.0 / Fundamentals 7.22.8
+(`references/versions.md` in the toolchain; standalone Screenplay is 4.131.0).
+Option/admission evidence checked at CLI 3.41.0: released
 `GenerateScreenplaySettings.cs`, `ArcScreenplayGeneration.cs`, v7 planning specs
 and `Documentation/reference/screenplay.md`; older diagnostic probes below keep
 their original labels. Arc#3054 and CLI#270 describe the recovered-source expansion.
@@ -96,8 +98,8 @@ The expanded Arc recovery surface includes:
   deterministic generation fixtures and response expectations can be recovered.
   Unsupported shapes/pre-generation protection remain code with SP0052.
 
-Generated values/responses select ESM v7. CLI 3.41.0 admits v7 to planning, but
-Stage refuses those members with STAGE-ESM-028/029. CLI#261 is closed; do not say
+Generated values/responses select ESM v7. The historical CLI 3.41.0 check
+admitted v7 to planning, but Stage 4.51.3 refused those members with STAGE-ESM-028/029. CLI#261 is closed; do not say
 the compiler or CLI version gate universally refuses v7. Above v7 remains
 CLI-RENDER-004. A generated source model is evidence, not guaranteed render output.
 

package/package/corpus/skills/cratis-screenplay-model-authoring/SKILL.md

@@ -23,7 +23,7 @@ contract is in `cratis-screenplay-ui-composition`.
 
 ## Verified product sources
 
-Current authoring/MCP guidance follows Screenplay v4.127.0
+Current authoring/MCP guidance follows Screenplay v4.131.0
 `Documentation/screenplay/mcp/`, `ast-authoring.md`, `folders.md`, `vscode.md`.
 Discover installed tools and schemas; CLI bundles can differ from the standalone
 tool. Pins are in `cratis-screenplay-toolchain` `references/versions.md`.
@@ -105,6 +105,12 @@ Keep reads scoped to the relevant module, feature, slice or document. Do not
 request a whole merged AST when a bounded declaration/property query answers the
 question. Size-limit refusals require narrower reads, not truncation.
 
+## Compare models
+
+For a `main` comparison, pass a worktree `path` to `semantic-diff`, not two
+exports. Read [comparison sources](references/mcp-tools.md#semantic-revision-comparison)
+for paging and proposal review.
+
 ## Make one coherent proposal
 
 **One edit strategy.** Discover what the server offers. Prefer typed,
@@ -286,7 +292,7 @@ that the code compiles or behaves. Read `references/mcp-tools.md#code-attachment
   syntax plus the consistency rules (`PLAY0282`-`PLAY0294`) but never binds, so a
   clean run is not a bound or executable result.
 - Operations/exact numbers remain unadmitted; source/stream routes bind as ESM v8,
-  and generated values/responses as v7. CLI 3.41.0 render passes v7 to Stage but
+  and generated values/responses as v7. CLI 3.46.1 render passes v7 to Stage but
   refuses newer versions. A source contract is never dropped or stubbed to bind.
 - Distinguish authoring acceptance from `executableReady`; unsupported backend
   capabilities are not a reason to drop source constructs or invent stubs.
@@ -307,11 +313,8 @@ a generated app that silently drops authored UI. Use the Screenplay-owned canoni
 corpus fixture path when it exists instead of copying `.play` examples into this
 repository.
 
-Repair and refactoring guidance follows Screenplay v4.127.0. The Cratis
-CLI bundles its own Screenplay version, so check the installed `tools/list`
-schemas before relying on a view or argument named here (for example
-`dropped-comments` or `implementation-requirements`). Do not invent a command,
-parameter, syntax node or downstream capability.
+Check installed `tools/list` schemas: the CLI bundle can differ. Never invent
+commands, parameters, syntax nodes or downstream capabilities.
 
 ## Route near misses