@cratis/pi 7.34.1 → 7.36.0

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.142.0: add/rename/remove 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
@@ -39,14 +40,10 @@ directory when it holds `.play` files). Only when it answers that no root was gi
 or that several roots are offered, pass `path`: the folder holding the project's `.play` files, otherwise the
 folder the user names. Without a project, the server works in `Documents/Screenplay`
 in the user's home folder, so do not invent a location. A root fixed at launch
-can switch only to the corresponding model folder in a registered Git worktree
-of the same repository. Pass the worktree checkout or exact model directory as
-`path`; unrelated roots return `RootChangeRefused`. Switching clears proposals
-and uses the destination's own identity state and journal; nothing migrates.
-Submodules and `--separate-git-dir` checkouts require another connection.
-
-Prefer a fixed root; the historical dynamic-roots bug and connection procedure
-are in [MCP loop](references/mcp-loop.md). Send `initialize` and
+can switch only to the same model folder in a registered Git worktree of the
+same repository; rules and refusals are in [MCP loop](references/mcp-loop.md).
+
+Prefer a fixed root (dynamic-roots history: [MCP loop](references/mcp-loop.md)). Send `initialize` and
 `notifications/initialized` before any tool call, then discover `tools/list`
 schemas rather than relying on a remembered count.
 
@@ -82,7 +79,7 @@ can keep that entry point; use the project's supported installation channel.
    of `.play` files is one application, not independent files.
 2. Use `search-declarations`, `declaration-details`, `find-references` and
    `dependencies` to locate the owning declaration and affected references.
-   Before a property rename/removal, read [property links](references/property-links.md):
+   Before a property change, read [property links](references/property-links.md):
    `kind: "Property"`, `Owner.member` / `Owner.generationN.member`, direct mappings.
    `complete: false` is incomplete evidence, never a successful empty list.
 3. Read diagnostics and coverage limitations. Use `dependency-graph` for container
@@ -134,9 +131,10 @@ and applies; others send an edit request ([MCP loop](references/mcp-loop.md)).
 3. Prefer `propose-rename` for supported logical renames: it coordinates fragments,
    repairs proven references and preserves assigned identities. Never substitute
    global string replacement for an explicit refusal.
-4. Use `propose-source` for whole text or `propose-ast` for typed edits
-   (Authoring defaults); `propose` is executable-only. Batch changes;
-   details: `references/mcp-tools.md`.
+4. Prefer `propose-property` for property add/rename/remove, not hand-composed
+   `propose-ast` batches. Inspect the chain and never guess past a refusal:
+   [property links](references/property-links.md). Otherwise use `propose-source`
+   (whole text) or `propose-ast` (typed edits); `propose` is executable-only.
 5. Keep reference policy `Safe`. Use `Draft` only for deliberately requested
    unresolved model debt and report that debt; it does not waive structural,
    identity or binding-protection checks.
@@ -172,15 +170,9 @@ files, 8 MiB total, 2 MiB per file, 1 MiB structured result, 200 items or 192 Ki
 per page. Excluded directories: `.git`, `.ai-work`, `.screenplay`, `bin`, `obj`,
 `node_modules`.
 
-Formatting is explicit. Prefer `PreserveTrivia` for identifier, literal-value and
-whole-mapping edits; it rewrites only the changed span. Structural edits (add,
-remove, move) need `CanonicalizeTouchedDocuments`, which keeps attached comments
-and the authored member order within a document but normalizes whitespace and
-blank lines. Before applying, check the proposal's `droppedCommentCount`; when it
-is not zero, read `read-proposal` with `view: "dropped-comments"` and disclose
-each lost comment (`PLAY0288` also reports their count and lines). Untouched
-documents retain exact bytes. A printer that loses requested structural fields
-rejects the plan.
+Choose formatting explicitly and disclose dropped comments before applying;
+read [formatting and limits](references/mcp-loop.md#formatting-and-limits) for
+`PreserveTrivia`, canonical consent, comment review and byte preservation.
 
 `identityMigrationIssues`: read the [MCP loop](references/mcp-loop.md).
 
@@ -295,7 +287,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 (since 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-loop.md

@@ -13,6 +13,7 @@
 - Identity state (`.screenplay/identities.json`)
 - Read-only views worth knowing
 - Failures (use `failureKind`, never message text)
+- Formatting and limits
 - Provenance
 
 The working loop for the session that owns the model connection: connect, orient,
@@ -106,7 +107,7 @@ the server sends `roots/list` and serves `tools/list` after the reply).
    `find-specification-obligations` (presence, not execution), use
    `find-modeling-smells` as questions needing a domain consequence, and compare
    generated/curated exported snapshots with `semantic-diff`.
-   Before renaming/removing a property, use `find-references`/`dependencies`
+   Before a property change, use `find-references`/`dependencies`
    `kind: "Property"` (4.138.0+) and `Owner.member` or historical event
    `Owner.generationN.member`. Follow direct mapping counterparts one query at a
    time; inspect incomplete/ambiguous evidence and `reasons`. `complete: false`
@@ -117,7 +118,11 @@ the server sends `roots/list` and serves `tools/list` after the reply).
 4. Choose the edit route (next section). For typed edits: `syntax-schema` for the
    node kind, then `read-ast` with `includeContent` for revision-bound handles.
    Never invent a handle.
