@cratis/pi 7.27.3 → 7.28.0

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

@@ -17,13 +17,13 @@ probe; older probes retain their original labels in the other references.
 
 | Source | Pin | Evidence |
 | --- | --- | --- |
-| Screenplay language, standalone tool and MCP | **4.127.0** (`e70435a4`) | Released tag `v4.127.0`; installed `screenplay --version`; changed identity/compliance examples compiled |
-| cratis CLI | **3.41.0** | Released tag `v3.41.0`; installed `cratis --version` |
-| Screenplay bundled by CLI | **4.114.0** | CLI `v3.41.0:Directory.Packages.props` |
-| Stage bundled by CLI | **4.51.3** | Same file; the CLI's runtime image follows its Stage package version |
+| Screenplay language, standalone tool and MCP | **4.131.0** (`71f3ef37`) | Released tag `v4.131.0` and its published contract; `semantic-diff` source selections in `Source/DotNET/Screenplay.Mcp/McpRevisionDiff.cs` |
+| cratis CLI | **3.46.1** (`73578fbf`) | Released tag `v3.46.1`; source-checked, not a new render/browser probe |
+| Screenplay bundled by CLI | **4.130.0** | CLI `v3.46.1:Directory.Packages.props`; predates the 4.131.0 `semantic-diff` source objects |
+| Stage bundled by CLI | **4.52.0** | Same file; default runtime image `cratis/stage:4.52.0`, confirmed by `Source/Cli.Specs/for_RunCommand/when_running/with_a_folder_and_the_default_stage_tag.cs` |
 | 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 |
-| 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 |
+| 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 |
 
 The published `screenplay-contract.json` beside this reference is the machine-readable authority for PLAY codes, MCP tools and parameters, and standalone CLI commands/options. Its unchanged release bytes are pinned by `screenplay-contract.version` to the standalone version above. Before adding a claim, search this large JSON file by exact `code` in `diagnostics`, or by exact `name` in `mcpTools`/`cliCommands`, and inspect that object's retirement flag, parameters or options; do not load the full file into context. For example, search for `"code": "PLAY0029"` or `"name": "read-workspace"`; `screenplay-contract-exceptions.json` preserves explicitly reasoned historical statements, not current-release exceptions. Coverage gaps are mention inventories, not proof that a skill teaches a feature.
 
@@ -33,7 +33,7 @@ on PATH can shadow a newer install; inspect `which -a cratis`.
 
 ## Two compilers, one rule
 
-Standalone Screenplay 4.127.0 and the CLI's 4.114.0 bundle are different releases.
+Standalone Screenplay 4.131.0 and the CLI's 4.130.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.
@@ -65,20 +65,22 @@ for identity-stable selection.
 
 ## Admission boundaries
 
-Screenplay `v4.127.0:Source/DotNET/Screenplay/Semantics/Versions.cs` supports schema
+Screenplay `v4.131.0:Source/DotNET/Screenplay/Semantics/Versions.cs` supports schema
 pairs through v10. Generated values/responses and policy negation select v7;
 sources/streams and command/specification routes select v8; reaction
 `runs as system [role "<Role>"]` selects v10 and reference-executes on 4.125.0.
 The checked trusted-actor scenario is in captures-and-reactions
-`references/invocation-identity.md`. CLI 3.41.0's 4.114.0 compiler rejects its
-source with PLAY0137 (validation probe, exit 5). Stage 4.51.3's direct planner
-uses EsmSchemaV7Support and refuses v10 with STAGE-ESM-016; CLI's version gate
-separately refuses above v7 with CLI-RENDER-004. A source construct
+`references/invocation-identity.md`. The historical CLI 3.41.0/Screenplay 4.114.0
+validation probe rejected its source with PLAY0137 (exit 5); that is not a
+3.46.1 parser claim. Stage 4.52.0's direct planner uses EsmSchemaV7Support
+(`Source/Rendering.Cratis/Semantics/SemanticCratisAdmission.cs`) and refuses v10
+with STAGE-ESM-016; CLI's version gate separately refuses above v7 with
+CLI-RENDER-004. A source construct
 still requires explicit binder/runner/provider admission: operations, exact
 numeric mode and reaction refusals/redelivery remain authorable but unadmitted
 (`PLAY0268`). Never delete those contracts to obtain a green bind.
 
