@cratis/pi 7.34.0 → 7.35.0

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

@@ -7,6 +7,7 @@
 - Coverage (what a provider reads)
 - Diagnostics are the loss list
 - Arc recovery and authoring-only options
+- Arc 22.76.0 enum and response recovery
 - Arc 22.70.0 compliance recovery
 - Generated-document self-check on compiler upgrades
 - Reading the output cheaply
@@ -16,7 +17,7 @@ cratis-screenplay-toolchain `references/versions.md`; behaviour from the cratis
 (`v3.28.2:Source/Cli/Commands/Screenplay/`; the generate files are unchanged since `v3.27.1`), Arc `v22.50.5`
 (`Documentation/backend/csharp/generating-a-screenplay.md`,
 `Source/DotNET/Screenplay/ScreenplayDiagnosticCodes.cs`), Screenplay.Generation `v0.18.0` and
-Screenplay.CritterStack `v0.24.0`. Version-specific capability facts belong in cratis-screenplay-toolchain
+Screenplay.CritterStack `v0.24.0` (the versions cli 3.53.1 bundles). Later releases exist (Generation 0.18.1 preserves compiler warnings, including on successful generation; CritterStack 0.26.0 adds enum concepts, command-to-event production links and the `MixedSliceKindsSplit` and `ProductionLinkOmitted` diagnostics); do not claim them for `cratis screenplay generate` until a cli bundles them. Version-specific capability facts belong in cratis-screenplay-toolchain
 `references/versions.md`.
 
 For the current standalone compiler and CLI bundle, use the toolchain's
@@ -75,7 +76,7 @@ cratis screenplay generate <solution|project|folder> \
 | Provider | Reads | Does not read |
 |---|---|---|
 | Arc | commands, events, concepts, read models, projections, reducers, reactors, constraints, declarative FluentValidation rules, authorization policies, `produces` from constants and input paths, Chronicle integration specs as given/when/then, `.tsx` beside a slice as `screen` + `data via query` | handler bodies, rules written in code, computed messages (`SP0016`), screen bodies, captures, personas, seeds, `@sensitive`. A rule held to `When`/`Unless` is written down as if unconditional and `SP0016` names the condition: read the diagnostic, do not trust the declaration |
-| Marten / Critter Stack (preview) | aggregates, snapshots, HTTP and message handlers, document operations, queries, outgoing and delayed messages, saga facts | saga lifecycle, policies, middleware bodies, runtime tenancy, upcasting; unbounded extension code is reported by presence only |
+| Marten / Critter Stack (preview; an independent optional adapter built on the neutral Screenplay.Generation SDK, not affiliated with JasperFx: review every `GEN`/`MARTEN`/`WOLVERINE` diagnostic by hand) | aggregates, snapshots, HTTP and message handlers, document operations, queries, outgoing and delayed messages, saga facts | saga lifecycle, policies, middleware bodies, runtime tenancy, upcasting; unbounded extension code is reported by presence only |
 | any non-.NET stack | nothing | use Prologue and targeted reads |
 
 ## Diagnostics are the loss list
@@ -123,6 +124,34 @@ Handler/reaction bodies, unresolved conditions and unproven origins still need
 source review. Do not infer generation/evolution/absence-assertion coverage from
 a package upgrade; read diagnostics and reconcile each recovered scenario.
 
+## Arc 22.76.0 enum and response recovery
+
+Source-verified at Arc `v22.76.0:Source/DotNET/Screenplay/Emission/Concepts/ConceptSyntaxBuilder.cs`,
+`Analysis/Types/{ConceptRegistry,FlagsEnumUses}.cs`, `Analysis/EnumConstants.cs`,
+`Analysis/Specifications/SpecificationReturnValues.cs`, and
+`Documentation/backend/csharp/generating-a-screenplay.md`. Arc 22.76.0 takes
+Screenplay 4.139.0, not 4.141.0. The CLI bundles an older generator; see the
+central toolchain `references/versions.md` rather than assuming parity.
+
+Every enum member now emits its stored integer, including positional members.
+Sparse, negative and reordered values preserve identity when representable as int32
+and permitted by `MaximumExecutableModelVersion` (non-positional values need v12).
+SP0068 warns when numbers fall back together to positions because of the range or
+cap, and on dropped emitted-name collisions: do not treat that output as preserving
+stored identity. SP0069 reports aliases sharing a number; the ordinal-first member
+used by scenario constant resolution is kept. SP0067 reports `[Flags]` enums with
+unnamed combinations and names the property uses; named members still emit, but
+unnamed combinations cannot become scenario values. Read every warning as a loss.
+
+Since 22.75.2, `result!` and `in` arguments remain reads for recovered `then returns`.
+Writes through any member/element of the executed result (assignment, increment,
+decrement, `ref`/`out`, including null-conditional chains) or aliases of the result
+or non-string reference values reached through it withhold the response assertion.
+This includes variables/fields/initializers, foreach/pattern variables,
+returned/yielded/lambda values and conditional/coalescing/tuple/collection flows.
+Mutation through ordinary method calls is not analyzed. Inspect reported scenarios;
+never infer a response contract from a post-execution mutation.
+
 ## Arc 22.70.0 compliance recovery
 
 A concept with both `[Encrypted]` and `[NotAudited]` becomes `secret`.
@@ -136,8 +165,9 @@ without adding `secret`; an existing `pii` classification remains.
   `namespace` scope: the document instead implies Subject scope. Global behaves
   the same way. Set `ScreenplayOptions.AuthoringOnlyConstructs = true` (CLI
   adapter option `--authoring-only-constructs`) to emit `secret scope namespace`
-  or `secret scope global` in the concept body. Scope is syntax-only and does
-  not raise the ESM version; it does not make protected concepts executable.
+  or `secret scope global` in the concept body. This was syntax-only on that
+  compiler; standalone 4.141.0 instead admits concept compliance as ESM v13.
+  That upgrade does not change the older generator or CLI bundle.
 - A concept also marked `[PII]` becomes `pii secret`, with no emitted scope:
   the C# providers render only `[PII]`; Chronicle rejects `[PII]` combined with
   `[Encrypted]`. Do not add a scope the provider ignores.

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

@@ -21,8 +21,9 @@ same model root or workspace export to all checks. Workflow:
 
 ## Verified product sources
 
