@cratis/pi 7.31.0 → 7.33.0

package/package/corpus/skills/cratis-screenplay-toolchain/references/screenplay-contract.version

@@ -1 +1 @@
-4.135.0
+4.139.0

package/package/corpus/skills/cratis-screenplay-toolchain/references/sources-and-streams.md

@@ -15,7 +15,7 @@ Sources, streams and command/specification routes bind and reference-execute as
 `specifications.md`, `Versions.cs`; the complete example below compiled with
 `--warnaserror` and passed `screenplay test` on 4.125.0.
 
-CLI 3.50.0/Stage 4.67.0 admits through v10 to construct checks, including v8
+The pinned CLI/Stage pair (`versions.md`) admits through v10 to construct checks, including v8
 routes. Routed read-model/query replay scenarios can still refuse STAGE-ESM-030;
 run admission before promising parity. Previous CLI 3.46.1/Stage 4.52.0 refused
 above v7 with CLI-RENDER-004. Keep routing intact when a target refuses it;

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

@@ -1,6 +1,6 @@
 # Traps (one line each, with the fix)
 
-Current pins: Screenplay 4.135.0 / CLI 3.50.0 (`versions.md`). Unless explicitly
+Current pins: `versions.md`. Unless explicitly
 updated below, [probed]/[source] rows retain their historical v4.66.0/CLI 3.28.2
 scope; negative capability claims there are not current verdicts. Current routes
 bind as v8, v7 reaches Stage planning, reference tests have CLI/MCP routes, and
@@ -15,7 +15,7 @@ exact numbers are documented in the grammar. Compiler syntax: `cheat-sheet.md`.
 7. Current V1 warns on absent projection/children/nested targets (PLAY0514) and unknown removal/capture events (PLAY0166). Opt-in field-origins checks find unmapped declared fields (PLAY0534) where coverage is known; still walk lineage for skipped/opaque shapes.
 8. Severity does not soften a rule: `severity warning` still rejects the command.
 9. Authorization (module AND feature AND construct) runs before validation; unauthorized is `then denied`, never `then error`.