-CLI 3.41.0 `RenderedSemanticVersions.Newest` is **v7**:
+CLI 3.46.1 `RenderedSemanticVersions.Newest` is **v7**:
 `Source/Cli/Commands/Render/RenderedSemanticVersions.cs`. Models above it get
 `CLI-RENDER-004` before planning/publication. v7 generated values/responses reach
 Stage admission; they are not universally refused until CLI#261. That issue is
@@ -86,9 +88,17 @@ closed. Each unsupported construct still needs a Stage diagnostic, not a silent
 omission or inferred support from package versions.
 
 The renderable-subset and Stage references retain older probes explicitly;
-read them as tested snapshots, not as a claim that Stage 4.51.3 shares every
+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.46.1 defaults
+to Stage 4.52.0, so neither new rule applies 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`,
+`CratisRenderTarget.cs`); a newer renderer needs a CLI release that pins it.
+The Stage skill teaches the version-gated examples.
+
 At 4.127.0, `$identity` aliases built-in caller paths; declared identity details
 remain metadata and their executable reads report PLAY0268. Bare `pii`/`secret`
 still block binding; `personal` aliases `pii`. Legacy markers are accepted with

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

@@ -4,7 +4,7 @@
   "fixtures": [],
   "assertions": [
     { "kind": "play-compiles" },
-    { "kind": "skill-contains", "value": "4.127.0" },
+    { "kind": "skill-contains", "value": "4.131.0" },
     { "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

@@ -32,13 +32,13 @@ hand-writing an alternate shape.
   without dropping it, silently falling back or replacing it with a default.
 
 Keep those three lines separate in reports. Correct an old limitation only when
-the package/version you are using proves the new level. Verified public vector:
+the package/version you are using proves the new level. Historical verified vector:
 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, CLI 3.46.1 (its default Stage is still 4.52.0) and Studio 0.152.2. All
-three levels hold for the canonical `ScreenComposition`
-corpus:
+4.64.0, CLI 3.46.1 (bundled Screenplay 4.130.0; its default Stage is still 4.52.0) and
+Studio 0.152.2. All three levels hold for the canonical `ScreenComposition` corpus on
+the historical vector:
 
 - authoring and executable admission: MCP opens it with `sourceSuccess true`,
   `semanticSuccess true`, `executableReady true`, and the stdio MCP harness sends
@@ -111,8 +111,8 @@ presentation offers, never access control. Downstream runtime support is separat
 from parsing; do not publish an empty plain action as equivalent behavior.
 The complete checked model and conditions are in
 `cratis-screenplay-read-surface` `references/guarded-actions.md`, grounded in
-Screenplay v4.125.0 `screens.md`. CLI 3.41.0/Stage 4.51.3 reports unsupported
-screen actions with STAGE-SCENE-ACTION-001, not proof of runtime selection.
+Screenplay v4.125.0 `screens.md`. Historical CLI 3.41.0/Stage 4.51.3 checks reported
+unsupported screen actions with STAGE-SCENE-ACTION-001, not proof of runtime selection.
 
 ## Exposed template configuration
 

package/package/corpus/skills/cratis-specifications-csharp/SKILL.md

@@ -22,6 +22,9 @@ This skill is verified against these exact public releases:
 | `Cratis.Arc.Testing` | `22.16.0` | `CommandScenario<TCommand>` and `CommandResult` assertions |
 | `Cratis.Chronicle.Testing` | `18.3.0` | `EventScenario`, `ReadModelScenario<T>`, `ReactorScenario<T>` |
 
+Generated-value scenario pinning is verified separately against
+`Cratis.Arc.Testing` **22.68.0** (introduced in **22.67.0**).
+
 Reverify against the owning product repository before claiming support for
 another version. Never translate an assertion or helper name from memory.
 
@@ -82,6 +85,24 @@ real kernel with an out-of-process integration specification instead.
 
 Specification projects are named `<Source>.Specs` and run on xUnit.
 
+### Pin server-generated Handle values
+
+For Arc 22.67.0+, `CommandScenario<TCommand>` defaults to strict generation:
+without a named pin or `AllowGeneration()`, `Execute` returns a command result
+with `GeneratedValueNotPinned`, rather than throwing it. Import
+`Cratis.Arc.Testing.Commands`; configure `PinGeneratedValue(name, concept)`
+before the first execution, then assert the response/events and
+`GeneratedValues.Last<T>(name)` or `All<T>(name)`.
+
+Use `AllowGeneration()` only when the exact value is irrelevant. Late changes
+throw `GeneratedValuesMustBePinnedBeforeExecution`. Nested-command pins require
+both generic arguments: `PinGeneratedValue<TCommand, TOtherCommand>(name, value)`.
+Read the minimal pinned specification and capture semantics in
+[application-scenarios.md](references/application-scenarios.md#pin-generated-values).
+A plain-call decision spec passes the known concept directly to `Handle()`; it
+cannot prove pipeline generation or validation. Command declarations belong to
+`cratis-arc-command`.
+
 ## Step 2 — Create the folder structure
 
 ```