-Current authoring/MCP guidance follows Screenplay v4.139.0
-`Documentation/screenplay/mcp/`, `ast-authoring.md`, `folders.md`, `vscode.md`.
+Screenplay v4.141.0: planner in `references/property-links.md`;
+compliance in command-surface `references/compliance.md`. Other MCP evidence:
+v4.139.0 `Documentation/screenplay/mcp/`.
 Discover installed tools and schemas; CLI bundles can differ from the standalone
 tool. Pins are in `cratis-screenplay-toolchain` `references/versions.md`.
 Historical probes remain 4.66.0; registration example compilation/execution
@@ -295,7 +296,8 @@ that the code compiles or behaves. Read `references/mcp-tools.md#code-attachment
   clean run is not a bound or executable result.
 - Operations/`numbers exact` remain unadmitted; routes bind as v8, public
   boundaries v9, identity/overrides/filters v10, qualifying non-route Double
-  literals v11, non-positional enum numbers v12 (standalone 4.139.0).
+  literals v11, enum numbers v12, compliance v13 (4.141.0;
+  limits: command-surface `references/compliance.md`).
   CLI 3.53.1/Stage 4.73.1 bundle 4.137.0 and do not admit v12. Never drop or stub source contracts to bind.
 - Distinguish authoring acceptance from `executableReady`; unsupported backend
   capabilities are not a reason to drop source constructs or invent stubs.

package/package/corpus/skills/cratis-screenplay-model-authoring/references/language-reference.md

@@ -266,7 +266,7 @@ See read-surface `references/named-keys.md` for the collection-key exclusion alg
 | Binds as ESM v7 on standalone Screenplay 4.68.0 (source and release notes; `PLAY0268` on the 4.66.0 in Cratis CLI 3.28.x, probed) | `generated` properties and `returns` responses, generated fixtures and `then returns`: bound and executed by the reference runner; a policy, rule or requirement that references a generated value is `PLAY0273`, and a generated property on a concept with validation rules is `PLAY0268`. Stage 4.73.1 refuses them (`STAGE-ESM-028`/`-029`, Stage#175): gap-fill |
 | Authorable, not executable (PLAY0268) | Systems/operations, the `numbers exact` source mode (PLAY0268; exact lowering of qualifying Double literals is the admitted v11) and refusal/redelivery remain unadmitted |
 | Current routing and actor admission | Sources/streams and command/specification routes bind and reference-execute as v8; reaction `runs as system role` supplies the invocation actor as v10 on 4.125.0. Whole-workspace binding determines executable availability; CLI/Stage realization remains separate |
-| Blocks binding (`PLAY0268`) | `pii`/`secret` concepts (also legacy spellings; historical probe: "compliance attributes require portable data-subject semantics"), command `handler` (never binds; a command cannot declare both `produces` and `handler`, `PLAY0035`), bare `rule <Name>`, `require` or conditions over read-model paths, dates and `today` in comparisons, `$context.tenant`/claims/roles/causation in `produces`, `$env` conditions, `file` constraints, unquoted `import` of an external contract, a read model with neither explicit `key` nor unambiguous query-based identity as described above (composite keys remain unadmitted), queries with filters, scope, performer, context-derived `by` or composite `by` blocks (optional keyed and collection queries, including observable delivery, bind at 4.135.0), `$causedBy` and templates in projections |
+| Blocks binding (`PLAY0268`) | enum/identity compliance and events combining personal or explicitly subject-scoped secret values with explicit subject marks (4.141.0); the older CLI bundle refuses all `pii`/`secret` concepts (historical probe: "compliance attributes require portable data-subject semantics"); command `handler` (never binds; a command cannot declare both `produces` and `handler`, `PLAY0035`), bare `rule <Name>`, `require` or conditions over read-model paths, dates and `today` in comparisons, `$context.tenant`/claims/roles/causation in `produces`, `$env` conditions, `file` constraints, unquoted `import` of an external contract, a read model with neither explicit `key` nor unambiguous query-based identity as described above (composite keys remain unadmitted), queries with filters, scope, performer, context-derived `by` or composite `by` blocks (optional keyed and collection queries, including observable delivery, bind at 4.135.0), `$causedBy` and templates in projections |
 | Blocks binding (`PLAY0271`, legacy meaning) | Command `reads` and `concurrency` |
 | Deferred (`PLAY0269`, information) | Screens, layouts, templates, forms, contributions, UI profiles, themes, behaviors and `on`/`uses` |
 | Metadata only (`PLAY0270`, information) | `domain`, `seed`, `persona`, trigger and other descriptions, and `file` provenance on declarations |

package/package/corpus/skills/cratis-screenplay-model-authoring/references/mcp-tools.md

@@ -51,7 +51,7 @@ the [MCP loop](mcp-loop.md).
 | Source and validation | `diagnostics`, `read-document`, `merged-document`, `syntax-schema` | Read exact source or typed structure and diagnose problems |
 | Workspace inspection | `open-workspace`, `read-workspace`, `read-ast`, `workspace-state`, `export-workspace`, `repair-capabilities` | Obtain current identities, handles, readiness, code attachment requirements, source-map locations, durable-state status and the repair catalog |
 | Visual (MCP-Apps hosts only) | `visualize-model` | Draw the board for the model or a `proposalId`; its `sketch` argument previews a what-if of whole documents. Reads only |
-| Planning | `propose-source`, `propose-ast`, `propose-rename`, `propose-move`, `propose-repair`, `propose-number-enum-members`, `propose-extract-inline-event`, `propose`, `recommend-layout`, `expand-layout` | Produce validated, reviewable candidates without writing them |
+| Planning | `propose-source`, `propose-ast`, `propose-rename`, `propose-move`, `propose-repair`, `propose-property`, `propose-number-enum-members`, `propose-extract-inline-event`, `propose`, `recommend-layout`, `expand-layout` | Produce validated, reviewable candidates without writing them |
 | Review | `read-proposal`, `discard-proposal` | Inspect exact changes, dropped comments and proposed attachments, or abandon a connection-local proposal |
 | Effects | `apply`, `recover-workspace` | Apply an accepted plan or explicitly recover an interrupted write |
 
@@ -59,7 +59,9 @@ the [MCP loop](mcp-loop.md).
 
 `propose` is the executable-only whole-document interface. Prefer `propose-source`
 for whole `.play` text, `propose-ast` for focused typed edits, and `propose-rename`
-for proved logical renames. A
+for proved logical renames. Standalone 4.140.0 adds `propose-property` for explicit
+property rename/removal selections, AutoMap preservation and event-generation
+choices; read [property evidence and planning](property-links.md) before proposing. A
 source-only authoring proposal may be accepted while `executableReady` is false.
 That is not permission to claim the application runs.
 

package/package/corpus/skills/cratis-screenplay-model-authoring/references/property-links.md

@@ -7,11 +7,13 @@
 
 - Address and query
 - Read evidence, not just a count
+- Propose a property change (4.140.0)
 
 Screenplay 4.138.0 released property-path evidence in `find-references` and
 `dependencies`; this guidance was checked against 4.139.0. Discover installed
 `tools/list`: CLI 3.53.1's 4.137.0 bundle predates it. These are read-only
-inspection tools, not a property-change planner.
+inspection tools. Standalone 4.140.0 adds the separate `propose-property` planner
+below; the CLI bundle has neither capability.
 
 ## Address and query
 
@@ -122,5 +124,42 @@ needs a persisted-contract evolution decision; the catalog is not storage eviden
 
 Source/output authority: `v4.139.0:Documentation/screenplay/mcp/reference.md`
 (property links), `Source/DotNET/Screenplay.Mcp/McpPropertyDependencies.cs`,
-`McpToolSchemas.cs`, and decision 0044's released prerequisite index. The planner
-phases in that decision are not release evidence.
+`McpToolSchemas.cs`, and decision 0044's released prerequisite index. The planner's release evidence is separate below.
+
+## Propose a property change (4.140.0)
+
+Read the target property handle with `read-ast`, then call `propose-property`
+with `expectedRevision`, `expectedCatalogRevision`, `action: "rename"|"remove"`,
+`target` and `expectedName`. Rename also needs `newName`. Optional `alsoRename`
+or `alsoRemove` entries are `{ "target": <handle>, "expectedName": <name> }`.
+Select only intended command, current-event and non-key read-model properties:
+chain membership establishes eligibility, not permission to edit every field.
+Off-chain selections refuse atomically. Historical generations, inline events,
+keys, opaque or incomplete links and unsupported spans refuse rather than guess.
+
+Rename repairs proven references and fixtures. Renaming only a command input
+keeps the event payload name; broken AutoMap links become explicit mappings.
+Removal refuses while readers remain. Removed expected values disclose
+`weakensAssertion: true`; when inherited `then` steps cannot be determined, removal
+refuses `AmbiguousPropertyReference`, not a false assertion-preservation verdict.
+Unrelated same-named fields appear in `property.notChanged`.
+
+For any selected event property, choose exactly one mode: `newGeneration: true`
+appends N+1 and preserves history; `eventNeverPersisted: true` edits current N in
+place and requires actual knowledge that it was never stored. Neither flag selects
+additional events. New generations require transformations before Chronicle deployment.
+
+Default validation is `Authoring` (optional `Executable`), formatting
+`PreserveTrivia`, reference policy always `Safe`. Structural changes require
+explicit `CanonicalizeTouchedDocuments` consent. Inspect retained `read-proposal`
+and `view: "semantic-diff"` before `apply`; only apply writes source and identities.
+Review `property.generations`, always an array ordered by canonical event address,
+with one entry per selected event: `event`, `from`, `to`, `mode`. In-place edits
+have equal revisions. `[]` means no accepted planned event edits, not success;
+there is no singular `property.generation`. `deployableWithoutTransformation`
+and `esmVersionKnown` are independent of authoring acceptance.
+
+Authority: Screenplay `v4.140.0:Source/DotNET/Screenplay.Mcp/McpWorkspaces.Property.cs`,
+`Screenplay/Workspaces/WorkspaceProperty{Request,Plan,Safety,Report}.cs`,
+`WorkspacePropertyAssertionProvenance.cs`, `WorkspaceEventGenerations.cs`, and
+`Documentation/screenplay/mcp/authoring-tools.md`; decision 0067.

package/package/corpus/skills/cratis-screenplay-model-authoring/verification.json

@@ -4,9 +4,11 @@
   "fixtures": [],
   "assertions": [
     { "kind": "play-compiles" },
+    { "kind": "skill-contains", "value": "weakensAssertion: true", "file": "references/property-links.md" },
+    { "kind": "skill-contains", "value": "property.generations", "file": "references/property-links.md" },
     {
       "kind": "skill-contains",
-      "value": "Screenplay v4.139.0"
+      "value": "Screenplay v4.141.0"
     },
     {
       "kind": "skill-contains",

package/package/corpus/skills/cratis-screenplay-modeling-lifecycle/references/vocabulary-map.md

@@ -21,7 +21,7 @@ speaks in them; never model board mechanics (lanes, node ids, positions).
 | Storyline (ordered beats) | a **family** of specifications sharing example data, each one transition (no storyline syntax at Screenplay 4.139.0) | several spec classes | specifications |
 | Field validation | concept `validate` (every use) / command `validate`, `require` | `ConceptValidator<T>` / `CommandValidator<T>` | command validation |
 | Role permission ("Cannot") | `policy` + `authorize` + `then denied` spec; ownership via `claim ... matches subject` | `[Authorize(Policy)]`, generated policies | authorization |
-| Precondition on stream state | `reads` + `require` as stated intent, not enforced at Screenplay 4.139.0 (target: Arc `[ProtectedDecision]` + `DecisionRead<T>`, or Chronicle DCB; APIs available to gap-fill in Stage 4.73.1's scaffold of Arc 22.68.0/Chronicle 19.45.0, not emitted protection) | decision over a guarded read | command validation |
+| Precondition on stream state | `reads` + `require` as stated intent, not enforced at Screenplay 4.139.0 (target: Arc `[ProtectedDecision]` + `DecisionRead<T>`, or Chronicle DCB; APIs available to gap-fill in the Arc and Chronicle the Stage 4.73.1 scaffold pins, not emitted protection) | decision over a guarded read | command validation |
 | Generated id (`derived:uuid4()`) | `generated` (authorable, not executable) | id supplied before `Handle()` | commands |
 | External system / outbound call | `Translate` slice (inbound); `system`/`operation` (authorable, not executable) or Automation (outbound) | `ICommandOperation` / reactor | operations, reactors |
 | HTML mockup | `screen` Level 1 + board (`visualize-model`) | default Scene composition | ui composition |
@@ -44,7 +44,7 @@ Screenplay meaning, and when you meet the older usage, translate it and say so.
 - Chronicle **reactor**: C# observer, usually for side effects; it does not by itself define
   business decisions. A Screenplay reaction is authorable and bindable, but Stage 4.73.1 renders no Automation or
   Translate slice: the reactor and command are gap-fill code. A reaction that both produces events and invokes commands is
-  refused by Stage (`STAGE-ESM-037`); Arc 22.72.0 and later run one reactor returning events and commands (the Stage scaffold's Arc 22.68.0 needs a proven override), so keep the reaction whole.
+  refused by Stage (`STAGE-ESM-037`); Arc 22.72.0 and later run one reactor returning events and commands (the Arc the Stage scaffold pins needs a proven override), so keep the reaction whole.
 
 ## Scenario vs specification
 "Scenario" is the Event Modeling example and the scenario *types* `cratis-screenplay-scenario-coverage` uses for

package/package/corpus/skills/cratis-screenplay-render-and-gap-fill/SKILL.md

@@ -23,11 +23,11 @@ rule is in `cratis-screenplay-modeling-lifecycle` ("Decide the level first"); it
 ## Verified product sources
 
 Version pins live once in `cratis-screenplay-toolchain` `references/versions.md`; read it before
-selecting the compiler and renderer for delivery. Current pair: CLI 3.53.1 bundling Screenplay
-4.137.0 and Stage 4.73.1 (the standalone compiler is newer, 4.139.0). Render options (`--scope`,
+selecting the compiler and renderer for delivery: the CLI bundles its own Screenplay and Stage, older
+than the standalone compiler. Render options (`--scope`,
 `--check`, `--package-set`) and exit codes were read at cli `v3.53.1` `Documentation/reference/screenplay.md`
-and `cratis render --help`; admission at Stage `v4.73.1`. Stage's scaffold pins Arc 22.68.0 and
-Chronicle 19.45.0, which are not the latest releases (`cratis-stage-rendering-and-sandbox`
+and `cratis render --help`; admission at Stage `v4.73.1`. Stage's scaffold pins Arc and
+Chronicle releases, which are not the latest (`cratis-stage-rendering-and-sandbox`
 `references/rendered-application.md`). Source reading is not a new render run.
 
 Runs: the worked example (`references/worked-example.md`) was probed with cratis 3.53.1 (observed; the
@@ -90,7 +90,7 @@ Stage (`STAGE-ESM-037`, Stage#207) although Arc 22.72.0 and later run one reacto
 and commands (events appended first as one batch, then commands in order, no cross-effect
 transaction; a retry can repeat the events, so use `[OnceOnly]`/idempotent handling per
 `cratis-chronicle-reactor`). Keep the modeled reaction whole and gap-fill it as that one reactor; never
-split it or drop an effect to get a render. The scaffold pins Arc 22.68.0; whether a newer Arc
+split it or drop an effect to get a render. The scaffold pins an older Arc; whether a newer Arc
 override in `Customizations/Dependencies.props` restores next to it is unverified, so prove it with a restore and build.
 
 Two rules hold in every case: a customization never makes a rejected model renderable, and
@@ -153,7 +153,7 @@ Adapters and non-renderable scope follow the contract rules of `cratis-applicati
 - One ledger scope per `slice-implementer` brief; the brief carries addresses and paths, not contents.
 - Model-enforced rules realized in code (state-dependent rules) need a protected read or
   concurrency scope; never claim them from prose. Stage 4.73.1 rendered apps scaffold