-5. Propose one coherent change (a slice works best): `propose-source` for whole
+5. Prefer `propose-property` for supported property add/rename/remove chains,
+   not hand-composed `propose-ast` batches; inspect `incomplete`, `needsDecision`
+   and `chainCandidates` before choosing sources, fixtures or event evolution.
+   Exact arguments and decisions: [property links](property-links.md).
+   Otherwise propose one coherent change (a slice works best): `propose-source` for whole
    `.play` text, `propose-ast` for focused typed edits, with
    `validation: "Authoring"`, `referencePolicy: "Safe"` (`Draft` only for
    deliberate, reported gaps), `formatting: "PreserveTrivia"` for value and mapping
@@ -251,6 +256,18 @@ or create a fallback folder to bypass the conflict.
 
 See "Failures (use `failureKind`, never message text)" in SKILL.md.
 
+## Formatting and limits
+
+Formatting is explicit. Prefer `PreserveTrivia` for identifier, literal-value and
+whole-mapping edits; it rewrites only the changed span. Structural edits (add,
+remove, move) need `CanonicalizeTouchedDocuments`, which keeps attached comments
+and the authored member order within a document but normalizes whitespace and
+blank lines. Before applying, check the proposal's `droppedCommentCount`; when it
+is not zero, read `read-proposal` with `view: "dropped-comments"` and disclose
+each lost comment (`PLAY0288` also reports their count and lines). Untouched
+documents retain exact bytes. A printer that loses requested structural fields
+rejects the plan.
+
 ## Provenance
 
 The structure of this loop (ownership, edit-request shape, failure handling) is

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,15 @@ 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. Prefer `propose-property` over hand-composed AST
+batches for property chains: rename/remove shipped in 4.140.0, add in 4.142.0.
+Add takes `owner`, `expectedOwnerName`, `name`, `type`, `optional`,
+`hops` (`{at, name}` or `{at, value}`) and `fixtureValue`, plus both revision guards.
+Missing sources/required fixture values refuse `SourcesRequired`/`FixtureValueRequired`;
+off-chain hops refuse `HopNotOnChain`, nested feeds `UnsupportedPropertySpan`.
+Read `property.needsDecision` and `property.chainCandidates`, select an event
+evolution mode even for optional additions, and review before applying.
+Exact arguments, AutoMap and fixture rules: [property evidence and planning](property-links.md). A
 source-only authoring proposal may be accepted while `executableReady` is false.
 That is not permission to claim the application runs.
 
@@ -272,7 +280,7 @@ limits. Continue with `expectedSourceRevision`.
 
 From 4.138.0, `find-references` and `dependencies` accept `kind: "Property"`
 and `Owner.member`, or historical event `Owner.generationN.member`. Before a
-rename/removal, read [property links](property-links.md) for exact query/result
+property change, read [property links](property-links.md) for exact query/result
 shapes, roles, direct counterpart traversal, revision paging and `complete: false`
 with `reasons`. Incomplete evidence is never a successful empty list. These tools
 inspect authored links, not code execution or a transitive runtime graph.

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

@@ -7,11 +7,14 @@
 
 - Address and query
 - Read evidence, not just a count