-10. Without a declared actor an invocation is caller-less. At 4.125.0 declare reaction `runs as system role "<Role>"` (ESM v10), keep its gate, and reference-test the trusted path. The historical CLI 3.41.0/4.114.0 parser rejected this syntax (PLAY0137); previous CLI 3.46.1 refused v10 at its version gate; CLI 3.50.0/Stage 4.67.0 reaches construct checks but still refuses reaction identity (STAGE-ESM-034). Arc gap-fill uses `[ExecuteCommandsAsSystem]` for returned commands, not a fictional `given caller`.
+10. Without a declared actor an invocation is caller-less. At 4.125.0 declare reaction `runs as system role "<Role>"` (ESM v10), keep its gate, and reference-test the trusted path. The historical CLI 3.41.0/4.114.0 parser rejected this syntax (PLAY0137); previous CLI 3.46.1 refused v10 at its version gate; the pinned CLI/Stage pair (`versions.md`) reaches construct checks but still refuses reaction identity (STAGE-ESM-034). Arc gap-fill uses `[ExecuteCommandsAsSystem]` for returned commands, not a fictional `given caller`.
 11. A reaction `produces` without `for` lands on the trigger's event source; clock and application triggers need an explicit `for`.
 12. Explicit trailing `key` marks replace inference (never `identifier`); multipart read-model keys remain PLAY0268 (#599). Without marks, single-instance queries in the owning slice must agree on `by xId XId`, where `xId` is a read-model property. Only with no such identifier and an admitted list query does `*Id` inference run (collection-key exclusions: read-surface `references/named-keys.md`); queryless views need explicit `key`. The identifier equals the projection's effective key (table in slice-design `references/read-model-design.md`; full rule, including Stage's narrower admission and `STAGE-ESM-017`, in `cratis-stage-rendering-and-sandbox` `references/admission.md`). Never mark a read-model property `identifier`. (Without explicit `key`, PLAY0268 when identity inference is ambiguous or absent; PLAY0351 when a `given`/`then` readmodel block omits that property.)
 13. Projection `key` routes only on `from` (projection-level: PLAY0381). `all` is per event source. Joins never create instances and match the joined event's source id. [probed]
@@ -31,7 +31,7 @@ exact numbers are documented in the grammar. Compiler syntax: `cheat-sheet.md`.
 23. `@` escapes are mandatory for `tag`, `authorize`, `produces`, `reads`, `file`, `validate`, `sequence`, `occurred`, `causedBy`, `namespace`, `correlation`, `causation`, and projection `key`/`parent`/`with` as names.
 24. Canonicalizing edits can drop unplaceable comments (PLAY0288; inspect `droppedCommentCount`); keep durable rationale in fenced Markdown `documentation`, not `//`, and summaries in `description`. Documentation survives canonical printing but changes neither executable bytes nor `modelRevision`; it is not rendered code.
 25. MCP writes: propose, review, approval, apply by the identity owner (the session that owns the MCP connection); other subagents return edit requests; proposals are connection-local, at most 16 (`cratis-screenplay-model-authoring`).
-26. Operations/systems and `numbers exact` source mode remain unadmitted. Qualifying retained non-route Double literals instead select published v11 at 4.135.0. Sources/streams/routes bind as v8, public/direction forms v9, identity/overrides/filters v10. CLI 3.50.0 reaches Stage construct checks through v10; v11 needs explicit consumer admission. See `versions.md`.
+26. Operations/systems and `numbers exact` source mode remain unadmitted. Qualifying retained non-route Double literals instead select published v11 at 4.135.0. Sources/streams/routes bind as v8, public/direction forms v9, identity/overrides/filters v10. The pinned CLI (`versions.md`) reaches Stage construct checks through v10; v11 needs explicit consumer admission. See `versions.md`.
 27. Translate crosses the public boundary: inbound foreign/data to private local facts; outbound private facts to one local public type. Public metadata needs explicit direction; a quoted origin is an unverified store name, not a path. Commands never publish public events. In-app private follow-up is Automation; see public-events-and-direction in the method skill.
 28. Personas drive the board: a persona must list every policy on the path, including module-level `IsAuthenticated`.
 29. A sample's source check is not execution. Run selected admitted specifications through `screenplay test`/MCP; given==when clock still fires no scheduled occurrence.

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

@@ -28,7 +28,7 @@ V3 are read from the MCP server or from a render, V1 and V5 from the CLIs.
 
 | Tool | Command | Pass | Fail |
 | --- | --- | --- | --- |
-| Standalone 4.135.0 (preferred) | `screenplay <model-root> --warnaserror --no-color` | exit 0 and a nonzero compiled file count | exit 1 defects; exit 2 could not run/invalid arguments or input |
+| Standalone (preferred; pin: `versions.md`) | `screenplay <model-root> --warnaserror --no-color` | exit 0 and a nonzero compiled file count | exit 1 defects; exit 2 could not run/invalid arguments or input |
 | cratis (fallback) | `cratis screenplay validate <model-folder> --warnings-as-errors -o json-compact` | exit 0 | exit 5; exit 1 means missing path or no files |
 
 - Validate the complete application root, not an independently selected fragment.
@@ -85,7 +85,7 @@ never "specifications pass".
   `secret`, authorization, list queries, automations or rules to reach V3; record the
   slice and the code in the gap list.
 - A model is executable only on the compiler that bound it. V3 does not carry
-  to render admission: CLI 3.50.0 passes through ESM v10 to Stage construct
+  to render admission: the pinned CLI (`versions.md`) passes through ESM v10 to Stage construct
   checks; newer models receive CLI-RENDER-004. Public publication and reaction
   identity/filters/production overrides still receive typed Stage refusals.
   The old 3.28.x/Stage 4.24.x probes remain historical in the subset references.
@@ -152,9 +152,9 @@ source change makes earlier verdicts stale.
 
 Historical corpus fences were checked with standalone 4.68.0 and CLI 3.28.2.
 Do not promote those results to current pins without rerunning. Check each changed
-complete fence with standalone 4.135.0 `--warnaserror`; run `screenplay test` for
+complete fence with the pinned standalone tool (`versions.md`) `--warnaserror`; run `screenplay test` for
 specification examples, and verify expected-diagnostic examples against their
-claimed codes. Where bundle compatibility matters, also check CLI 3.50.0.
+claimed codes. Where bundle compatibility matters, also check the pinned CLI (`versions.md`).
 The `// Needs the standalone screenplay compiler (ESM v6)` first-line marker belonged to cratis
 before 3.28.2, which could not validate those fences; no fence carries it now, and a
 checker that still skips marked fences under `cratis` skips nothing. Examples meant to execute are also opened through MCP and

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

@@ -17,10 +17,10 @@ probe; older probes retain their original labels in the other references.
 
 | Source | Pin | Evidence |
 | --- | --- | --- |
-| Screenplay language, standalone tool and MCP | **4.135.0** (`b4e46130`) | Released tag `v4.135.0` and its unchanged published contract |
-| cratis CLI | **3.50.0** (`546dea12`) | Released tag `v3.50.0`; source-checked, not a new render/browser probe |
-| Screenplay bundled by CLI | **4.131.0** | CLI `v3.50.0:Directory.Packages.props`; includes `semantic-diff` source objects, not v11 literal lowering |
-| Stage bundled by CLI | **4.67.0** | Same file; renderer and default sandbox image use the same Stage release |
+| Screenplay language, standalone tool and MCP | **4.139.0** (`dcd84574`) | Released tag `v4.139.0` and its unchanged published contract; enum numbers/ESM v12 and property references |
+| cratis CLI | **3.53.1** | Released tag `v3.53.1`; source-checked, not a new render/browser probe |
+| Screenplay bundled by CLI | **4.137.0** | CLI `v3.53.1:Directory.Packages.props`; enum-number authoring, not v12 binding |
+| Stage bundled by CLI | **4.73.1** | Same file; Stage's own `Directory.Packages.props` also pins Screenplay 4.137.0 |
 | Cratis.Arc.Screenplay bundled by CLI | **22.54.0** | Same file; this is the generator package, not a blanket rendered-app dependency pin |
 | Chronicle / Fundamentals bundled by CLI | **19.32.0 / 7.22.8** | Same file |
 | Historical Stage 4.51.3 rendered backend | **Arc 22.50.5 / Chronicle 19.32.0** | Stage `v4.51.3:Source/Rendering.Cratis/Scaffolding/CratisBackendApplicationScaffoldProfile.cs`; client/testing/image match; scaffold disables embedded reverse extraction |
@@ -44,7 +44,7 @@ or renderer probes below as results from the newer bundle.
 
 ## Two compilers, one rule
 
-Standalone Screenplay 4.135.0 and CLI 3.50.0's 4.131.0 bundle are different releases.
+Standalone Screenplay 4.139.0 and CLI 3.53.1's 4.137.0 bundle are different releases.
 Prefer standalone for the current language checks; CLI owns generation, Prologue
 and rendering. Name the tool/version with every verdict. No verdict transfers
 between differing compilers without checking the same inputs there.
@@ -76,8 +76,8 @@ for identity-stable selection.
 
 ## Admission boundaries
 
-Screenplay `v4.135.0:Source/DotNET/Screenplay/Semantics/Versions.cs` supports
-schema pairs through v11. Admission selects by use:
+Screenplay `v4.139.0:Source/DotNET/Screenplay/Semantics/Versions.cs` supports
+schema pairs through v12. Admission selects by use:
 
 - v7: generated values/responses and policy negation.
 - v8: sources/streams and command/specification routes.
@@ -100,23 +100,38 @@ schema pairs through v11. Admission selects by use:
   admit `numbers exact` source mode or arbitrary precision. At this tag,
   interoperability documentation still says "claimed, unreleased"; this corpus
   follows Versions.cs and decision 0066's publication boundary.
+- **Published, frozen v12 in 4.139.0:** non-positional explicit enum numbers
+  select v12, carrying optional canonical last `numbers` parallel to `values`.
+  Positional pins retain earlier executable bytes/version/revision; unnumbered
+  enums retain positional meaning. Names remain fixture/condition/specification
+  values. Strict reading rejects arrays in older versions, without enum values,
+  with mismatched length, duplicates, non-int32 entries or positional numbers
+  (non-canonical). Consumers must admit v12 explicitly. Authoring shipped in
+  4.137.0 (decision 0065); syntax/example: command-surface `references/enum-numbers.md`.
 
 Decision 0066 freezes a version when any exposing NuGet/npm package is published,
 including prereleases. Later byte-changing features take the next version at
 admission; a byte-preserving extension under 0004 is the exception. Published
-numbers never change or get reused. Enum member numbers (decision 0065) remain
-unimplemented/unadmitted and have no numbered claim. Concept generation strategies
-and freshness (decision 0054, #616) are accepted but not implemented. Operations,
+numbers never change or get reused. Enum member numbers are admitted as v12;
+this does not admit flags or numeric values in name-based specifications.
+Concept generation strategies and freshness (decision 0054, #616) are accepted but not implemented. Operations,
 exact source numeric mode and reaction refusals/redelivery remain PLAY0268.
 Composite read-model keys/query blocks are also still PLAY0268 (#599), not
 admitted by the 4.129.0 authoring delivery; a single explicit key preserves bytes.
 Never delete these contracts to obtain a green bind.
 
-CLI 3.50.0 `RenderedSemanticVersions.Newest` is **v10**:
-`Source/Cli/Commands/Render/RenderedSemanticVersions.cs`. Stage 4.67.0 uses
-EsmSchemaV10Support in `SemanticVersionFeatures.cs` and construct checks in
-`SemanticVersionFeatureAdmission.cs`. v11 gets CLI-RENDER-004 before planning
-(and STAGE-ESM-016 at the direct Stage version gate). Through v10 is not blanket
+CLI 3.53.1 `RenderedSemanticVersions.Newest` is **v10**:
+`Source/Cli/Commands/Render/RenderedSemanticVersions.cs`. Stage 4.73.1 uses
+EsmSchemaV10Support in `Source/Rendering.Cratis/Semantics/SemanticVersionFeatures.cs`
+and construct checks in `SemanticVersionFeatureAdmission.cs`. Both bundle
+Screenplay 4.137.0: non-positional enum numbers pass source validation but
+fail executable binding with PLAY0268, before renderer version admission.
+Standalone >= 4.139.0 binds them as v12; that verdict does not transfer to
+`cratis render`. The bundled compiler and Stage do not support reading v12 ESM.
+A compiler upgrade alone would not lift the CLI/Stage v10 admission ceiling.
+Bound v11 models get CLI-RENDER-004 before planning (STAGE-ESM-016 at the
+Stage version gate); this is not the diagnostic path for v12 source on these pins.
+Through v10 is not blanket
 render support: public publication STAGE-ESM-032, foreign events/event captures
 033, reaction identity 034, reaction filters 035 and production overrides 036
 remain refused; reducer filters render. ESM v8 routes reach their own checks.
@@ -130,8 +145,8 @@ read them as tested snapshots, not as a claim that Stage 4.52.0 shares every
 4.24.2 limitation. Query the actual bundled renderer before a V5 claim.
 
 Stage case tables require 4.59.0; ESM v8 whole numbers as `long` and the
-pre-v8 out-of-`int` refusal STAGE-ESM-031 require 4.61.0. CLI 3.50.0 defaults
-to Stage 4.67.0, so both rules apply. Previous CLI 3.46.1 bundled Screenplay
+pre-v8 out-of-`int` refusal STAGE-ESM-031 require 4.61.0. Historical CLI 3.50.0
+defaulted to Stage 4.67.0; current CLI 3.53.1 defaults to 4.73.1, so both rules apply. Previous CLI 3.46.1 bundled Screenplay
 4.130.0 and Stage 4.52.0; neither rule applied there. `cratis run --tag 4.63.2`
 selects a newer sandbox image only (`RunSettings.cs`), not a renderer package.
 `cratis render` has a statically bundled target (`RenderSettings.cs`,

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

@@ -10,7 +10,9 @@
     { "kind": "skill-contains", "value": "Composite read-model keys/query blocks are also still PLAY0268", "file": "references/versions.md" },
     { "kind": "skill-contains", "value": "the **whole source, stream and stream id**", "file": "references/production-routes-and-filters.md" },
     { "kind": "play-compiles" },
-    { "kind": "skill-contains", "value": "4.135.0" },
+    { "kind": "skill-contains", "value": "4.139.0" },
+    { "kind": "skill-contains", "value": "Published v12" },
+    { "kind": "skill-contains", "value": "PLAY0671", "file": "references/diagnostics.md" },
     { "kind": "skill-contains", "value": "PLAY0653", "file": "references/diagnostics.md" },
     { "kind": "skill-contains", "value": "PLAY0646", "file": "references/diagnostics.md" },
     { "kind": "skill-contains", "value": "PLAY0595", "file": "references/diagnostics.md" },

package/package/corpus/skills/cratis-screenplay-ui-composition/references/screen-composition-contract.md

@@ -37,8 +37,8 @@ CLI 3.43.0 with its default `cratis/stage:4.52.0` and bundled Screenplay 4.127.0
 the executed vector renders on Scene 4.15.0. Packages published since are newer than
 that vector and are not claimed verified: Scene 4.17.0, Screenplay 4.133.1, Stage
 4.64.0, previous CLI 3.46.1 (bundled Screenplay 4.130.0; its then-default Stage was
-4.52.0) and Studio 0.152.2. Current pins are CLI 3.50.0 (Screenplay 4.131.0 / Stage
-4.67.0) and standalone Screenplay 4.135.0; see toolchain `references/versions.md`.
+4.52.0) and Studio 0.152.2. Current pins:
+`cratis-screenplay-toolchain/references/versions.md`.
 All three levels hold for the canonical `ScreenComposition` corpus on the historical vector:
 
 - authoring and executable admission: MCP opens it with `sourceSuccess true`,

package/package/corpus/skills/cratis-stage-rendering-and-sandbox/SKILL.md

@@ -42,18 +42,16 @@ argument or an invalid semantic option.
 
 | Source | Pin | Notes |
 | --- | --- | --- |
-| Stage | `4.67.0` as CLI 3.50.0's renderer and default sandbox image | Source-checked, not a new executed vector. Case tables (4.59.0+) and whole numbers as `long` from ESM v8 (4.61.0+) apply to this default. Previous CLI 3.46.1 used Stage 4.52.0 (`0e4fd87`) and applied neither. Stage 4.52.0 defines `STAGE-SCENE-ACTION-001`/`STAGE-SCENE-INTERACTION-001` and was executed on CLI 3.43.0. Earlier executed baselines: 4.51.3, 4.51.1, 4.49.5 and `v4.24.2` (`32dcac4`) |
-| cratis CLI | `3.50.0` (`546dea12`) | `v3.50.0:Directory.Packages.props` pins Stage 4.67.0, Screenplay 4.131.0, Arc.Screenplay 22.54.0, Chronicle 19.32.0, Fundamentals 7.22.8. `cratis run --tag` changes only the sandbox image. Executed render/browser/MCP baseline remains 3.43.0 (Stage 4.52.0, Screenplay 4.127.0), not a 3.50.0 probe; UI-profile refusal and rendered recovery shipped in Cratis/cli#301. Older baselines: 3.41.0, 3.40.7, `v3.28.2` (`141c499`, Cratis/cli#253) |
-| Screenplay | bundled `4.131.0`; standalone pin `4.135.0` | Name the compiler: bundled 4.131.0 lacks v11 literal lowering; `semantic-diff` source objects are in both current tools |
+| Stage | See toolchain pins below | Historical source check: Stage 4.67.0 under CLI 3.50.0, not a new executed vector. Case tables (4.59.0+) and whole numbers as `long` from ESM v8 (4.61.0+) apply to the pinned default. Previous CLI 3.46.1 used Stage 4.52.0 (`0e4fd87`) and applied neither. Stage 4.52.0 defines `STAGE-SCENE-ACTION-001`/`STAGE-SCENE-INTERACTION-001` and was executed on CLI 3.43.0. Earlier executed baselines: 4.51.3, 4.51.1, 4.49.5 and `v4.24.2` (`32dcac4`) |
+| cratis CLI | See toolchain pins below | Historical source check: `v3.50.0:Directory.Packages.props` pins Stage 4.67.0, Screenplay 4.131.0, Arc.Screenplay 22.54.0, Chronicle 19.32.0, Fundamentals 7.22.8. `cratis run --tag` changes only the sandbox image. Executed render/browser/MCP baseline remains 3.43.0 (Stage 4.52.0, Screenplay 4.127.0), not a 3.50.0 probe; UI-profile refusal and rendered recovery shipped in Cratis/cli#301. Older baselines: 3.41.0, 3.40.7, `v3.28.2` (`141c499`, Cratis/cli#253) |
+| Screenplay | See toolchain pins below | Name the compiler; binding and renderer admission differ. Historical 4.131.0 lacked v11 literal lowering; `semantic-diff` source objects require 4.131.0 or later |
 | Rendered applications | Arc, Chronicle, Scene 4.15.0, .NET 10 | CLI 3.43.0 renders the canonical corpus to `.cratis-render.json`, backend artifacts, `.frontend/**`, `scene.json`, `src/bindings.ts`. Verify the generated package set for each render before claiming exact Scene runtime parity |
 
 The retained admission and runtime evidence below was read at its named tags (`Source/Rendering.Cratis/**`, `README.md`,
 `Documentation/**` in Stage; `Source/Cli/Commands/Render/**` and
 `Documentation/reference/screenplay.md` in the CLI), and the vertical in
 [references/render-example.md](references/render-example.md) was rendered, built and
-tested with cratis 3.28.2 (re-run on 3.28.3). Read `references/render-example.md` when you need a complete renderable model and the observed render, build, and test results. The full version table (Screenplay 4.66.0, Arc 22.50.5,
-Chronicle 19.32.0 and the tool split) is in the `cratis-screenplay-toolchain` skill,
-`references/versions.md`. Stage 4.51.3 scaffolds Arc `22.50.5` and Chronicle
+tested with cratis 3.28.2 (re-run on 3.28.3). Read `references/render-example.md` when you need a complete renderable model and the observed render, build, and test results. Pins/tool split: `cratis-screenplay-toolchain/references/versions.md`. Stage 4.51.3 scaffolds Arc `22.50.5` and Chronicle
 `19.32.0`, with `CratisEmbeddedScreenplayEnabled=false`. `[ProtectedDecision]` and
 `DecisionRead<T>` are available to gap-fill code, not automatically emitted or
 protected by Stage; admission and unit-of-work enrollment still matter. See
@@ -140,7 +138,8 @@ Facts that surprise:
 
 ## Historical Stage 4.24 admission
 
-CLI 3.50.0/Stage 4.67.0 reaches construct checks through v10; v11 gets
+The pinned CLI/Stage pair (`cratis-screenplay-toolchain/references/versions.md`)
+reaches construct checks through v10; v11 gets
 CLI-RENDER-004 (direct Stage: STAGE-ESM-016). Public/foreign events, reaction
 identity/filters and production overrides still refuse. Reducer filters render.
 Read [admission](references/admission.md) for STAGE-ESM-032–036 and previous
@@ -198,8 +197,8 @@ Stage 4.59.0+ expands a case table to effective `<Specification>_<Case>` names
 and one generated class per case; normalized path collisions refuse the plan
 with `STAGE-CRATIS-004`. Failed case results include the case and effective fixtures.
 Stage 4.61.0+ renders whole numbers as `long` from ESM v8, retains `int` below
-v8 and refuses out-of-`int` literals there with `STAGE-ESM-031`. CLI 3.50.0's
-Stage 4.67.0 default applies both rules. Previous CLI 3.46.1's
+v8 and refuses out-of-`int` literals there with `STAGE-ESM-031`. The pinned Stage default applies both rules;
+pins: toolchain `references/versions.md`. Previous CLI 3.46.1's
 Stage 4.52.0 renderer applies neither new rule. Read
 [case tables and whole numbers](references/case-tables-and-whole-numbers.md)
 for complete examples, stored-schema consequences and the sandbox-only `--tag` override.

package/package/corpus/skills/cratis-stage-rendering-and-sandbox/references/admission.md

@@ -9,11 +9,10 @@
 - Observed refusals
 - Source disagreements (trust the code)
 
-Current pins are in `cratis-screenplay-toolchain` `references/versions.md`:
-Standalone Screenplay is 4.135.0; CLI 3.50.0 bundles Stage 4.67.0 / Screenplay
-4.131.0 / Arc.Screenplay 22.54.0 / Chronicle 19.32.0 / Fundamentals 7.22.8.
-It admits through ESM v10 to construct planning; above v10 is CLI-RENDER-004.
-Stage 4.67.0 `SemanticVersionFeatures`/`SemanticVersionFeatureAdmission` refuse
+Current pins: `cratis-screenplay-toolchain/references/versions.md`.
+The pinned CLI admits through ESM v10 to construct planning; a bound newer model
+gets CLI-RENDER-004. Binding with the bundled compiler is a separate prerequisite.
+The pinned Stage's `SemanticVersionFeatures`/`SemanticVersionFeatureAdmission` refuse
 public publication (STAGE-ESM-032), foreign events/events-source captures (033),
 reaction identity (034), reaction filters (035) and production overrides (036).
 Reducer filters render. ESM v8 routes have construct checks including refusal of

package/package/corpus/skills/cratis-stage-rendering-and-sandbox/references/case-tables-and-whole-numbers.md

@@ -12,8 +12,8 @@
 
 ## CLI default versus Stage release
 
-CLI 3.50.0 bundles Screenplay 4.131.0 and Stage 4.67.0. Its default renderer
-applies case-table support introduced in Stage 4.59.0 and the whole-number rule
+Current CLI/compiler/Stage pins: `cratis-screenplay-toolchain/references/versions.md`.
+The pinned default renderer applies case-table support introduced in Stage 4.59.0 and the whole-number rule
 introduced in 4.61.0: v8+ whole numbers use `long`, earlier versions keep `int`.
 CLI and Stage admit through v10 to construct checks; newer versions receive
 CLI-RENDER-004 before planning (direct Stage: STAGE-ESM-016).

package/package/corpus/skills/cratis-stage-rendering-and-sandbox/verification.json

@@ -3,7 +3,7 @@
   "input": "Can Stage render this Screenplay model, and how do I re-render it safely after someone edited Program.cs?",
   "fixtures": [],
   "assertions": [
-    { "kind": "skill-contains", "value": "Stage 4.67.0 default applies both rules" },
+    { "kind": "skill-contains", "value": "pinned Stage default applies both rules" },
     { "kind": "skill-contains", "value": "Reducer filters render" },
     { "kind": "play-compiles" },
     { "kind": "skill-contains", "value": "`cratis render`" },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cratis/pi",
-  "version": "7.31.0",
+  "version": "7.33.0",
   "description": "Configuration-aware Cratis AI integration for Pi",
   "type": "module",
   "files": [