-  Arc 22.68.0/Chronicle 19.45.0; API availability alone is not verified enforcement.
+  the Arc/Chronicle set in `cratis-stage-rendering-and-sandbox` `references/rendered-application.md`; API availability alone is not verified enforcement.
 - Adapters that call outside systems follow `cratis-engineering-effect-boundaries`; slice
   specifications follow `cratis-application-slice-specifications`.
 - Realization notes are the explicit realization requirements stated in a slice `description` or `documentation`

package/package/corpus/skills/cratis-screenplay-render-and-gap-fill/references/drift-and-ledger.md

@@ -34,7 +34,7 @@ Compare in this order:
    never V4 or V5; it needs the same generation options (`--domain`, `--feature-root`, `--module`,
    `--skip-segments`, `--modules-from-namespace-roots`) that reproduce the authored placement, or
    everything looks missing. MSBuild evaluates the project (use a trusted clone) and the bundle's
-   `Cratis.Arc.Screenplay` is 22.54.0, so recovery behaves like that adapter. It does not replace
+   `Cratis.Arc.Screenplay` is the version in `cratis-screenplay-toolchain` `references/versions.md`, so recovery behaves like that adapter. It does not replace
    `cratis-application-slice-conformance`, which reconciles specifications, rules and behavior.
    Whether it is meaningful on a Stage-rendered application is unverified.
 

