@cratis/pi 7.32.0 → 7.34.0

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

@@ -5,35 +5,40 @@
 - Caller and compliance boundary (4.127.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 only
+- Generated values and responses (ESM v7): standalone 4.68.0 or later; the cratis 3.53.1 bundle binds them too
 - Released public boundaries and observer routes
 - Code attachments (what binds, what never does)
 - Refused (code, reason): fix, or record as a mode gap
 - Not refused, but do not rely on it
 - Never do this to reach V3
 
-Current pins are Screenplay 4.135.0 / CLI 3.50.0 (`versions.md`). Detailed
+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 and qualifying non-route Double literals as v11. Operations,
-`numbers exact` source mode and reaction refusals/redelivery remain unadmitted. Use the actual
+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
+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: standalone Screenplay 4.68.0 admits ESM v1 to v7; the 4.66.0 compiler bundled in
-cratis 3.28.2 and 3.28.3 admits v1 to v6; the 4.60.1 compiler bundled in cratis before 3.28.2 admits v1 to v5.
+compiler version: the standalone tool (4.139.0) binds through v12; 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.
 Tool facts and the exact v6 messages: `versions.md`. Always name
 the tool with a V2 or V3 result. When tool and documentation disagree, the tool decides
 current capability; the documentation and the domain decide intended correctness. Record
 the gap, never strip the model to pass.
 
-Binding is observed only through MCP (`read-workspace view=executable-diagnostics`) or a
-render. `screenplay <folder>` and `cratis screenplay validate` never bind (`verdicts.md`).
+Binding is observed through MCP (`read-workspace view=executable-diagnostics`), a render, or
+`cratis screenplay validate --executable <root>` (bundled compiler; binding errors only, writes
+nothing; exit 5 when it does not bind). `screenplay <folder>` and plain `cratis screenplay validate`
+never bind (`verdicts.md`).
 
 Complete examples that bind live in `executable-example.md` (both compilers),
 `pdl-example.md` (projections, both compilers) and `automation-translate-example.md`
 (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 only).
+(ESM v7; standalone tool 4.68.0 or later, and the cratis 3.53.1 bundle).
 
 ## Caller and compliance boundary (4.127.0)
 
@@ -94,7 +99,7 @@ Authority: v4.127.0 `context.md`, `identity.md`, `concepts.md`, `events.md`, `pu
   ...` with an explicit `for`. Without a declared actor, a gated invocation denies.
   On 4.125.0 reaction `runs as system role "<Role>"` supplies the actor and
   selects ESM v10; keep the gate. CLI 3.41.0's older compiler rejected this syntax;
-  CLI 3.50.0's bundle supports it, but Stage refuses reaction identity with STAGE-ESM-034.
+  The pinned CLI bundle (`versions.md`) supports it, but Stage refuses reaction identity with STAGE-ESM-034.
   Standalone reference execution admits it.
 - Application `trigger` declarations and `when trigger` specifications.
 - `slice Translate` with `capture` (`key`, `map ... translate`, `append ... when x from "a"
@@ -106,13 +111,15 @@ Authority: v4.127.0 `context.md`, `identity.md`, `concepts.md`, `events.md`, `pu
 - Command specifications that list reaction cascades (no false PLAY0285).
 - In a `then` list after `when append`, only what followed the appended event.
 
-## Generated values and responses (ESM v7): standalone 4.68.0 or later only
+## Generated values and responses (ESM v7): standalone 4.68.0 or later; the cratis 3.53.1 bundle binds them too
 
 Facts read at `v4.68.0`: decision 0026 and `Documentation/screenplay/{commands,specifications,interoperability}.md`.
 A model selects ESM v7 only when it uses a generated property, a response, a generated fixture or a `then returns`
 expectation; every other model keeps its version, bytes and revision. The cratis CLI 3.28.3 (bundled 4.66.0)
-reports `PLAY0268` for these constructs, and Stage 4.24.2 refuses ESM v7 with `STAGE-ESM-016` (tracked in
-Stage#201), so they bind and run but are not rendered: gap-fill with the model as contract. Complete example:
+reported `PLAY0268` for these constructs (history). The current CLI (3.53.1, bundled 4.137.0) binds them
+and reaches Stage planning, where Stage 4.73.1 refuses generated values with `STAGE-ESM-028` and
+responses with `STAGE-ESM-029` (Stage#175), so they bind and run but are not rendered: gap-fill with the
+model as contract. Complete example:
 `generated-responses-example.md`.
 
 - A generated property is command-only, required, scalar and a concept backed by `Uuid`; bare `Uuid`, optional and collection
@@ -153,6 +160,12 @@ filters match routed source/stream names only. Read
 Qualifying retained non-route Double literals bind/reference-execute as v11 on
 4.135.0, unlike `numbers exact`; see `versions.md`.
 
+Non-positional enum member numbers bind as ESM v12 from 4.139.0; positional
+pins preserve the earlier executable version/bytes. The optional canonical last
+`numbers` array parallels `values`; specifications still use member names.
+Consumers must admit v12 explicitly; CLI 3.53.1/Stage 4.73.1 do not. Syntax:
+command-surface `references/enum-numbers.md`; version contract: `versions.md`.
+
 ## Code attachments (what binds, what never does)
 
 Inline fences (`csharp`, `typescript`, `react`, `html`, `sql`) and `file <path>` attach
@@ -181,8 +194,9 @@ bodies still leave their owner non-executable.
   `require`/`validate` bodies (`v4.66.0:Documentation/screenplay/commands.md`, `context.md`).
 - A handler therefore makes the slice non-executable and non-renderable: it is gap-fill
   with the model as the contract.
-- Stage 4.24 admits only pure reducer bodies (Roslyn allowlist, STAGE-ESM-019 and 022);
-  code validation (STAGE-ESM-005) and opaque policies (STAGE-ESM-015) are refused.
+- Stage admits only pure reducer bodies (Roslyn allowlist, STAGE-ESM-019 and 022);
+  code validation is refused (STAGE-ESM-005). Opaque pure policies render at Stage 4.73.1 (4.24
+  refused them with STAGE-ESM-015).
 - The reference runner returns Unsupported for the opaque bodies that do bind (rule and
   policy predicates, code validation, reducer transitions); a specification that needs one
   never passes. Handlers, file constraints and query performers (and reaction effects on a trigger with
@@ -196,8 +210,8 @@ 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 |
-| `query` returning a collection (`RM[]`), or without exactly one caller-supplied scalar `by` | PLAY0268 | Current 4.135.0 boundary: composite `by` blocks remain unadmitted (#599); optional scalar snapshot lookup binds |
-| `observable`, `filter`, `scoped to`, `performer` queries | PLAY0268 | "uses delivery, filtering, scope, or implementation behavior outside the first ESM v1 vertical." `observable` goes in the return position (`=> observable RM optional`); as a body line it is PLAY0048 |
+| `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 |
 | Date or DateTime comparison, `today` | PLAY0268 | no runtime date value |
 | Rule on a nested path (`lines.qty all > 0`) | PLAY0268 | put the rule on the nested value's concept |
@@ -216,7 +230,7 @@ bodies still leave their owner non-executable.
 | `$eventContext.occurred.Week` | PLAY0273 | derived value |
 | Projection `parent p` where `p` is not on the child event | PLAY0273 | "Event property not found" |
 | `generated` or `returns` on a compiler before 4.68.0 (4.66.0 and 4.67.0 refuse; 4.66.0 is bundled in cratis 3.28.x) | PLAY0268 | admitted from standalone 4.68.0 (ESM v7), see above |
-| Operations or systems, `numbers exact`, reaction refusals/redelivery | PLAY0268 | not admitted by any supported ESM version; one such construct leaves the **whole** application without an executable model. Event sources/streams/routes instead bind as ESM v8 on the current compiler (`sources-and-streams.md`) |
+| Operations or systems, `numbers exact` source mode, reaction refusals/redelivery | PLAY0268 | not admitted by any supported ESM version; one such construct leaves the **whole** application without an executable model. Event sources/streams/routes instead bind as ESM v8 on the current compiler (`sources-and-streams.md`) |
 | Spec of a gated command or query without `given caller` | PLAY0389 | module and feature gates count |
 | `given` or `then readmodel` missing key parts | PLAY0351 | explicit `key` marks replace inference; composite fixtures need every part but remain unadmitted (#599) |
 | When-less spec asserting events or errors | PLAY0352 | |

package/package/corpus/skills/cratis-screenplay-toolchain/references/production-routes-and-filters.md

@@ -108,7 +108,7 @@ contract. A consumer admitting v10 must include all three, not just identity.
 Composite **read-model** keys are separate and remain unadmitted (PLAY0268, #599).
 
 Previous CLI 3.46.1/Stage 4.52.0 refused versions above v7 before planning.
-CLI 3.50.0/Stage 4.67.0 admits through v10 to construct checks: production overrides
+The pinned CLI/Stage pair (`versions.md`) admits through v10 to construct checks: production overrides
 still refuse STAGE-ESM-036 and reaction filters STAGE-ESM-035; reducer filters render.
 A supported version number alone never proves target support or a passing render.
 

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

@@ -14,11 +14,10 @@ the file that holds it.
 | --- | --- | --- |
 | TrogonStack/agentskills `7b249d3ee42d8b7e11fa564141ebd5fbc37aadf1` (MIT, Copyright (c) 2025 Straw Hat, LLC) | none: no passage of this skill is adapted from it | no third-party notice needed in `LICENSE` |
 
-## Adapted closely (Martin Dilger and Nebulit GmbH, with agreement)
+## Adapted closely (Martin Dilger and Nebulit GmbH)
 
 Source: https://github.com/Nebulit-GmbH/agentic-engineer at commit `07b0f30648d663cb588d7e2c7aa031af9dfc21f2`,
-by Martin Dilger and Nebulit GmbH (https://nebulit.de). The repository carries no licence file; this material
-is adapted with the agreement of Martin Dilger and Nebulit GmbH.
+by Martin Dilger and Nebulit GmbH (https://nebulit.de), used with the explicit consent of Martin Dilger and Nebulit GmbH.
 
 | Source file | Used in | How |
 |---|---|---|
@@ -28,7 +27,7 @@ is adapted with the agreement of Martin Dilger and Nebulit GmbH.
 
 ## Sources read for facts
 
-- Current public/keys/routes/version update: Screenplay `v4.135.0` (`b4e46130`),
+- Historical public/keys/routes/version source check: Screenplay `v4.135.0` (`b4e46130`),
   unchanged release contract, `Semantics/Versions.cs`, `Documentation/screenplay/{events,slices,captures,readmodels,queries,event-sources,diagnostics,interoperability}.md`,
   decisions 0049–0051 and 0060–0066. Composite view keys remain PLAY0268 (#599);
   v11 literal lowering is admitted despite interoperability's unreleased label.

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

@@ -2,13 +2,13 @@
 
 ## Contents
 
-- What Stage 4.24 admits
+- Current admission (Stage 4.73.1)
+- Historical: what Stage 4.24 admitted
 - Authoring consequences in renderable mode
 - Ownership, publication and recovery
 - Reading V5
 
-Current pins: standalone Screenplay 4.135.0; CLI 3.50.0 bundles Screenplay
-4.131.0 and Stage 4.67.0 (`versions.md`). CLI/Stage admit through v10 to construct
+Current compiler/CLI/Stage pins: `versions.md`. CLI/Stage admit through v10 to construct
 checks, not blanket rendering; above v10 is CLI-RENDER-004 (direct Stage:
 STAGE-ESM-016). v9 publication/foreign facts and v10 reaction identity,
 reaction filters and production overrides still refuse STAGE-ESM-032–036;
@@ -19,7 +19,9 @@ admitted only through v7 and applied neither newer rule. The historical v7 canon
 STAGE-ESM-028/029 for generated values/responses
 (`v3.41.0:Source/Cli.Specs/for_ScreenplayPlanning/when_planning_an_esm_v7_model.cs`).
 The following detailed Stage 4.24.x results are **historical**, not reverified
-4.67.0 claims. Run the bundled renderer before asserting current renderability.
+4.73.1 claims. Non-positional enum numbers select v12 on standalone 4.139.0,
+but the CLI's 4.137.0 compiler does not bind them and Stage does not admit v12.
+Keep the pins and report the consumer gap. Run the bundled renderer before asserting current renderability.
 
 Historical sources, all read at tags: Stage v4.24.1 `Source/Rendering.Cratis/Semantics/SemanticSurfaceLedger.cs`
 (an exhaustive map of every ESM member to Rendered, Rejected(code) or Ignored),
@@ -29,12 +31,35 @@ render itself before claiming renderability: this table is a reading of the sour
 render result.
 
 Renderable is a strict subset of executable (`executable-subset.md`). Order of events in
-`cratis render`: the CLI binds the model with its **bundled Screenplay** (4.66.0 in cratis 3.28.2, so PLAY0268
-and friends appear first), then Stage admits or
-rejects members. An ESM v6 model binds but Stage refuses it whole with `STAGE-ESM-016`
-(probed on 3.28.2; an ESM v7 model with generated values or responses fails binding first on the bundled 4.66.0 with `PLAY0268`, and Stage 4.24.2 would refuse it with `STAGE-ESM-016` too, tracked in Stage#201; on before 3.28.2 it failed binding first, with PLAY0268).
+`cratis render`: the CLI binds the **whole** model with its **bundled Screenplay** (4.137.0 in cratis
+3.53.1, so PLAY0268 and friends appear first, even with `--scope`), then Stage admits or rejects
+members of the selected scope. (Historical, cratis 3.28.2: an ESM v6 model bound but Stage refused it
+whole with `STAGE-ESM-016`.)
 
-## What Stage 4.24 admits
+## Current admission (Stage 4.73.1)
+
+Read at Stage `v4.73.1` (`Documentation/guides/build-renderer-target.md`, `SemanticVersionFeatures.cs`,
+`SemanticCratisAdmission*.cs`) and cli `v3.53.1`; source reading, not a render run (the worked
+example in `cratis-screenplay-render-and-gap-fill` was probed). Stage admits ESM v1 to v10 by
+version; each construct it does not render refuses with its own code before any artifact is planned.
+
+| Area | Renders at 4.73.1 | Refused (code) |
+| --- | --- | --- |
+| Slice kinds | `StateChange`, `StateView` | `Automation`, `Translate`, every reaction, capture, application trigger and clock specification (`STAGE-ESM-001`/`-024`); a reaction that both produces and invokes (`-037`, Stage#207; Arc 22.72.0+ can run it, and the scaffold's Arc 22.68.0 needs a proven override; hand-write one reactor, never split the reaction) |
+| Queries | optional keyed snapshot lookups; observable collections, keyed or unkeyed (since 4.49.0) | a snapshot list: `STAGE-ESM-010`; `filter`, `scoped to`, `performer`, composite `by`: `PLAY0268` at binding |
+| 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) |
+| 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) |
+| Descriptions, documentation | XML `<summary>`/`<remarks>` doc comments only (Stage#178 closed) | characters invalid in XML: `CLI-RENDER-005`; never behavior |
+
+Still bind-refused (not Stage): `reads` and `concurrency` (`PLAY0271`), command `handler`s, `pii`/`secret`
+(`PLAY0268`). Other rows of the table below that name 4.24 behavior are history.
+
+## Historical: what Stage 4.24 admitted
 
 Models using `eventsource`, `stream` or command routes are not renderable: they fail
 binding (`PLAY0268`) and Stage refuses their ESM version (`STAGE-ESM-016`); rendered
@@ -67,7 +92,7 @@ accepted with PLAY0565 information); either still refuses binding. Identity bloc
 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
-refusal above; current CLI 3.50.0 reaches Stage's v8 route checks. Never split hand-joined
+refusal above; the pinned CLI (`versions.md`) reaches Stage's v8 route checks. Never split hand-joined
 legacy ids or drop protected ids into routing to fit a renderer (PLAY0515).
 
 ## Authoring consequences in renderable mode
@@ -79,11 +104,14 @@ legacy ids or drop protected ids into routing to fit a renderer (PLAY0515).
   readmodel`). The seeded when-less `then query` only checks a lookup over a given read-model
   state; it proves no projection (Stage `SemanticSpecificationAdmission.Callers.cs`).
 - Use `$context.occurred` only; no `$context.identity.*` mappings.
-- A list is a design-only query and blocks binding, and so rendering, of the whole application on its own. A keyed `XById` sibling does not change that: while any list query remains, nothing in the model binds, runs or renders. Keep a list the domain needs and report the capability gap.
+- A list query binds (unfiltered, or narrowed by one `by` key); Stage 4.73.1 renders it only as an
+  `observable` collection, and refuses a snapshot list with `STAGE-ESM-010`. `filter`, `scoped to` and
+  `performer` queries block binding of the whole application. Keep a list the domain needs and report
+  the capability gap; marking it `observable` or keying it is a modeling decision for the user.
 - A `handler` (with or without `implementation` or `hint`) never binds; the slice is
   gap-fill, never "customized into" rendering.
-- Descriptions and documentation are never rendered (Stage#178): a rule that exists only in
-  prose is unenforced in rendered code.
+- Descriptions and documentation render only as XML doc comments (Stage#178 closed), never as
+  behavior: a rule that exists only in prose is unenforced in rendered code.
 
 ## Ownership, publication and recovery
 
@@ -103,8 +131,9 @@ legacy ids or drop protected ids into routing to fit a renderer (PLAY0515).
   `Customizations/styles.css`. The planner never reads it, and it never binds a modeled
   reaction or capture. A customization never makes a rejected model renderable.
 - `cratis render` does **not** build, test or run the application.
-- Stage 4.51.3's scaffold pins .NET 10, Arc 22.50.5, Chronicle client/kernel 19.32.0
-  and emits a `.frontend/` React/Vite app (Components 4.14.0, Scene 4.10.0).
+- Stage 4.73.1's scaffold pins .NET 10, Arc 22.68.0, Chronicle client/kernel 19.45.0
+  and emits a `.frontend/` React/Vite app (Components 4.26.2, Scene 4.21.0); these are not the latest
+  releases (`cratis-stage-rendering-and-sandbox` `references/rendered-application.md`).
   `CratisEmbeddedScreenplayEnabled=false`; `Directory.Packages.props` is managed,
   never edit it. `[ProtectedDecision]` / `DecisionRead<T>` are available to gap-fill,
   not Stage-emitted enforcement; projection/key admission and unit-of-work enrollment
@@ -116,7 +145,8 @@ V5 is four separate results (admission, publication, build, tests), plus runtime
 was exercised; formats and the Debug-only spec classes are in `verdicts.md`. Three cases
 stay distinct: admission failure (nothing rendered); an existing generated base plus
 separately authorized hand-written gap-fill; and a fully hand-written delivery. Never claim a
-whole-application V5 from a subset. Drift: compare successive `.cratis-render.json`
+whole-application V5 from a subset (`cratis render --scope` renders an admitted part; state the scope).
+Drift: `cratis render ... --check` (CLI 3.44.0+; exit 6 means pending changes), or compare successive `.cratis-render.json`
 `semanticRevision` values from renders with the same `--name` and inputs (see `versions.md`,
 "Revisions and descriptions"); not the MCP `modelRevision`, not `open-workspace.revision`.
 

package/package/corpus/skills/cratis-screenplay-toolchain/references/screenplay-contract-exceptions.json

@@ -25,7 +25,7 @@
     "text": "  remains on disk. On CLI 3.43.0: 9 requests and 9 responses, 37 tools,",
     "kind": "toolCount",
     "value": "37",
-    "reason": "Measured CLI 3.43.0 transcript, whose bundled Screenplay 4.127.0 exposes 37 tools; the standalone pin's catalog has 38. Update with the transcript when the CLI bundle changes."
+    "reason": "Measured historical CLI 3.43.0 transcript, whose bundled Screenplay 4.127.0 exposes 37 tools. Current compiler and bundle pins are in references/versions.md; this count describes only that transcript. Remove when the transcript is removed or replaced."
   },
   {
     "file": ".cratis/ai/skills/cratis-screenplay-model-review/SKILL.md",