+- Propose a property change (4.142.0)
+- Add with explicit sources and fixtures
 
 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` rename/remove planner;
+4.142.0 adds `add`. The CLI bundle has neither capability.
 
 ## Address and query
 
@@ -114,7 +117,7 @@ same-named properties in unrelated declarations do not affect completeness.
 External code contents and registrations remain outside coverage even with
 `complete: true`; authored links do not prove executable admission.
 
-Before a rename/removal: pin the revision, inspect incoming readers and outgoing
+Before a property change: pin the revision, inspect incoming readers and outgoing
 counterparts, page to completion, resolve uncertainties, then choose the supported
 identity-safe edit route with the connection owner. Never infer safe deletion from
 zero resolved hits or edit every same-named field. An event-property change still
@@ -122,5 +125,88 @@ 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.142.0)
+
+Use `propose-property`, not hand-composed `propose-ast` batches, for supported
+add/rename/remove changes along a proven chain. For add, inspect existing
+producer/consumer properties and mapping blocks first; the new property has no
+reference address yet.
+
+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 (`HopNotOnChain`). 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`.
+
+Read `property.needsDecision` for refusal reasons and located candidates;
+`property.chainCandidates` lists unselected chain members, not automatic edits.
+A refusal returns `success: false` and no writable partial candidate. Missing an
+event mode returns `EventContractChangeRequiresDecision`; do not bypass it by
+text editing or claiming the catalog proves non-persistence.
+
+For any selected event property (including optional additions), 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.
+
+## Add with explicit sources and fixtures
+
+Read the declaration's original `read-ast` handle. Send `action: "add"`, both
+revision guards, `owner`, `expectedOwnerName`, `name` (new unqualified member),
+`type` (authored type text, not a concept declaration), and optional `optional`
+(default false). Use the flag, not an optional suffix in `type`.
+
+`hops` defaults to `[]`: each entry has an original `at` handle and exactly one
+of `name` or `value`. `{at, name}` adds the same type at a connected declaration;
+`{at, value}` supplies a value expression at a `produces`, `from` or capture
+`append` block. Every selected event producer/read-model consumer needs an
+explicit mapping decision or compatible same-named AutoMap source. Never infer
+a business expression. Existing property names and off-chain hops refuse.
+Add does not accept `target`, `expectedName`, `newName`, `alsoRename` or `alsoRemove`;
+add-only fields are invalid for rename/remove.
+
+For a required addition with existing fixtures/assertions, supply `fixtureValue`
+as **literal source text**, for example `"\"normal\""` for a String value. The
+planner adds it to existing specification steps, examples and query results;
+`optional: true` adds no fixture values. A literal is not proof of behavior:
+inspect the assertions and run `run-specifications` on the retained proposal.
+
+| Refusal | Response |
+| --- | --- |
+| `SourcesRequired` | Select missing producer/consumer mappings from the located candidates; do not guess sources |
+| `FixtureValueRequired` | Supply the intended required literal fixture value; do not weaken assertions |
+| `HopNotOnChain` | Remove or correct the off-chain selection; never edit same-named unrelated fields |
+| `UnsupportedPropertySpan` | Preserve source and report unsupported nested feeds/expressions or shared spans; do not flatten the model to bypass refusal |
+
+Use `CanonicalizeTouchedDocuments` for additions. Review `property.changed`
+(`added`, `fixtureAdded`), decisions, chain candidates and generations, exact
+bytes, dropped comments, identities and semantic diff before ordinary `apply`.
+Even an optional event addition needs the same explicit evolution mode above.
+
+Authority: Screenplay `v4.142.0:Source/DotNET/Screenplay.Mcp/McpWorkspaces.Property.cs`,
+`Screenplay/Workspaces/WorkspaceProperty{Request,Plan,Safety,Report}.cs`,
+`WorkspacePropertyAdd{Plan,Edits}.cs`, `WorkspacePropertyAssertionProvenance.cs`,
+`WorkspaceEventGenerations.cs`, and `Documentation/screenplay/mcp/{edit,reference,authoring-tools}.md`;
+the published contract's `mcpTools` entry for `propose-property`; decisions 0067 and 0044.

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