package/package/corpus/skills/cratis-screenplay-render-and-gap-fill/references/gap-fill-handoff.md

@@ -69,7 +69,7 @@ ambiguous addresses; contracts are never inferred from names.
 A rule that exists only in a description, or a state-dependent rule the model marks as not
 enforced, is unenforced in generated scope. List it in the ledger as a target requirement. In
 hand-written code it needs an atomic enforcement point: a protected read or a concurrency scope
-(Stage 4.73.1 rendered apps scaffold Arc 22.68.0/Chronicle 19.45.0: protected-read APIs
+(Stage 4.73.1 rendered apps scaffold the Arc/Chronicle set in `cratis-stage-rendering-and-sandbox` `references/rendered-application.md`: protected-read APIs
 are available to gap-fill, with projection/key admission and active enrollment), or a Chronicle constraint. A stale view or
 a caller-supplied status is not enforcement.
 
@@ -93,11 +93,13 @@ captures-and-reactions `references/invocation-identity.md`.
 
 A reaction that both produces events and invokes commands keeps its single modeled form
 (`STAGE-ESM-037` is Stage's refusal, not a model defect). Hand-write one reactor returning the events
-and the commands: on Arc 22.72.0 or later (the Stage 4.73.1 scaffold pins Arc 22.68.0, whose command handler accepts a collection only when every element is a command, so a rendered app needs a proven dependency override) the runtime appends the events first as one batch, then
+and the commands: on Arc 22.72.0 or later (the Arc the Stage scaffold pins accepts a collection in a command handler only when every element is a command, so a rendered app needs a proven dependency override) the runtime appends the events first as one batch, then
 runs the commands in order, with no transaction across the two effects; a failing command stops the
 later ones but keeps the committed events, and a retry can append the events again, so make the
-handler idempotent (`[OnceOnly]` and the failure behavior in `cratis-chronicle-reactor`). Return a
-stable array or list. The Stage scaffold pins Arc 22.68.0, so raise the version through
+handler idempotent independently of `[OnceOnly]`, which excludes replay only, not recovery
+or crash redelivery (Chronicle v19.50.1 `Documentation/code-analysis/CHR0022.mdx`;
+see `cratis-chronicle-reactor`). Return a
+stable array or list. The Stage scaffold pins an older Arc, so raise the version through
 `Customizations/Dependencies.props` only after a restore and build proves it. Never split the
 reaction or drop an effect to dodge rendering.
 

package/package/corpus/skills/cratis-screenplay-render-and-gap-fill/references/renderability-gate.md

@@ -30,7 +30,7 @@ ESM). Only the probe answers renderability. `PLAY0270` entries are information,
 | Class | Meaning | Typical examples (each verified in `admission.md`) | Action |
 | --- | --- | --- | --- |
 | **Model fix (in mode)** | the model is in, or the user chose, renderable mode and breaks its own subset in a way that has a renderable equivalent with the same meaning | a `produces` whose `for` is not the command identifier; one `StateChange` slice with two commands (`STAGE-ESM-004`); two projections for one read model (`-007`); a policy Stage cannot express portably (`-015`; role-only and opaque pure policies render at 4.73.1) | edit request to the modeler session with address, change and rationale |
-| **Capability gap** | the intended meaning needs a construct Stage does not render yet | a snapshot list query (`-010`; observable lists and keyed or unkeyed lists bind and observable lists render), and `filter`, `scoped to`, `performer` queries (`PLAY0268`); Automation and Translate slices (`-001`/`-024`, Stage#79); reactions, clocks, captures and triggers (`-024`); a reaction that both produces and invokes (`-037`: keep it whole and hand-write one reactor on Arc 22.72.0 or later (the scaffold pins 22.68.0: a proven override), never split it; Stage#207); generated values and responses (`-028`/`-029`, Stage#175); `then no readmodel` (`-027`); evolved events (`STAGE-ESM-026`); conditional `produces when` (`-006`); `reads` (`PLAY0271`); code validation (`-005`); compliance attributes (`PLAY0268` "require portable data-subject semantics"); a command `handler` (`PLAY0268`) | keep the model; ledger entry; options a to c in `SKILL.md`; link the Stage issue |
+| **Capability gap** | the intended meaning needs a construct Stage does not render yet | a snapshot list query (`-010`; observable lists and keyed or unkeyed lists bind and observable lists render), and `filter`, `scoped to`, `performer` queries (`PLAY0268`); Automation and Translate slices (`-001`/`-024`, Stage#79); reactions, clocks, captures and triggers (`-024`); a reaction that both produces and invokes (`-037`: keep it whole and hand-write one reactor on Arc 22.72.0 or later (the Arc the scaffold pins needs a proven override), never split it; Stage#207); generated values and responses (`-028`/`-029`, Stage#175); `then no readmodel` (`-027`); evolved events (`STAGE-ESM-026`); conditional `produces when` (`-006`); `reads` (`PLAY0271`); code validation (`-005`); compliance attributes (`PLAY0268` "require portable data-subject semantics"); a command `handler` (`PLAY0268`) | keep the model; ledger entry; options a to c in `SKILL.md`; link the Stage issue |
 | **Tool skew** | the bundled compiler disagrees with documented semantics | the false `PLAY0285` on reaction cascades from a cratis before 3.28.2 bundle (cli#242); codes the standalone compiler does not raise | record in the session state and the ledger; never "fix" a correct model |
 | **Environment** | not the model | restore failures, missing SDK, a destination that is not writable | fix the environment or report blocked |
 

package/package/corpus/skills/cratis-screenplay-scenario-coverage/SKILL.md

@@ -71,7 +71,9 @@ question is not four approvals.
    payload: one line per read model. One schema reused for every command and view may indicate
    the per-view judgment was skipped: check for a recorded reason per view before concluding.
 6. **Example data**: a small cast per feature; reuse only where meaning agrees; preserve
-   existing intentional fixtures (`references/scenario-catalogue.md` "Example data").
+   existing intentional fixtures (`references/scenario-catalogue.md` "Example data"). Shared
+   fixtures may live as typed `example`s in another document beside the declarations they type
+   (`cratis-screenplay-specifications` `references/examples-and-routes.md`).
 7. **Draft commands**: happy path, each rule, denial, duplicates and retries, competing claims,
    state violations, alternative branches, compensation, external failure, evolution. In each
    rejection vary only the value under test. Use typed `parameter`/named `case`

package/package/corpus/skills/cratis-screenplay-scenario-coverage/references/invoicing-dues-design.md

@@ -14,7 +14,7 @@ replaced by prose. The runnable counterpart, which holds no stored-state rule, i
 `invoicing-dues-example.md`; `scenario-examples.md` copies `ReversingAReceivedPayment` from here.
 
 The excerpt's Stage API-availability comment describes the historical Stage 4.24.x
-scaffold. Stage 4.73.1 pins Arc 22.68.0/Chronicle 19.45.0: protected-read APIs are
+scaffold. Stage 4.73.1's scaffold pins an Arc/Chronicle set (see the Stage skill's `references/rendered-application.md`): protected-read APIs are
 available to gap-fill (the "not in a Stage-rendered application" comment in the source is
 superseded), not emitted protection or `.play` rule admission. The
 original compiled source is retained unchanged.

package/package/corpus/skills/cratis-screenplay-slice-design/SKILL.md

@@ -81,7 +81,7 @@ report and slice `documentation`, and continue.
    over stored state is written as `reads <View>` + `require ... message "..."` and marked
    **NOT enforced in the model today** in the slice `description`, with its target named (Arc
    `[ProtectedDecision]` + `DecisionRead<T>` on Arc 22.39.0+ (available to gap-fill
-   code with Stage 4.73.1's Arc 22.68.0/Chronicle 19.45.0); Chronicle DCB; or a constraint). Never copy state
+   code with the Arc and Chronicle the Stage 4.73.1 scaffold pins); Chronicle DCB; or a constraint). Never copy state
    into the command as input or hide a rule in `handler` / hint prose; descriptions reach code
    only as XML comments (Stage#178). Fill the **refusal inventory**: success, each distinct refusal with
    layer and message, and the denied persona.

package/package/corpus/skills/cratis-screenplay-slice-design/references/rule-layers.md

@@ -15,7 +15,7 @@ code only as XML doc comments (Stage#178): a rule that exists only in prose is u
 
 An unguarded materialized read is unsafe for a protected decision; a guarded read is the
 supported route. Availability: `[ProtectedDecision]` and `DecisionRead<T>` exist in
-Stage 4.73.1's Arc 22.68.0/Chronicle 19.45.0 package set, but Stage does not emit
+the Arc/Chronicle package set Stage 4.73.1 scaffolds (see the Stage skill's `references/rendered-application.md`), but Stage does not emit
 protected decisions. Gap-fill must use an admitted projection/key shape and active
 unit-of-work enrollment; do not edit managed dependencies. Keep the `.play` rule
 NOT enforced until its target enforcement is separately verified. Forbidden: caller-supplied copies of state in `require`, boolean attestation
@@ -33,7 +33,7 @@ second caller with another claim value.
 
 Command property values are, by default, recorded in the causation chain of the events they
 produce, so treat them as permanent. Newer Chronicle versions can omit causation properties
-(`CausationPropertyRetention.Omit`, Chronicle v19.32.0); Stage 4.73.1 rendered apps pin 19.45.0 (the latest Chronicle is 19.50.0).
+(`CausationPropertyRetention.Omit`, Chronicle v19.32.0); Stage-rendered apps pin the Chronicle release listed in the Stage skill's `references/rendered-application.md` (not the latest).
 Verify the actual auditing and retention configuration before relying on omission, and never
 audit secrets. Classify personal values as bare `pii` and operational secrets as
 `secret` on their concepts, never the identifier concept. Use a surrogate identity

package/package/corpus/skills/cratis-screenplay-slice-design/references/worked-example.md

@@ -19,7 +19,7 @@ and record lineage reasoning in fenced Markdown `documentation` (`field-lineage.
 The historical source below stays unchanged; it is not the current placement recipe.
 
 The excerpt's Stage availability note is historical (Stage 4.24.x, Arc 22.25.0).
-Stage 4.73.1 pins Arc 22.68.0/Chronicle 19.45.0, so protected-read APIs are available
+Stage 4.73.1's scaffold pins an Arc/Chronicle set (see the Stage skill's `references/rendered-application.md`), so protected-read APIs are available
 to gap-fill (the compiled description below saying they are "not available in Stage-rendered apps" is superseded); this neither admits these `.play` rules nor proves target protection.
 The original compiled excerpt is retained unchanged.
 

package/package/corpus/skills/cratis-screenplay-specifications/references/examples-and-routes.md

@@ -6,6 +6,7 @@
 ## Contents
 
 - Typed examples
+- Examples typed from another document
 - Effective values
 - Event routes
 - Redelivery locators
@@ -49,6 +50,53 @@ module Projects
           name = "Override"
 ```
 
+## Examples typed from another document
+
+An example's type may be an event, command or read model declared in another
+document of the same compilation, by simple name when unambiguous or by qualified
+name (`Billing.Facts.Recording.Recorded`). Checked against Screenplay v4.139.0
+(Screenplay#648, released in 4.135.1) and the standalone 4.139.0 compiler:
+
+```text
+// declarations.play: module Billing > feature Facts > slice StateChange Recording
+//   declares command Record, event Recorded and a specification using the examples
+// application.play
+import "declarations.play"
+
+example Fact : Billing.Facts.Recording.Recorded
+  amount = 10
+  for "one"
+example Input : Record
+  id = "one"
+  amount = 20
+```
+
+That folder compiled with warnings as errors and `screenplay test` passed the
+specification that uses `given Fact` and `when Input`. Rules:
+
+- A document checked on its own defers an imported type, as for an inline
+  `given`; it reports no `PLAY0520` there.
+- Values are checked only when the compilation includes the declaration. A wrong
+  value (a string for an `Int`) surfaces as `PLAY0525` at binding (`screenplay
+  test`), not at compile.
+- A type that is still unknown or ambiguous after assembly, or names a concept,
+  type or another example, is `PLAY0520`. A scratch file importing only the
+  contract name is exactly that case:
+
+```screenplay expect PLAY0520
+import Billing.Facts.Recording.Recorded
+example Fact : Recorded
+  amount = 10
+```
+
+- Import the declaring file (`import "declarations.play"`), not the contract
+  name. A named `import X.Y.Z` of a declaration the application already has warns
+  `PLAY0290` (no effect), and binding still refuses any named import with
+  `PLAY0268`, as for inline givens; public `from "<store>"` imports are refused
+  the same way (#481).
+- The example is resolved in its own declaration scope, so shared example data may
+  live beside the declarations it types, in any document.
+
 ## Effective values
 
 An example occupies the ordinary name slot in given/event, given readmodel,

package/package/corpus/skills/cratis-screenplay-specifications/verification.json

@@ -79,6 +79,8 @@
     {
       "kind": "skill-contains",
       "value": "Cratis/cli#242", "file": "references/reactions-and-cascades.md"
-    }
+    },
+    { "kind": "skill-contains", "value": "Examples typed from another document", "file": "references/examples-and-routes.md" },
+    { "kind": "skill-contains", "value": "`PLAY0520`", "file": "references/examples-and-routes.md" }
   ]
 }

package/package/corpus/skills/cratis-screenplay-streams-and-consistency/SKILL.md

@@ -28,8 +28,8 @@ Require target evidence that the check ran: a concurrent first-append scenario a
 Chronicle, asserting one append wins, one is rejected, and `IAppendResult.ConcurrencyCheckPerformed`
 is `true` (a skipped check and a passing one look identical otherwise; a current client against
 an older kernel always reads `false`). This was source- and documentation-inspected, not
-concurrency-tested here. The Stage 4.73.1 scaffold pins Chronicle client/kernel 19.45.0
-and Arc 22.68.0 (the CLI bundle's Chronicle is 19.32.0); the APIs exist for gap-fill, not as automatically rendered enforcement.
+concurrency-tested here. The Stage scaffold pins Chronicle client/kernel and Arc releases (see `cratis-stage-rendering-and-sandbox` `references/rendered-application.md`;
+the CLI bundle's Chronicle is in `cratis-screenplay-toolchain` `references/versions.md`); the APIs exist for gap-fill, not as automatically rendered enforcement.
 
 ## Verified product sources
 
@@ -38,7 +38,7 @@ and Arc 22.68.0 (the CLI bundle's Chronicle is 19.32.0); the APIs exist for gap-
 | Screenplay | v4.68.0 (`79801bf`) | ESM v7 generated values (`generated identifier`, decision 0026) and decision 0025's numbering; the diagnostics below were read at v4.66.0 (`c89198b`): `identifier`, `for`, constraints, generations, `id` pins, diagnostics PLAY0019/0135/0268/0271/0273/0391-0393/0446-0449/0469/0471 |
 | Chronicle | v19.50.0 (read; first read at v19.32.0 `f17a2ff`) | CHR0012, CHR0034; open defects #3744, #4123, #4131 (still open) |
 | Arc | v22.72.0 | `[ProtectedDecision]` and `DecisionRead<T>` (since v22.39.0) |
-| Stage | v4.73.1 | rendered apps pin Arc 22.68.0 and Chronicle client/kernel 19.45.0; protected-read APIs available to gap-fill. Historical 4.24.2 admission probe: ESM v4, evolved events refused with `STAGE-ESM-026` |
+| Stage | v4.73.1 | rendered apps pin the Arc and Chronicle client/kernel listed in the Stage skill's `references/rendered-application.md`; protected-read APIs available to gap-fill. Historical 4.24.2 admission probe: ESM v4, evolved events refused with `STAGE-ESM-026` |
 
 Full pin table: `references/versions.md` in `cratis-screenplay-toolchain`. Re-check the three
 Chronicle issues before relying on a constraint in a later release.
@@ -156,8 +156,10 @@ option, mark it `ASSUMED` in the slice or module `documentation` and in the sess
   block compiles but is PLAY0271 at binding. Keep both when they state real intent; they are not
   protection. `description` text never reaches rendered code: a rule that lives only in prose is
   unenforced there.
-- `pii` and `secret` block binding (PLAY0268); legacy markers are deprecated
-  (PLAY0565). Never remove protection to pass a tool. PLAY0515 also refuses
+- `pii` and `secret` bind as ESM v13 on standalone 4.141.0, not the pinned CLI;
+  enum/identity compliance and protected events with explicit subject marks still
+  refuse PLAY0268 (command-surface `references/compliance.md`). Legacy markers are
+  deprecated (PLAY0565). Never remove protection to pass a tool. PLAY0515 also refuses
   scalar/composite stream-id types and route mapping sources, including nested paths.
 - At 4.127.0 stream-id literals must be nonempty, well-formed NFC text (refused,
   not normalized); integer ids in Double mode stay within ±(2^53−1). Exact mode

package/package/corpus/skills/cratis-screenplay-streams-and-consistency/references/chronicle-boundaries.md

@@ -10,8 +10,8 @@ event-source id) are present. Three runtime defects are **open at v19.50.0**: #3
 InMemory providers do not settle unique claims), #4123 (constraint index updates run after commit
 and fail silently) and #4131 (composite unique constraints collide when a component contains the
 separator). Arc **v22.72.0** has `[ProtectedDecision]` (since v22.39.0, needs Chronicle 19.23 or
-later); Stage 4.73.1 rendered apps pin Arc 22.68.0 and Chronicle client/kernel
-19.45.0, so the APIs are available to gap-fill, not automatically emitted or
+later); Stage-rendered apps pin an Arc and Chronicle client/kernel release
+(see the Stage skill's `references/rendered-application.md`) that include them, so the APIs are available to gap-fill, not automatically emitted or
 protected (see `consistency-and-concurrency.md` section 3). Re-check the issues before relying on a
 constraint in a new release.
 A concurrency scope's first append is unchecked by default at v19.50.0 (the default is planned to become checked in the next major, `Documentation/events/concurrency.mdx`); see

package/package/corpus/skills/cratis-screenplay-streams-and-consistency/references/consistency-and-concurrency.md

@@ -109,8 +109,8 @@ example a course capacity computed from enrolment streams, needs option a or b:
 deciding fact on the source that owns the state, or give each scarce item its own identity. Sources: Arc `v22.72.0:Documentation/backend/csharp/chronicle/read-models/injecting-into-commands.md` (limits unchanged since v22.50.5);
 `chronicle-boundaries.md`.
 
-**Availability in Stage-rendered applications.** Stage 4.73.1 scaffolds Arc 22.68.0
-and Chronicle client/kernel 19.45.0 (not the latest releases). `[ProtectedDecision]` and `DecisionRead<T>` /
+**Availability in Stage-rendered applications.** The Stage scaffold pins Arc and Chronicle client/kernel
+releases (not the latest). `[ProtectedDecision]` and `DecisionRead<T>` /
 `IDecisionReads` exist in that package set; source checks are in
 `cratis-stage-rendering-and-sandbox` `references/rendered-application.md`.
 This does not mean Stage emits protected decisions. Gap-fill must opt into the

package/package/corpus/skills/cratis-screenplay-streams-and-consistency/references/streams-example.md

@@ -5,16 +5,17 @@ cross-stream references as payload, three kinds of uniqueness constraint, a stat
 rule recorded as **NOT enforced in the model today**, a declared `concurrency` scope, and an
 active-state view with removal. Read it with `consistency-and-concurrency.md` (sections 1-4).
 
-The model compiles at 4.127.0 (V1, warnings as errors) but is not binding-ready by design: the `pii`
-concept fails binding (PLAY0268), `reads` and the `concurrency` block are PLAY0271, and
-`require` over a view is PLAY0268. Keep those lines: they state real intent.
+The model compiles at 4.127.0 (V1, warnings as errors) but is not binding-ready by design:
+`reads` and the `concurrency` block are PLAY0271, and `require` over a view is PLAY0268.
+The `pii` concept failed binding on that compiler and still fails on the pinned CLI,
+but binds as v13 on standalone 4.141.0. Keep those lines: they state real intent.
 
 ```screenplay expect PLAY0516 test=unbound
 // cratis-screenplay-streams-and-consistency: complete design-mode example (V1 with --warnings-as-errors).
 // Shows: one business identity per stream, cross-stream references as payload, uniqueness
 // constraints (single, composite with release, unique event), a recorded state-dependent rule
 // that Screenplay cannot enforce, a declared concurrency scope, and an active-state view with removal.
-// Historical binding probes refused compliance; the pii concept still fails binding (PLAY0268), the
+// Historical/CLI binding probes refuse compliance; standalone 4.141.0 binds this pii concept as v13, the
 // concurrency block and `reads` are PLAY0271, `require` over a view is PLAY0268. Keep them: they state
 // real intent. The capacity rule is NOT enforced in the model today (see the slice description).
 

package/package/corpus/skills/cratis-screenplay-toolchain/SKILL.md

@@ -22,7 +22,7 @@ files is one application: always check the folder, never one file of it.
 
 When choosing or upgrading a tool, or checking version-specific capabilities, read `references/versions.md`; it is the only version table, and other skills point to it. For exact diagnostic codes, MCP names/parameters and standalone CLI options, search the large published [references/screenplay-contract.json](references/screenplay-contract.json), pinned by [references/screenplay-contract.version](references/screenplay-contract.version), rather than loading it in full. Locate a diagnostic by its exact `code` (for example `"code": "PLAY0029"`), a tool by its exact `name` (for example `"name": "read-workspace"`), or a command in `cliCommands`; read the matched object for retirement, parameters or options. [references/screenplay-contract-exceptions.json](references/screenplay-contract-exceptions.json) records reasoned exceptions for historical statements; it does not change the current contract.
 
-The standalone pin is Screenplay 4.139.0.
+The standalone pin is Screenplay 4.141.0.
 CLI and bundled package pins: `references/versions.md`. The single version table records
 released source evidence and historical probes separately; do not relabel an old
 render/browser result as a probe of the current packages.
@@ -31,7 +31,7 @@ Historical screens-release evidence: CLI 3.40.7 / Stage 4.51.1 / bundled
 Screenplay 4.114.0 opened the canonical corpus with `executableReady true`
 and the stdio transcript exposed 37 tools; standalone language 4.122.0 was
 recorded in that vector. These retained results are not a rerun on CLI 3.53.1
-or Screenplay 4.139.0.
+or Screenplay 4.141.0.
 
 ## Ground rules
 
@@ -44,7 +44,7 @@ or Screenplay 4.139.0.
 3. **Pick the compiler deliberately and name it.** Standalone `screenplay` for
    current language checks and reference specifications; `cratis` for rendering
    and generation. Bundled and standalone versions differ (CLI 3.53.1 bundles 4.137.0;
-   the standalone pin is 4.139.0). Report both tool and
+   the standalone pin is 4.141.0). Report both tool and
    version, rather than transferring a verdict across releases.
 4. **Know the mode** (design, executable, renderable) and write from its subset.
 5. **Capability is not correctness.** The tool you ran decides what is accepted today; the
@@ -90,8 +90,8 @@ V2 and V3 need MCP (V3 alone can also be read from `cratis screenplay validate -
 server with a fixed root when the tool is older than 4.63.2 (the roots bug hit 4.63.1 and the
 4.60.1 bundled by cratis before 3.28.2; 4.66.0 and later and cratis 3.28.2 are fine). A subagent without MCP reports "V2 not run: no MCP in this agent".
 
-One line per verdict, tool first, for example `V1 pass (screenplay 4.139.0, 3 files)` and
-`V3 blocked: PLAY0268 x3 (filter query, pii)`. Name the source identity (commit plus the digest from
+One line per verdict, tool first, for example `V1 pass (screenplay 4.141.0, 3 files)` and
+`V3 blocked: PLAY0268 x3 (filter query, enum compliance)`. Name the source identity (commit plus the digest from
 the source-identity helper (`cratis-screenplay-modeling-lifecycle` `references/verdicts-and-modes.md` "Source identity")) the verdict ran on; keep it apart from the MCP
 `modelRevision`, which is semantic and, without `.screenplay/identities.json`,
 changes with the root folder name.
@@ -102,7 +102,9 @@ changes with the root folder name.
   `references/cheat-sheet.md`. Read [references/cheat-sheet-example.md](references/cheat-sheet-example.md) when you need one complete design-mode document with every construct family.
 - **Executable** (binds, V3): `references/executable-subset.md`. Optional keyed lookups, unfiltered
   lists and lists narrowed by one `by` key (observable too); `filter`, `scoped to`, `performer` and composite `by` do not bind; no handler (PLAY0268, with or without `implementation`/`hint`); `reads` and
-  `concurrency` do not bind (PLAY0271); no compliance markers (`pii`/`secret`); v6 constructs bind on Screenplay 4.61 or
+  `concurrency` do not bind (PLAY0271); concept compliance binds as v13 on standalone
+  4.141.0, not the pinned CLI (precise refusals: command-surface `references/compliance.md`);
+  v6 constructs bind on Screenplay 4.61 or
   later (standalone, and cratis 3.28.2 or later); generated values and `returns` responses bind (ESM v7)
   from Screenplay 4.68.0 (also in the current CLI bundle) (`references/generated-responses-example.md`). Read [references/executable-example.md](references/executable-example.md) when you need a small StateChange and StateView model that binds executable, [references/pdl-example.md](references/pdl-example.md) when writing projection forms that bind and run, and [references/automation-translate-example.md](references/automation-translate-example.md) when writing Automation and Translate slices (ESM v6).
 - **Renderable** (V5): `references/renderable-subset.md` has the current Stage 4.73.1 table and