@cratis/pi 7.34.1 → 7.35.0

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-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.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.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

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

@@ -2,7 +2,7 @@
 
 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.
 
 ```screenplay test=unbound
 // Design-mode cheat-sheet: every construct family; compiles warning-free on the standalone tool.
@@ -12,7 +12,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 on standalone 4.141.0; refuses on pinned CLI
   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.141.0, concept compliance binds as v13; 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

@@ -42,7 +42,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.141.0 instead admits concept compliance as v13 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 |

package/package/corpus/skills/cratis-screenplay-toolchain/references/executable-subset.md

@@ -2,7 +2,7 @@
 
 ## Contents
 
-- Caller and compliance boundary (4.127.0)
+- Caller and compliance boundary (4.141.0)
 - Admitted on both compilers
 - Admitted from Screenplay 4.61 (ESM v6): standalone tool and cratis 3.28.2 or later
 - Generated values and responses (ESM v7): standalone 4.68.0 or later; the cratis 3.53.1 bundle binds them too
@@ -16,12 +16,12 @@ Current pins: `versions.md`. Detailed
 4.66.0/4.68.0 binder probes below retain their historical labels. Current source
 admits routes as ESM v8, public/direction constructs as v9, identity/overrides/filters
 as v10, qualifying non-route Double literals as v11 (exact lowering of Double-mode literals)
-and non-positional enum numbers as v12. Operations, the `numbers exact` **source mode** (PLAY0268) and
+and non-positional enum numbers as v12; concept compliance as v13. Operations, the `numbers exact` **source mode** (PLAY0268) and
 reaction refusals/redelivery remain unadmitted. Use the actual
 binder before promoting an older probe to a current capability claim.
 
 What the binder admits, and what it refuses with which code. The answer depends on the
-compiler version: the standalone tool (4.139.0) binds through v12; the compiler bundled in cratis
+compiler version: the standalone tool (4.141.0) binds through v13; the compiler bundled in cratis
 3.53.1 (4.137.0) binds ESM through v10 for rendering and refuses non-positional enum numbers at
 binding; older bundles (4.66.0 in cratis 3.28.x, admitting v1 to v6; 4.60.1 before 3.28.2, v1 to v5)
 are history.
@@ -40,7 +40,7 @@ Complete examples that bind live in `executable-example.md` (both compilers),
 (ESM v6; standalone tool and cratis 3.28.2 or later) and `generated-responses-example.md`
 (ESM v7; standalone tool 4.68.0 or later, and the cratis 3.53.1 bundle).
 
-## Caller and compliance boundary (4.127.0)
+## Caller and compliance boundary (4.141.0)
 
 `$identity.id`/`.name`/`.userName` are aliases of the admitted
 `$context.identity` produces-mapping values. Authentication status, roles and
@@ -49,10 +49,14 @@ A top-level `identity` block alone is authoring metadata and does not block
 readiness. Executable reads of declared `$identity.<detail>` do (PLAY0268);
 `$context.identity` remains built-ins only. Purposes and event `subject` marks
 are metadata (PLAY0270), not source resolution, retention or subject propagation.
-Bare `pii`/`personal` and `secret` concepts, scopes and qualifiers still block
-binding. Legacy spellings compile with PLAY0565 information; duplicates warn
-PLAY0653. Never remove protection; see command-surface `references/compliance.md`.
-Authority: v4.127.0 `context.md`, `identity.md`, `concepts.md`, `events.md`, `purposes.md`.
+Bare `pii`/`personal` and `secret` concepts, scopes and qualifiers bind as v13
+on standalone 4.141.0; CLI 3.53.1's 4.137.0 bundle still refuses them. Enum/identity
+compliance and events mixing protected values with explicit subject marks remain
+refused; see command-surface `references/compliance.md` for the precise boundary.
+Legacy spellings compile with PLAY0565 information; duplicates warn PLAY0653.
+Never remove protection. Reference execution proves neither encryption nor erasure.
+Authority: v4.141.0 `SemanticModelBinder.Compliance.cs`, `concepts.md`, `events.md`;
+caller and purpose guidance retains v4.127.0 `context.md`, `identity.md`, `purposes.md`.
 
 ## Admitted on both compilers
 
@@ -209,7 +213,7 @@ bodies still leave their owner non-executable.
 | --- | --- | --- |
 | `Automation` or `Translate` slice, `reaction`, `capture`, `trigger`; `given clock`, `when clock`, `when trigger`, `when capture` | PLAY0268 | **cratis before 3.28.2 bundles only** (4.60.1); messages in `versions.md` |
 | Unquoted `import Other.Contract` | PLAY0268 | external contract import is not bound |
-| `pii` or `secret` on any concept (also alias/legacy markers) | PLAY0268 | Compliance requires portable data-subject semantics; scopes/qualifiers do not admit it. Secret provider mapping is `[Encrypted]` + `[NotAudited]`, not a bind/render claim |
+| `pii` or `secret` on a concept | PLAY0268 | Blanket refusal on CLI 3.53.1's 4.137.0 bundle only. Standalone 4.141.0 admits v13 except enum/identity compliance and events mixing personal or explicitly subject-scoped secret values with explicit subject marks; see `compliance.md` in command-surface references |
 | `query` with a composite `by` block, or `by ... from` context-derived arguments | PLAY0268 | composite `by` blocks remain unadmitted (#599). An optional scalar snapshot lookup, an unfiltered list (`RM[]`) and a list narrowed by one caller-supplied `by` key bind, in their `observable` form too (since 4.105.0) |
 | `filter`, `scoped to`, `performer` queries | PLAY0268 | "uses delivery, filtering, scope, or implementation behavior outside the first ESM v1 vertical." `observable` is not the blocker: it goes in the return position (`=> observable RM[]`); as a body line it is PLAY0048 |
 | `contains` or `starts with` in conditions | PLAY0268 | equality and numeric ordering only |
@@ -251,8 +255,9 @@ bodies still leave their owner non-executable.
 
 Do not remove `pii`, `secret`, `authorize` or policies, list queries, automations or
 rules a domain needs just to make binding pass. Report `V3 blocked: <codes>` and record the
-slice in the gap list. A `pii` or `secret` marker blocks V3 and rendering, and
-either attribute on an identifier or typed destination is a source error
+slice in the gap list. A `pii` or `secret` marker selects v13 on standalone
+4.141.0, but blocks binding on the pinned CLI and exceeds Stage 4.76.0's v12
+ceiling. Either attribute on an identifier or typed destination is a source error
 PLAY0515 on the current compiler (including stream-id parts and route mapping
 sources). Chronicle also rejects `[PII]`/`[Encrypted]` on event-source identifiers
 (CHR0034/CHR0052). Keep surrogate identity and protected payload separate.

package/package/corpus/skills/cratis-screenplay-toolchain/references/renderable-subset.md

@@ -50,7 +50,7 @@ version; each construct it does not render refuses with its own code before any
 | Authorization | role-only, authenticated, opaque pure policies, claim conditions with Uuid, Date, DateTime or text targets (numeric and Boolean claim matches render as always false; Stage 4.73.1 `IsSupportedClaimPath`), `not`/and/or; roles read through the identity's `RoleClaimType` | role-claim URIs, nested opaque policies, unresolved or non-portable policies, no single identifier, opaque-policy subjects that are not text, Uuid, Date or DateTime (`STAGE-ESM-015`; Stage 4.73.1 `IsTextualSubject`, a restriction separate from declarative claim targets) |
 | Event sources, streams, routes (ESM v8) | rendered, with routed specifications | reserved stored names, unformattable routed fixtures, unsupported routed replay (`STAGE-ESM-030`) |
 | Numbers, case tables | whole numbers as `long` from ESM v8; case tables | out-of-`int` literals below v8 (`STAGE-ESM-031`) |
-| Generated values and responses (v7) | not rendered | `STAGE-ESM-028`/`-029` (Stage#175) |
+| Generated values and responses (v7) | not rendered by Stage 4.73.1 (cli 3.53.1); rendered from standalone Stage 4.74.0 (UUID concepts, scalar and named responses) | `STAGE-ESM-028`/`-029` at 4.73.1 (Stage#175); `STAGE-ESM-038` for combinations the target cannot preserve |
 | Specifications | as in Stage's `admission.md` | `then no readmodel` (`-027`); an unauthenticated caller carrying roles or claims, `$context.occurred`-derived fixed values asserted (`-011`) |
 | v9 and v10 | reducer observer `from` filters | public events and event-target projections (`-032`); foreign origins and event-source captures (`-033`); directed Translate (`-024`); reaction `runsAs` (`-034`); reaction `from` filters (`-035`); per-production route overrides (`-036`) |
 | Evolved events | initial revisions only | `STAGE-ESM-026` (Stage#204) |
@@ -88,7 +88,10 @@ whole automation is hand-written (gap-fill).
 | Compliance | none | any `@pii` or `@sensitive` already fails binding (PLAY0268). The C# provider mapping (Stage v4.29.0, Stage#197) is `@pii` to `[PII]`, `@sensitive` to `[Encrypted]` + `[NotAudited]`, both to `[PII]` only |
 
 At standalone 4.127.0, compliance uses bare `pii`/`secret` (legacy markers are
-accepted with PLAY0565 information); either still refuses binding. Identity blocks,
+accepted with PLAY0565 information); either still refuses binding on that compiler.
+Standalone 4.141.0 admits concept compliance as v13 with narrower refusals
+(command-surface `references/compliance.md`), but Stage 4.76.0 admits only through
+v12 and the pinned CLI still bundles 4.137.0. Identity blocks,
 purposes and event `subject` are authoring metadata, not provider realization;
 executing identity detail reads still refuses PLAY0268. Current source/stream
 routes are admitted as v8, including composite ids, not the historical binding