@@ -4,9 +4,25 @@
   "fixtures": [],
   "assertions": [
     { "kind": "play-compiles" },
+    { "kind": "skill-contains", "value": "propose-property" },
+    { "kind": "skill-contains", "value": "not hand-composed `propose-ast` batches", "file": "references/property-links.md" },
+    { "kind": "skill-contains", "value": "`incomplete`, `needsDecision`", "file": "references/mcp-loop.md" },
+    { "kind": "skill-contains", "value": "`property.chainCandidates`", "file": "references/property-links.md" },
+    { "kind": "skill-contains", "value": "EventContractChangeRequiresDecision", "file": "references/property-links.md" },
+    { "kind": "skill-contains", "value": "action: \"add\"", "file": "references/property-links.md" },
+    { "kind": "skill-contains", "value": "`expectedOwnerName`", "file": "references/property-links.md" },
+    { "kind": "skill-contains", "value": "{at, name}", "file": "references/property-links.md" },
+    { "kind": "skill-contains", "value": "{at, value}", "file": "references/property-links.md" },
+    { "kind": "skill-contains", "value": "`fixtureValue`", "file": "references/property-links.md" },
+    { "kind": "skill-contains", "value": "SourcesRequired", "file": "references/property-links.md" },
+    { "kind": "skill-contains", "value": "FixtureValueRequired", "file": "references/property-links.md" },
+    { "kind": "skill-contains", "value": "HopNotOnChain", "file": "references/property-links.md" },
+    { "kind": "skill-contains", "value": "UnsupportedPropertySpan", "file": "references/property-links.md" },
+    { "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.142.0"
     },
     {
       "kind": "skill-contains",
@@ -90,7 +106,8 @@
     },
     {
       "kind": "skill-contains",
-      "value": "`view: \"dropped-comments\"`"
+      "value": "`view: \"dropped-comments\"`",
+      "file": "references/mcp-loop.md"
     },
     {
       "kind": "skill-contains",

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

@@ -96,7 +96,9 @@ A reaction that both produces events and invokes commands keeps its single model
 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
+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-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-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

@@ -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.142.0 (since 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/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.142.0 (since 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.142.0 binds this pii concept as v13 (since 4.141.0), 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.142.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.142.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.142.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.142.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.142.0 (since 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

package/package/corpus/skills/cratis-screenplay-toolchain/references/cheat-sheet-example.md

@@ -2,7 +2,13 @@
 
 One complete document with every construct family. Design mode, not executable. Prose rules: [cheat-sheet.md](cheat-sheet.md); tool versions: [versions.md](versions.md); what binds: [executable-subset.md](executable-subset.md).
 
-Binding blockers: unquoted import, `pii`, `reads` (PLAY0271), `starts with`, a `filter` query (lists and observable lists bind). Executable shapes are in the sibling examples. The bare-marker fence compiles warning-free on standalone 4.127.0; the earlier legacy-marker version compiled on 4.66.0 and CLI 3.28.2. `RecordingAPayment` lists the `InvoiceClosed` cascade, which the cratis 3.27.1 bundle (4.60.1) rejected with a false PLAY0285 ("outcome cannot be produced by 'RecordPayment'"); 3.28.2 accepts it.
+Binding blockers: unquoted import, `reads` (PLAY0271), `starts with`, a `filter` query (lists and observable lists bind). Executable shapes are in the sibling examples. The bare-marker fence compiles warning-free on standalone 4.127.0; the earlier legacy-marker version compiled on 4.66.0 and CLI 3.28.2. `RecordingAPayment` lists the `InvoiceClosed` cascade, which the cratis 3.27.1 bundle (4.60.1) rejected with a false PLAY0285 ("outcome cannot be produced by 'RecordPayment'"); 3.28.2 accepts it.
+
+Concept compliance itself binds as ESM v13 on standalone 4.142.0 (first released
+in 4.141.0); reasons remain report-only PLAY0270. CLI 3.53.1 bundles Screenplay
+4.137.0, which refuses markers; standalone Stage 4.76.0 admits only through v12
+(Stage#345). Binder-only PLAY0268
+refusals and subject-lineage limits: command-surface `references/compliance.md`.
 
 ```screenplay test=unbound
 // Design-mode cheat-sheet: every construct family; compiles warning-free on the standalone tool.
@@ -12,7 +18,7 @@ import Customers.CustomerRegistered        // unquoted = another bounded context
 
 concept InvoiceId : Uuid                   // primitives: Uuid String Int Decimal Bool Date DateTime Enum
 concept PaymentId : Uuid
-concept Email : String pii                 // pii / secret (blocks executability)
+concept Email : String pii                 // v13 since 4.141.0; current standalone 4.142.0 binds; pinned CLI refuses
   pii reason "Identifies a person"
   validate
     not empty  message "An email is required"

package/package/corpus/skills/cratis-screenplay-toolchain/references/diagnostics.md

@@ -172,8 +172,10 @@ escapes `%`/`|`, not an inferred split of legacy text.
 
 Identity declarations and event `subject` are metadata; reading a declared
 `$identity` detail in executable clauses is PLAY0268. `runs as` is admitted as
-ESM v10 in the current standalone, not a current PLAY0268 gap. Compliance markers
-still block binding; purpose metadata is PLAY0270. See command-surface
+ESM v10 in the current standalone, not a current PLAY0268 gap. At standalone
+4.142.0, concept compliance binds as v13 (since 4.141.0); enum/identity compliance and protected
+events with explicit subject marks still refuse PLAY0268. CLI 3.53.1's 4.137.0
+bundle retains the blanket marker refusal; purpose metadata is PLAY0270. See command-surface
 `references/compliance.md` and `references/context.md` for syntax and limits.
 
 `screenplay_repair_capabilities` and `propose-repair` advertise PLAY0653: a

package/package/corpus/skills/cratis-screenplay-toolchain/references/doc-contradictions.md

@@ -14,6 +14,12 @@ the released grammar/tool and successful purpose probes take precedence. The sam
 page's legacy `@pii` mentions do not change bare `pii`/`secret` canonical syntax;
 legacy forms compile with PLAY0565 information, duplicates with PLAY0653 warning.
 Event `subject` remains report-only, despite accepted future lineage work.
+Rechecked at 4.142.0: concept `pii`/`personal` and `secret` bind as v13, while
+reasons stay PLAY0270 report-only. PLAY0268 at binding only rejects enum/identity
+compliance and events mixing personal or explicitly subject-scoped secret values
+with an explicit `subject` mark. CLI 3.53.1 bundles Screenplay 4.137.0, which
+refuses markers; standalone Stage 4.76.0 admits only through v12 (Stage#345). These are distinct boundaries,
+not a reason to remove protection.
 
 `D/` is Screenplay `Documentation/screenplay/` at **v4.66.0**; line numbers were re-read at
 that tag. Rule: the compiler you ran decides what the tool accepts today; the documentation
@@ -42,7 +48,7 @@ read from source or documentation.
 | 14 | `$causedBy` | not evaluable (#4119), not ESM | showcase only |
 | 15 | literal keys | `key literal "global"` vs `key "global"` | both compile; prefer `literal` |
 | 16 | query admission | `D/queries.md:74` now says live, filtered, scoped and performer queries are not admitted | the binder also rejects collection queries and a missing `by`, which stay undocumented [probed] |
-| 17 | `@pii` | `D/concepts.md:3,33` "Chronicle applies `@pii` and `@sensitive` rules automatically" | the binder rejects any compliance attribute (PLAY0268); keep it, report V3 blocked. `@sensitive` means an operational secret (`[Encrypted]` + `[NotAudited]`; Screenplay decision 0034); the historically probed tools (standalone 4.68.0, bundle 4.66.0) do **not** report `PLAY0515` (`@pii` from 4.69.1, `@sensitive` from 4.84.1): there only Chronicle catches either attribute on an event-source identifier, at build time of the generated code (CHR0034 for `@pii`, CHR0052 for `@sensitive`) |
+| 17 | `@pii` | `D/concepts.md:3,33` "Chronicle applies `@pii` and `@sensitive` rules automatically" | the historical binder rejected any compliance attribute (PLAY0268); standalone 4.142.0 admits concept compliance as v13 (since 4.141.0) with narrower enum/identity/subject-lineage refusals (command-surface `references/compliance.md`). Keep protection; the pinned CLI still reports V3 blocked. `@sensitive` means an operational secret (`[Encrypted]` + `[NotAudited]`; Screenplay decision 0034); the historically probed tools (standalone 4.68.0, bundle 4.66.0) do **not** report `PLAY0515` (`@pii` from 4.69.1, `@sensitive` from 4.84.1): there only Chronicle catches either attribute on an event-source identifier, at build time of the generated code (CHR0034 for `@pii`, CHR0052 for `@sensitive`) |
 | 18 | read-model identity | `D/readmodels.md:32` "from the keyed query" | at 4.135.0 explicit `key` wins; else single-instance queries agree on one read-model `by` property; only with none and an admitted list query does conventional `*Id` inference run (collection-key exclusions: read-surface `references/named-keys.md`). Queryless views need explicit `key` |
 | 19 | `$strings` constraint messages | `D/constraints.md:31` vs `D/internationalization.md:55` | the compiler keeps the key; realization localizes |
 | 20 | composite key braces | optional in the EBNF; both forms in docs | both fine |