package/package/corpus/skills/cratis-specifications-csharp/references/application-scenarios.md

@@ -86,6 +86,78 @@ from `Cratis.Arc.Chronicle.Testing`.
 - **Validator and `Provide()` dependencies** are registered in
   `_scenario.Services`; the concrete validator is discovered automatically.
 
+### Pin generated values
+
+Verified at **Arc v22.68.0**, available in `Cratis.Arc.Testing` **22.67.0+**.
+For the `AllocateCartId` command from `cratis-arc-command`, whose
+`Handle([GeneratedValue("cart")] CartId cartId)` returns that id, specify the
+pipeline with a known concept pin. Import `Cratis.Arc.Commands` and
+`Cratis.Arc.Testing.Commands`; the usual specification global usings supply
+`Cratis.Specifications` and `Xunit`. In a dedicated spec project:
+
+```csharp
+// Copyright (c) Cratis. All rights reserved.
+// Licensed under the MIT license. See LICENSE file in the project root for full license information.
+
+using Cratis.Arc.Commands;
+using Cratis.Arc.Testing.Commands;
+
+namespace Shopping.Carts.for_AllocateCartId.when_allocating;
+
+public class and_value_is_pinned : Specification
+{
+    readonly CommandScenario<AllocateCartId> _scenario = new();
+    readonly CartId _cartId = new(Guid.Parse("9a073b78-423c-43bc-b94c-19e4c83d1001"));
+    CommandResult _result = default!;
+
+    void Establish() => _scenario.PinGeneratedValue("cart", _cartId);
+    async Task Because() => _result = await _scenario.Execute(new AllocateCartId());
+    void Destroy() => _scenario.Dispose();
+
+    [Fact] void should_succeed() => _result.ShouldBeSuccessful();
+    [Fact] void should_return_the_pinned_id() =>
+        ((CommandResult<CartId>)_result).Response.ShouldEqual(_cartId);
+    [Fact] void should_capture_the_pinned_id() =>
+        _scenario.GeneratedValues.Last<CartId>("cart").ShouldEqual(_cartId);
+    [Fact] void should_capture_it_once() =>
+        _scenario.GeneratedValues.All<CartId>("cart").ShouldContainOnly(_cartId);
+}
+```
+
+- Pins use the attribute's explicit name, or the C# parameter name without one.
+  Names are case-sensitive and pins are keyed by command type plus name.
+- Supply the concept, not a raw `Guid`. Incompatible/null pins yield
+  `PinnedGeneratedValueHasWrongType` during execution. Pins still undergo normal
+  concept validation; only validated values are captured.
+- Strict is the default. Without a pin, an unpinned generated parameter yields
+  `GeneratedValueNotPinned` as an exception outcome in `CommandResult`; `Execute`
+  does not throw it to the spec. Assert the unsuccessful/exception outcome when
+  specifying that failure, not a request-validation rejection.
+- `AllowGeneration()` opts into normal generation for unpinned values, including
+  nested commands, when exact values do not matter. Explicit pins still win.
+  Each pin supplies the same value on every execution; it is not a queue.
+- For a child invoked through `ICommandPipeline`, configure
+  `_scenario.PinGeneratedValue<ParentCommand, ChildCommand>("child", childId)`.
+  The extension declares `PinGeneratedValue<TOtherCommand>` but C# requires
+  **both** type arguments at the call site. This does not replace a same-named
+  parent pin.
+- `Last<T>(name)` returns the latest capture of that name and declared type,
+  failing if absent. `All<T>(name)` returns a read-only snapshot in resolution
+  order across executions (empty if none). Both include nested commands. Same
+  name/type captures combine; use distinct names to distinguish commands.
+- Configure pins and `AllowGeneration()` before the first execution, even if it
+  fails or has no generated parameters. Changes after that throw
+  `GeneratedValuesMustBePinnedBeforeExecution`; create a new scenario instead.
+  Validation alone neither generates values nor freezes configuration.
+- Do not log or trace captures. Do not replace/seed the production generator.
+  A direct-call decision spec supplies the known argument to `Handle()` itself.
+
+Guide: [Pin generated values in command specs](/arc/backend/csharp/testing/generated-values/).
+Source: **Arc v22.68.0**, `Source/DotNET/Testing/Commands/CommandScenarioGeneratedValueExtensions.cs`,
+`ScenarioGeneratedValueFixture.cs`, `ScenarioGeneratedValues.cs` and
+`GeneratedValuesCommandScenarioExtender.cs`;
+`Source/DotNET/Testing.Specs/Commands/for_CommandScenario/generated_values/when_pinning_a_value.cs`.
+
 ### Unhappy paths assert twice
 
 ```csharp
@@ -192,10 +264,14 @@ those substitutes after `Given` fires the events.
 
 ## Application conventions
 
-- **Use a per-specification value for anything under a uniqueness check** — a
-  fresh `Guid`, or a truncated `Guid.NewGuid().ToString("N")[..9]`. Hardcoded
-  values cause order-dependent flakes. Do not add `[Collection(…)]` to work
-  around a collision; that is the wrong fix here.
+- **Use a per-specification fixture value for anything under a shared uniqueness
+  check** — a fresh `Guid`, or a truncated `Guid.NewGuid().ToString("N")[..9]`.
+  Hardcoded values in shared storage cause order-dependent flakes. This is
+  fixture isolation, not advice to generate inside production `Handle()`;
+  for generated parameters, pin the typed expected fixture value before
+  execution. A known fixed pin is appropriate in an isolated scenario such as
+  the allocation-only example above. Do not add `[Collection(…)]` to work around
+  a collision; that is the wrong fix here.
 - **Sequence numbers are zero-based.** The first event is `0`, the tail of two
   events is `1`. The tail after a single append is `0`, never `1`.
 - A behavior covering several subjects groups its specifications under

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

@@ -42,12 +42,12 @@ argument or an invalid semantic option.
 
 | Source | Pin | Notes |
 | --- | --- | --- |
-| Stage | `4.52.0` (`v4.52.0`, `0e4fd87`) as the CLI 3.43.0 default; newer public packages exist (latest `4.64.0`, built on Scene 4.16.0) and are not part of the verified vector | Renderer, sandbox host, spec runner; the CLI default image is `cratis/stage:4.52.0`. Both define `STAGE-SCENE-ACTION-001` and `STAGE-SCENE-INTERACTION-001`. Earlier executed baselines: 4.51.3, 4.51.1, 4.49.5 and `v4.24.2` (`32dcac4`) |
-| cratis CLI | `3.43.0` (`v3.43.0`, `23e5a24`) | `cratis render`, `cratis run`; the tag pins `StageVersion` 4.52.0 and `ScreenplayVersion` 4.127.0. The public CLI renders the canonical corpus and runs the stdio MCP transcript; refusing an unresolvable UI profile and recovering a rendered application shipped in Cratis/cli#301. Older baselines: 3.41.0, 3.40.7, `v3.28.2` (`141c499`, Cratis/cli#253) |
-| Screenplay | bundled `4.127.0`; latest public language package `4.129.0` | The CLI bundles 4.127.0, so compiler claims made through `cratis` are 4.127.0 claims; use the standalone 4.129.0 tool only for language features newer than the bundle |
+| Stage | `4.52.0` (`v4.52.0`, `0e4fd87`) as the CLI 3.46.1 default; latest public `4.64.0` (Scene 4.16.0) is not in the verified vector | Default image `cratis/stage:4.52.0`; defines `STAGE-SCENE-ACTION-001` and `STAGE-SCENE-INTERACTION-001`. Case tables need 4.59.0, whole numbers as `long` need 4.61.0; the CLI default renderer applies neither. 4.52.0 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.46.1` (`v3.46.1`, `73578fbf`) | Source-checked `Directory.Packages.props` pins Stage 4.52.0 and Screenplay 4.130.0. `cratis run --tag` changes only the sandbox image; newer rendering needs a CLI pinning newer Stage. Executed render/browser/MCP baseline remains 3.43.0 (Stage 4.52.0, Screenplay 4.127.0), not a 3.46.1 probe; refusing an unresolvable UI profile and recovering a rendered application shipped in Cratis/cli#301. Older baselines: 3.41.0, 3.40.7, `v3.28.2` (`141c499`, Cratis/cli#253) |
+| Screenplay | bundled `4.130.0`; standalone pin `4.131.0` | Claims through CLI 3.46.1 are 4.130.0 claims; 4.131.0 `semantic-diff` source objects need the standalone MCP |
 | 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 |
 
-Everything below was read at those tags (`Source/Rendering.Cratis/**`, `README.md`,
+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
@@ -140,11 +140,12 @@ Facts that surprise:
 
 ## Historical Stage 4.24 admission
 
-Current pins are standalone Screenplay 4.127.0 / CLI 3.41.0 / Stage 4.51.3.
+Current pins are standalone Screenplay 4.131.0 / CLI 3.46.1 / Stage 4.52.0.
 Routes bind/reference-execute as v8; reaction `runs as` identity as v10.
-CLI renders through v7 only (CLI-RENDER-004 for newer model versions) and its
-older 4.114.0 parser rejects `runs as` (PLAY0137). Stage 4.51.3's direct planner
-also audits only through v7 (STAGE-ESM-016 otherwise). Source/identity contracts
+CLI renders through v7 only (CLI-RENDER-004 for newer model versions).
+The historical CLI 3.41.0/4.114.0 parser rejected `runs as` (PLAY0137);
+that is not a current parser refusal. Stage 4.52.0's direct planner also audits
+only through v7 (STAGE-ESM-016 otherwise). Source/identity contracts
 stay intact for gap-fill; source acceptance is not target admission.
 
 The following detailed 4.24.x probes are historical, not current pin claims.
@@ -195,6 +196,15 @@ Modeled specifications become xunit classes compiled in **Debug only**
 `<slice namespace>.when_<snake>` (so `when_x.when_x`), queries `when_<snake>_is_queried`,
 read models `when_<snake>_is_projected`.
 
+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.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.
+
 For UI, record what the generated output claims separately from what the model
 authored. On Stage 4.24 the generated scaffold is not screen parity evidence.
 On public CLI 3.43.0 / `cratis/stage:4.52.0` the canonical corpus publishes,

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

@@ -10,9 +10,11 @@
 - Source disagreements (trust the code)
 
 Current pins are in `cratis-screenplay-toolchain` `references/versions.md`:
-CLI 3.41.0 bundles Stage 4.51.3 / Screenplay 4.114.0. It admits through ESM v7
-to Stage planning; above v7 is CLI-RENDER-004. The CLI's v7 canonical-corpus
-planning spec receives STAGE-ESM-028/029 for generated values/responses.
+Standalone Screenplay is 4.131.0; CLI 3.46.1 bundles Stage 4.52.0 / Screenplay
+4.130.0 / Arc.Screenplay 22.54.0 / Chronicle 19.32.0 / Fundamentals 7.22.8.
+It admits through ESM v7 to Stage planning; above v7 is CLI-RENDER-004.
+The historical CLI 3.41.0 v7 canonical-corpus planning spec received
+STAGE-ESM-028/029 for generated values/responses.
 The detailed 4.24.x source/probe rows below have not been relabeled as current
 runtime verification; run admission on the actual bundled renderer.
 

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

@@ -0,0 +1,127 @@
+<!-- Copyright (c) Cratis. All rights reserved. -->
+<!-- Licensed under the MIT license. See LICENSE file in the project root for full license information. -->
+
+# Case tables and whole numbers: check the Stage version
+
+## Contents
+
+- CLI default versus Stage release
+- One specification per case (Stage 4.59.0+)
+- Whole numbers as long (Stage 4.61.0+)
+- Released source evidence
+
+## CLI default versus Stage release
+
+CLI 3.46.1 bundles Screenplay 4.130.0 and Stage 4.52.0. Its default renderer
+applies neither the case-table support introduced in Stage 4.59.0 nor the
+whole-number rule introduced in 4.61.0. It renders whole-number types as `int`
+and refuses models newer than ESM v7 with `CLI-RENDER-004` before Stage planning.
+A newer standalone Screenplay compiler does not upgrade the bundled renderer.
+
+`cratis run ./model --tag 4.63.2` selects a newer **sandbox image**; it does not
+change `cratis render`. The renderer is statically bundled and has no Stage
+package/image override. A newer renderer needs a CLI release that pins it.
+Sandbox execution is not generated-application verification.
+
+## One specification per case (Stage 4.59.0+)
+
+Case tables expand before rendering. The effective specification names are
+`<Specification>_<Case>`; Stage emits one Debug specification class per case,
+then applies its usual `when_<snake>` naming. This complete example yields
+`Registering_Small` and `Registering_Large`, rendered as
+`when_registering_small` and `when_registering_large` (one file/class each):
+
+```screenplay
+concept ProjectId : String
+concept ProjectName : String
+module Projects
+  feature Registration
+    slice StateChange Register
+      command RegisterProject
+        projectId ProjectId identifier
+        name ProjectName
+        produces ProjectRegistered
+          for projectId
+          name = name
+      event ProjectRegistered
+        name ProjectName
+      specification Registering
+        parameter name ProjectName
+        case Small name = "small"
+        case Large name = "large"
+        when RegisterProject
+          projectId = "project-1"
+          name = case.name
+        then ProjectRegistered
+          name = case.name
+```
+
+Generated path comparisons are case-insensitive. Adding `case large` alongside
+`case Large` can pass source validation but normalizes to the same generated
+path: Stage refuses the whole plan with `STAGE-CRATIS-004`, never overwrites one
+case with another. Choose distinct names in the model; do not edit generated files.
+
+A failing case in SpecRunner or Host results names its authored specification,
+case and effective fixtures: `Case '<Case>' of '<Specification>': … Effective
+fixtures: …`. Read the failure details and each case outcome; SpecRunner exit 0
+alone is not a pass. Map generated Debug test classes back to effective cases,
+not just to the authored table or a total count.
+
+## Whole numbers as long (Stage 4.61.0+)
+
+The **model's ESM version**, not the Stage package version alone, selects the
+C# whole-number type: v8 and later use `long`; v1–v7 retain `int` for stored-schema
+compatibility. This covers properties, concepts, command inputs, events, read
+models, stream ids, sentinels and literals (`0L`, `2147483648L`). Check generated
+frontend types separately; this C# admission rule does not establish their mapping.
+Screenplay's Double-mode whole-number range is
+±(2^53−1), not the entire C# `long` range; `numbers exact` remains unadmitted.
+
+This routed model selects ESM v8. On Stage 4.61.0+, `Quantity` wraps `long` and
+the fixture renders as `2147483648L`:
+
+```screenplay
+concept StockId : String
+concept Quantity : Int
+eventsource Stock
+  identifier StockId
+  stream Measurements
+module Inventory
+  feature Stock
+    slice StateChange Record
+      command RecordStock
+        stockId StockId identifier
+        quantity Quantity
+        stream Stock.Measurements
+        produces StockRecorded
+          for stockId
+          quantity = quantity
+      event StockRecorded
+        quantity Quantity
+      specification RecordingLargeQuantity
+        when RecordStock
+          stockId = "stock-1"
+          quantity = 2147483648
+        then StockRecorded
+          quantity = 2147483648
+```
+
+Without the `eventsource` declaration and command `stream` clause, the model is
+below v8. On Stage 4.61.0+, that out-of-`int` fixture is refused with
+`STAGE-ESM-031`; literals within −2147483648…2147483647 still render as `int`.
+Do not remove the fixture, narrow its value or patch generated C# to pass.
+Widening an already persisted event property from `int` to `long` requires a new
+Chronicle event generation; changing model version is not a safe schema migration.
+
+## Released source evidence
+
+- Stage `v4.59.0`: `Source/Rendering.Cratis/for_CratisArtifactRenderPlanner/given/a_specification_case_table.cs`,
+  `when_executing_generated_case_table_specifications.cs`, `when_refusing_colliding_case_names.cs`,
+  `CratisArtifactRenderPlanner.cs`; `Source/Specifications/SemanticSpecificationExecutor.cs`
+  and `Source/SpecRunner/for_Program/when_running_semantic_case_tables.cs`.
+- Stage `v4.61.0`: `Source/Rendering.Cratis/Semantics/SemanticTypeSystem.cs`,
+  `SemanticCratisAdmission.WholeNumbers.cs` and
+  `Source/Rendering.Cratis/Semantics/for_SemanticCratisAdmission/when_admitting_whole_number_literals/with_a_pre_v8_model.cs`.
+- CLI `v3.46.1`: `Directory.Packages.props`,
+  `Source/Cli/Commands/Render/{RenderSettings,CratisRenderTarget,RenderedSemanticVersions}.cs`,
+  `Source/Cli/Commands/Run/{RunSettings,StageContainer}.cs`.

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

@@ -26,6 +26,10 @@
     { "kind": "skill-contains", "value": "Cratis/cli#253" },
     { "kind": "skill-contains", "value": "Silent fallback to a default screen is a failure" },
     { "kind": "skill-contains", "value": "package/image versions" },
-    { "kind": "skill-contains", "value": "dropped authored UI" }
+    { "kind": "skill-contains", "value": "dropped authored UI" },
+    { "kind": "skill-contains", "value": "references/case-tables-and-whole-numbers.md" },
+    { "kind": "skill-contains", "value": "STAGE-CRATIS-004" },
+    { "kind": "skill-contains", "value": "STAGE-ESM-031" },
+    { "kind": "skill-contains", "value": "Stage 4.52.0 renderer applies neither new rule" }
   ]
 }

package/package.json

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