@cratis/pi 7.19.0 → 7.21.0

package/package/corpus/rules/concepts.md

@@ -64,15 +64,23 @@ public record AuthorName(string Value) : ConceptAs<string>(Value)
 ## Chronicle stream identity rules
 
 ```csharp
-public record AuthorId(Guid Value) : EventSourceId<Guid>(Value)
+public record AuthorId(Guid Value) : EventSourceId<Guid>(Value), IGeneratable<AuthorId>
 {
-    public static AuthorId New() => new(Guid.NewGuid());
+    public static AuthorId New() => new(GenerateValue.Uuid());
     public static implicit operator AuthorId(Guid value) => new(value);
 }
 ```
 
 - `New()`, primitive → derived ID conversion, and sentinels are optional domain
   conveniences; `EventSourceId<T>` does not create an arbitrary derived type.
+- When the system creates the value, implement `IGeneratable<TSelf>` and use
+  `GenerateValue.Uuid()` (or `GenerateValue.UuidV7()` when index locality
+  matters), both from `Cratis.Concepts` in Cratis.Fundamentals 7.23.0 or later.
+  Never `System.Random`. A client-supplied identifier is an input, not something
+  to generate; see the **cratis-fundamentals-concept** skill.
+- Arc and Chronicle can resolve an older Cratis.Fundamentals. Check the resolved
+  version first; if it is below 7.23.0, add a direct `Cratis.Fundamentals`
+  7.23.0 or later reference, or keep the existing `static New()` (without the interface) until you can.
 - The exact `EventSourceId<T>` base supports conversions among its underlying
   `T`, string, typed ID, and untyped `EventSourceId`, but those operators do not
   construct your derived domain record from every source form.

package/package/corpus/rules/vertical-slices.md

@@ -54,10 +54,10 @@ Every domain identifier or named value is a typed record — raw `string`/`Guid`
 - **[contract] Chronicle stream identities** derive from `EventSourceId<T>` with an `IComparable` underlying primitive. Add `NotSet`, `New()`, or a `T` → derived-id operator only when the domain API justifies it; typed empty/zero values are real specified stream IDs. The base conversion surface does not construct every derived domain record automatically.
 
 ```csharp
-public record AuthorId(Guid Value) : EventSourceId<Guid>(Value)
+public record AuthorId(Guid Value) : EventSourceId<Guid>(Value), IGeneratable<AuthorId>
 {
     public static readonly AuthorId NotSet = new(Guid.Empty);
-    public static AuthorId New() => new(Guid.NewGuid());
+    public static AuthorId New() => new(GenerateValue.Uuid());
     public static implicit operator AuthorId(Guid value) => new(value);
 }
 
@@ -67,6 +67,8 @@ public record AuthorName(string Value) : ConceptAs<string>(Value)
 }
 ```
 
+`IGeneratable<T>` and `GenerateValue` need Cratis.Fundamentals 7.23.0 or later. Arc and Chronicle can resolve an older version; add a direct reference or keep a plain `static New()` until then (see [concepts.md](./concepts.md)).
+
 **[convention] Placement:** slice-specific concept → in the slice file; feature-shared → feature folder; module-shared → module folder; app-wide → `Common/`. Scan `Common/` and the feature folder before creating a new concept. See [concepts.md](./concepts.md) for full patterns, or invoke the **cratis-fundamentals-concept** skill.
 
 ## Commands

package/package/corpus/skills/cratis-fundamentals-concept/SKILL.md

@@ -15,7 +15,7 @@ This skill is verified against these exact public releases:
 
 | Package | Version | Purpose |
 | --- | --- | --- |
-| `Cratis.Fundamentals` | `7.19.2` | `Cratis.Concepts.ConceptAs<T>` |
+| `Cratis.Fundamentals` | `7.23.0` | `Cratis.Concepts.ConceptAs<T>`, `IGeneratable<TSelf>` and `GenerateValue` |
 | `Cratis.Chronicle` | `18.3.0` | `Cratis.Chronicle.Events.EventSourceId` and `EventSourceId<T>` |
 
 Reverify product sources before claiming support for another version.
@@ -76,6 +76,55 @@ A `NotSet` or `Empty` value is optional domain policy. Add one only when the
 chosen primitive value is impossible or explicitly reserved in that domain.
 Do not assume `string.Empty`, `0`, or `Guid.Empty` is universally invalid.
 
+## Let a concept generate its own value
+
+Check the Cratis.Fundamentals version the project resolves first. Arc and
+Chronicle can bring an older one; when it is below 7.23.0, add a direct
+`Cratis.Fundamentals` 7.23.0 or later package reference, or keep the existing
+`static New()` (without the interface) until you can.
+
+When the system, not the caller, creates a value, the concept declares how by
+implementing `IGeneratable<TSelf>` (`Cratis.Concepts`, Cratis.Fundamentals
+7.23.0 or later). The interface requires `static abstract TSelf New()`, so
+generic code constrained on `where T : IGeneratable<T>` calls `T.New()` without
+reflection. Generate a UUID with `GenerateValue`, never with `Guid.NewGuid()` in
+scattered call sites and never with `System.Random`:
+
+```csharp
+using Cratis.Concepts;
+
+public record <ConceptName>(Guid Value) : ConceptAs<Guid>(Value), IGeneratable<<ConceptName>>
+{
+    public static <ConceptName> New() => new(GenerateValue.Uuid());
+}
+```
+
+Both helpers return a `Guid` with the RFC 9562 variant and fill their random
+bits from `RandomNumberGenerator`:
+
+- `GenerateValue.Uuid()` — version 4, 122 random bits. The default.
+- `GenerateValue.UuidV7()` — version 7: Unix-epoch milliseconds first, then 74
+  random bits. Choose it only when database index locality or rough creation
+  order matters, after checking how the database stores and compares UUIDs. It reveals the creation time, it is **not** monotonic within a
+  millisecond, and clock adjustments can reorder values.
+
+Neither helper guarantees uniqueness; a collision is extremely unlikely, not
+impossible. `IGeneratable<TSelf>` is not limited to Guid-backed concepts, but
+`GenerateValue` only produces UUIDs.
+
+Do not generate when:
+
+- The client supplies the identifier. It is an input; keep it.
+- The value must be secret or authenticate someone. A UUID is an identifier,
+  not a token; use a dedicated secure-token API.
+- The same input must yield the same value. Random generation is not
+  idempotency; derive the value deterministically, or persist and reuse the
+  first one.
+
+In specifications, construct the concept from a known value
+(`new <ConceptName>(Guid.Parse("…"))`) and assert against it. Do not seed or
+replace the generator. Guide: `/fundamentals/csharp/generating-values/`.
+
 ## Create a Guid-backed Chronicle stream identity
 
 Use this shape only for an identity actually supplied to Chronicle append/read
@@ -86,6 +135,7 @@ operations as the event-source ID.
 // Licensed under the MIT license. See LICENSE file in the project root for full license information.
 
 using Cratis.Chronicle.Events;
+using Cratis.Concepts;
 
 namespace <NamespaceRoot>.<Feature>;
 
@@ -93,13 +143,13 @@ namespace <NamespaceRoot>.<Feature>;
 /// Represents the event-source identity of a <description>.
 /// </summary>
 /// <param name="Value">The underlying Guid value.</param>
-public record <ConceptName>(Guid Value) : EventSourceId<Guid>(Value)
+public record <ConceptName>(Guid Value) : EventSourceId<Guid>(Value), IGeneratable<<ConceptName>>
 {
     /// <summary>
     /// Creates a new <ConceptName>.
     /// </summary>
     /// <returns>A new <ConceptName>.</returns>
-    public static <ConceptName> New() => new(Guid.NewGuid());
+    public static <ConceptName> New() => new(GenerateValue.Uuid());
 
     /// <summary>
     /// Converts a Guid to a <ConceptName>.
@@ -108,8 +158,8 @@ public record <ConceptName>(Guid Value) : EventSourceId<Guid>(Value)
 }
 ```
 
-`New()` and the primitive-to-derived conversion are conveniences on this domain
-type. `EventSourceId<T>` does not construct an arbitrary derived identity for
+`New()` (through `IGeneratable<TSelf>`) and the primitive-to-derived conversion
+are conveniences on this domain type. `EventSourceId<T>` does not construct an arbitrary derived identity for
 you.
 
 ## Create a non-Guid Chronicle stream identity
@@ -185,6 +235,9 @@ repository structure.
 - `ConceptAs<T>` and `EventSourceId<T>` use an `IComparable` underlying type.
 - A concept contains exactly one wrapped value and no extra properties.
 - Enums remain enums.
+- A concept that creates its own value implements `IGeneratable<TSelf>`; a
+  Guid-backed one uses `GenerateValue`, not `Guid.NewGuid()` or `Random`.
+  Client-supplied, secret or idempotent values are not generated.
 - Null absence uses a nullable concept reference rather than a null wrapped
   value.
 - Primitive-to-derived conversions and sentinels exist only when justified by

package/package/corpus/skills/cratis-fundamentals-concept/verification.json

@@ -3,6 +3,9 @@
   "input": "Create a strongly typed value for a domain concept.",
   "fixtures": [],
   "assertions": [
-    { "kind": "skill-contains", "value": "ConceptAs<T>" }
+    { "kind": "skill-contains", "value": "ConceptAs<T>" },
+    { "kind": "skill-contains", "value": "IGeneratable<TSelf>" },
+    { "kind": "skill-contains", "value": "GenerateValue.Uuid()" },
+    { "kind": "skill-contains", "value": "not** monotonic within a" }
   ]
 }

package/package/corpus/skills/cratis-screenplay-model-authoring/references/screen-authoring-workflow.md

@@ -121,13 +121,12 @@ not to the AI corpus. Link to the fixture path and run its published checks; do
 copy those `.play` files into `.cratis/ai/` or into a skill reference as a
 maintained duplicate.
 
-Round-5 vector and executable checks (2026-10-09):
+Verified public vector and executable checks:
 
-- final public vector: Scene 4.12.0, Screenplay 4.114.0 (final ABI release after #592), Stage
-  4.49.5, Docker `cratis/stage:4.49.5`, CLI 3.40.3 and Studio 0.136.4; public
-  NuGet flat-container visibility was verified for `Cratis.Screenplay` and
-  `Cratis.Screenplay.CanonicalCorpus` 4.114.0, while CLI 3.40.3 still pins
-  Screenplay 4.105.0, so keep the package pairing visible;
+- toolchain: public CLI 3.40.7 (`af9f18e`), whose default runtime is
+  `cratis/stage:4.51.1` and which bundles Screenplay 4.114.0. Latest public
+  packages are Scene 4.14.0, Screenplay 4.122.0, Stage 4.51.3 and Studio 0.141;
+  claims made through `cratis` are 4.114.0 compiler claims;
 - fixture root: `Source/DotNET/Screenplay.CanonicalCorpus/Corpus/ScreenComposition/v1/source/folder`
   in the Screenplay repository;
 - Screenplay repo tool (available checkout): `dotnet run --project Source/DotNET/Tool
@@ -140,9 +139,15 @@ Round-5 vector and executable checks (2026-10-09):
   `apply`, real `apply` and `open-workspace` again. It uses a scratch copy,
   changes `application.play` with a comment-preservation probe, fails closed on a
   stale revision, applies with the matching revision and verifies the comment
-  remains on disk;
+  remains on disk. On CLI 3.40.7: 9 requests and 9 responses, 37 tools,
+  `executableReady true`, stale apply `StaleRevision`, comment preserved;
 - render (`cratis render <corpus-folder> --name ScreenComposition --destination
-  <dir> -o json`) with packaged CLI 3.40.3 publishes the corpus.
+  <dir> -o json`) with CLI 3.40.7 publishes the corpus, and its browser
+  acceptance run passes 51 assertions (Cratis/Screenplay#605);
+- still refused by design: guarded Close (`STAGE-SCENE-ACTION-001`) and
+  double-click (`STAGE-SCENE-INTERACTION-001`); still pending: UI-profile
+  rejection and render-then-recover (Cratis/cli#301) and Studio production Play
+  proof (test-account decision).
 
 Report a corpus the released compiler, MCP server or renderer refuses as a
 capability/version-pairing gap with the exact diagnostics; never soften it to a

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

@@ -25,14 +25,15 @@ Version pins live once in `cratis-screenplay-toolchain` `references/versions.md`
 
 | Source | Pin | Used for |
 | --- | --- | --- |
-| cratis CLI | `3.40.3` (public package/tag #295) | `cratis render` options, exit codes, publication receipt; tag pins Stage 4.49.5 and Screenplay 4.105.0, with `cratis/stage:4.49.5` as the runtime image. Reading baselines: 3.40.2, 3.39.0 and 3.28.3 (`8b43fef`) |
-| Stage | `4.49.5` | admission (`STAGE-ESM-*`, and `PLAY0268` render refusals surfaced by the CLI), ownership manifest, `Customizations/` seams, Debug-only specifications, generated query specs, guarded-action safety and frontend form stability. Older baselines: 4.49.2, 4.49.1, 4.43.0 and `v4.24.2` (`32dcac4`) |
-| Screenplay | `4.114.0` final ABI release | standalone compiler for V1 to V3; binding codes `PLAY0268` and the code-attachment rules, read at `v4.66.0`; CLI 3.40.3 still bundles 4.105.0, so rerun if a later CLI consumes 4.114.0 |
-| Rendered apps | Arc `22.25.0`, Chronicle `19.8.1`, Scene packages | `[ProtectedDecision]` (Arc 22.39.0 and later) is not available in code written into one; verify the generated package set before claiming exact Scene 4.12.0 runtime parity |
+| cratis CLI | `3.40.7` (`v3.40.7`, `af9f18e`) | `cratis render` options, exit codes, publication receipt; tag pins Stage 4.51.1 and Screenplay 4.114.0, with `cratis/stage:4.51.1` as the runtime image. UI-profile rejection and render-then-recover fixes are pending in Cratis/cli#301. Reading baselines: 3.40.3, 3.39.0 and 3.28.3 (`8b43fef`) |
+| Stage | `4.51.1` (CLI default; latest package 4.51.3) | admission (`STAGE-ESM-*`, and `PLAY0268` render refusals surfaced by the CLI), ownership manifest, `Customizations/` seams, Debug-only specifications, fail-closed guarded actions (`STAGE-SCENE-ACTION-001`) and interactions (`STAGE-SCENE-INTERACTION-001`). Older baselines: 4.49.5, 4.43.0 and `v4.24.2` (`32dcac4`) |
+| Screenplay | bundled `4.114.0`; latest language package `4.122.0` | standalone compiler for V1 to V3; binding codes `PLAY0268` and the code-attachment rules, read at `v4.66.0`; claims made through `cratis` are 4.114.0 claims |
+| Rendered apps | Arc `22.25.0`, Chronicle `19.8.1`, Scene packages | `[ProtectedDecision]` (Arc 22.39.0 and later) is not available in code written into one; verify the generated package set before claiming exact Scene 4.14.0 runtime parity |
 
 Facts were read at those tags and `cratis render` was run at 3.28.2 and 3.28.3 for the worked example
-(`references/worked-example.md`); with packaged CLI 3.40.3 it was run over the canonical
-`ScreenComposition` corpus and published successfully. The AI repository's `screenplay-mcp-transcript.ts`
+(`references/worked-example.md`); with public CLI 3.40.7 it was run over the canonical
+`ScreenComposition` corpus and published successfully, and its browser acceptance run passed 51
+assertions (Cratis/Screenplay#605). The AI repository's `screenplay-mcp-transcript.ts`
 harness proves the real stdio proposal/apply path against the packaged CLI. The renderer facts are owned by `cratis-stage-rendering-and-sandbox`;
 this skill links them and never restates the admission table.
 

package/package/corpus/skills/cratis-screenplay-toolchain/SKILL.md

@@ -25,9 +25,9 @@ When choosing or upgrading a tool, or checking version-specific capabilities, re
 | Package | Version | Purpose |
 | --- | --- | --- |
 | `Cratis.Screenplay.Tool` | `4.68.0` (`79801bf`) | standalone compiler, binder and MCP server; admits ESM v7 (generated values and responses) |
-| cratis CLI | `3.40.3` public package/tag #295 | Tag pins Stage 4.49.5 and Screenplay 4.105.0, with `cratis/stage:4.49.5` as the runtime image. The packaged CLI executed render publication and the real stdio MCP transcript harness. Reading baselines: 3.40.2, 3.39.0 and 3.28.3 (`8b43fef`) |
-| Screenplay | `4.114.0` final ABI release | Exact public Screenplay release after #592. CLI 3.40.3 still bundles 4.105.0 and reports `sourceSuccess true`, `semanticSuccess true`, `executableReady true`; the repo tool compiles the corpus with `10 file(s) compiled - 0 error(s), 0 warning(s)`. Rerun if a later CLI consumes 4.114.0 |
-| Stage | `4.49.5` | Docker image `cratis/stage:4.49.5`; includes the 4.49.x generated query spec, guarded-action safety and frontend form-stability line. Packaged CLI 3.40.3 renders the canonical screen corpus and publishes Scene output with Arc `CommandForm` shells plus query bindings. Check generated package sets before claiming exact Scene 4.12 runtime parity |
+| cratis CLI | `3.40.7` (`v3.40.7`, `af9f18e`) | Tag pins Stage 4.51.1 and Screenplay 4.114.0, with `cratis/stage:4.51.1` as the runtime image. The public CLI executed render publication, the browser acceptance run and the real stdio MCP transcript harness (37 tools, `executableReady true`). Reading baselines: 3.40.3, 3.39.0 and 3.28.3 (`8b43fef`) |
+| Screenplay | bundled `4.114.0`; latest language package `4.122.0` | CLI 3.40.7 bundles 4.114.0 and reports `sourceSuccess true`, `semanticSuccess true`, `executableReady true` for the canonical corpus; the repo tool compiles it with `10 file(s) compiled - 0 error(s), 0 warning(s)`. Language features newer than 4.114.0 need the standalone 4.122.0 tool until a CLI bundles them |
+| Stage | `4.51.1` (CLI default; latest package 4.51.3) | Docker image `cratis/stage:4.51.1`; renders the canonical screen corpus with Arc `CommandForm` shells and query bindings, and refuses guarded Close and double-click with `STAGE-SCENE-ACTION-001` / `STAGE-SCENE-INTERACTION-001`. Check generated package sets before claiming exact Scene 4.14 runtime parity |
 | Arc / Chronicle | `22.50.5` / `19.32.0` | code-level facts cited here |
 
 Facts were read with `git show <tag>:<path>` and probed on the installed tools. Behaviour

package/package/corpus/skills/cratis-screenplay-ui-composition/SKILL.md

@@ -225,10 +225,9 @@ same typed navigate binding a screen action uses.
 ⚠️ The v4.31.0 baseline, re-verified at v4.66.0, ships `navigate`, `label` and `order` only. Grouping beyond a
 flat ordered list, and an explicit override for when nearest-enclosing is not the
 point you mean, are deliberately left for later. The screens-release vector
-(Screenplay 4.105.0, canonical `ScreenComposition` corpus v1) adds typed screen
-composition; CLI 3.40.0 renders it through Stage 4.49.1. Report a refused form as
-a capability gap, never a flat-list fallback, and keep browser/Studio production
-proof separate from render publication.
+(canonical `ScreenComposition` corpus v1) adds typed screen composition; public
+CLI 3.40.7 renders it and passes the browser run. Report a refused form as a
+capability gap, never a flat-list fallback; Studio production proof is separate.
 
 ## Interactions — what a click does
 

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

@@ -31,20 +31,27 @@ 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. Round-5 target vector:
-Scene 4.12.0, Screenplay 4.114.0 (final ABI release after #592), Stage 4.49.5, Docker
-`cratis/stage:4.49.5`, CLI 3.40.3 and Studio 0.136.4. Executed packaged-CLI
-protocol proof: the canonical `ScreenComposition` corpus opens with `sourceSuccess true`,
-`semanticSuccess true`, `executableReady true`; the stdio MCP harness sends real
-proposal/apply requests, rejects a stale revision and preserves an authored
-comment on disk. Render publication is verified on the available CLI checkout;
-the CLI 3.40.3 package still pins Screenplay 4.105.0, so rerun if a later CLI
-package consumes Screenplay 4.114.0. Runtime/browser
-behavior, Studio Play and production deploy are separate checks; Studio 0.136.4
-production deploy proof remains pending because Pulumi lock recovery cleared but
-deploy failed on Core CrashLoopBackOff. On Stage
-4.24.2 or cratis 3.28.x renderers, authored screens are still reported as
-omitted/default composition.
+the package/version you are using proves the new level. Verified public vector:
+CLI 3.40.7 with its default `cratis/stage:4.51.1` and bundled Screenplay 4.114.0;
+latest public packages are Scene 4.14.0, Screenplay 4.122.0, Stage 4.51.3 and
+Studio 0.141. All three levels hold for the canonical `ScreenComposition` corpus
+on that CLI:
+
+- authoring and executable admission: MCP opens it with `sourceSuccess true`,
+  `semanticSuccess true`, `executableReady true`, and the stdio MCP harness sends
+  real proposal/apply requests, rejects a stale revision and preserves an
+  authored comment on disk;
+- runtime: render publishes, and the browser acceptance run passes 51
+  assertions with none blocked or pending (Cratis/Screenplay#605) - native
+  command forms, required fields, scoped comments, deep links, stale-response
+  handling and theme included.
+
+Still true on that vector: a guarded Close action and a double-click interaction
+are refused (`STAGE-SCENE-ACTION-001`, `STAGE-SCENE-INTERACTION-001`) and recorded
+as unsupported, never emulated; refusing an unresolvable UI profile and recovering
+a rendered application are pending in Cratis/cli#301; Studio production Play
+proof is pending a test-account decision. On Stage 4.24.2 or cratis 3.28.x
+renderers, authored screens are still reported as omitted/default composition.
 
 ## Data context and component bindings
 

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

@@ -1,6 +1,6 @@
 ---
 name: cratis-stage-rendering-and-sandbox
-description: "What Cratis Stage and `cratis render` actually do with a Screenplay `.play` model today: the narrow model shape Stage 4.49.5 admits and refuses (`STAGE-ESM-*`, `PLAY0268` render refusals), what it emits (C# Arc/Chronicle backend, React/Vite scaffold with Arc `CommandForm` shell emission over Scene 4.12 typed bindings, Debug specifications), managed publication, `--force` and recovery, authored-UI omission/parity checks, the unmanaged `Customizations/` seam, and the `cratis/stage` sandbox and `cratis/stage-specrunner` job. Use when deciding whether Stage can render a model, reading a blocked render, re-rendering safely, checking generated/runtime screen parity, or running the sandbox. Not for: authoring the model (use `cratis-screenplay-model-authoring`) or the render and gap-fill workflow (use `cratis-screenplay-render-and-gap-fill`)."
+description: "What Cratis Stage and `cratis render` actually do with a Screenplay `.play` model today: the narrow model shape Stage 4.51 admits and refuses (`STAGE-ESM-*`, `PLAY0268` render refusals), what it emits (C# Arc/Chronicle backend, React/Vite scaffold with Arc `CommandForm` shell emission over Scene 4.12 typed bindings, Debug specifications), managed publication, `--force` and recovery, authored-UI omission/parity checks, the unmanaged `Customizations/` seam, and the `cratis/stage` sandbox and `cratis/stage-specrunner` job. Use when deciding whether Stage can render a model, reading a blocked render, re-rendering safely, checking generated/runtime screen parity, or running the sandbox. Not for: authoring the model (use `cratis-screenplay-model-authoring`) or the render and gap-fill workflow (use `cratis-screenplay-render-and-gap-fill`)."
 license: MIT
 ---
 
@@ -18,14 +18,16 @@ reading in this skill is not a render result.
 
 Authored UI has its own parity hazard. Stage 4.24 rendered a default React/Vite
 scaffold and did not prove that modeled screens, templates, forms, toolbars,
-components, outlets, package icons or routes were implemented. The final public
-vector is Stage 4.49.5, Screenplay 4.114.0 (the final ABI release), Scene 4.12.0,
-CLI 3.40.3 and Studio 0.136.4; the sandbox image is `cratis/stage:4.49.5`.
-The packaged CLI 3.40.3 render/MCP transcript publishes the canonical corpus, but
-its tag still pins Screenplay 4.105.0, so keep the CLI/Screenplay pairing visible
-when claiming exact compiler coverage. Runtime/browser parity is still a
-separate claim: require a generated plan or artifact entry for every authored UI
-construct, and report every unsupported UI directive as a diagnostic.
+components, outlets, package icons or routes were implemented. The first fully
+passing public browser vector is CLI 3.40.7 with its default `cratis/stage:4.51.1`
+and bundled Screenplay 4.114.0: 51 browser assertions passed, none blocked or
+pending (recorded in Cratis/Screenplay#605). Native command forms, required
+fields, scoped comments, deep links, stale-response handling and theme all pass
+there. Two behaviors stay fail-closed by design: a guarded Close action
+(`STAGE-SCENE-ACTION-001`) and a double-click interaction
+(`STAGE-SCENE-INTERACTION-001`) are refused and recorded as unsupported
+capabilities, never emulated. Require a generated plan or artifact entry for every
+authored UI construct, and report every unsupported UI directive as a diagnostic.
 Silent fallback to a default screen is a failure, not a partial render.
 
 ## Specification runner exit codes
@@ -39,10 +41,10 @@ argument or an invalid semantic option.
 
 | Source | Pin | Notes |
 | --- | --- | --- |
-| Stage | `4.49.5` (`v4.49.5`) | Renderer, sandbox host, spec runner; includes the 4.49.x generated query specs, guarded-action safety and frontend form-stability fixes. The Docker image is `cratis/stage:4.49.5`. Earlier executed baselines: 4.49.2, 4.49.1, 4.43.0 and `v4.24.2` (`32dcac4`) |
-| cratis CLI | `3.40.3` (`v3.40.3`, PR #295) | `cratis render`, `cratis run`; public packaged CLI 3.40.3 renders the canonical corpus and runs the stdio MCP transcript. Its tag pins Stage 4.49.5 and Screenplay 4.105.0, so mention that pairing until a CLI package consumes Screenplay 4.114.0. Older baseline: `v3.28.2` (`141c499`, Cratis/cli#253) |
-| Screenplay | `4.114.0` (`v4.114.0`, final ABI release after #592) | Standalone Screenplay final release after #592. The canonical screen corpus and MCP transcript were rerun through packaged CLI 3.40.3, which still bundles Screenplay 4.105.0; rerun if a CLI package moves to 4.114.0 |
-| Rendered applications | Arc, Chronicle, Scene 4.12.0, .NET 10 | Stage 4.49.5 / CLI 3.40.3 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 |
+| Stage | `4.51.1` (`v4.51.1`, `0fe4a63`) as the CLI default; latest public package `4.51.3` (`e7dc0a0`) | Renderer, sandbox host, spec runner; the CLI 3.40.7 default image is `cratis/stage:4.51.1`. Defines `STAGE-SCENE-ACTION-001` and `STAGE-SCENE-INTERACTION-001`. Earlier executed baselines: 4.49.5, 4.43.0 and `v4.24.2` (`32dcac4`) |
+| cratis CLI | `3.40.7` (`v3.40.7`, `af9f18e`) | `cratis render`, `cratis run`; the tag pins `StageVersion` 4.51.1 and `ScreenplayVersion` 4.114.0. The public CLI renders the canonical corpus and runs the stdio MCP transcript. Unresolvable UI-profile rejection and render-then-recover fixes are pending in Cratis/cli#301. Older baseline: `v3.28.2` (`141c499`, Cratis/cli#253) |
+| Screenplay | bundled `4.114.0`; latest public language package `4.122.0` | The CLI bundles 4.114.0, so compiler claims made through `cratis` are 4.114.0 claims; use the standalone 4.122.0 tool only for language features newer than the bundle |
+| Rendered applications | Arc, Chronicle, Scene 4.14.0, .NET 10 | CLI 3.40.7 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`,
 `Documentation/**` in Stage; `Source/Cli/Commands/Render/**` and
@@ -51,10 +53,11 @@ Everything below was read at those tags (`Source/Rendering.Cratis/**`, `README.m
 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`. Rendered apps are on Arc `22.25.0`, so `[ProtectedDecision]`
-(Arc 22.39.0 and later) is not available in code written into one. Screen UI render publication for the canonical corpus is verified on packaged
-CLI 3.40.3 / Stage 4.49.5. Browser runtime behavior, Studio Play and production
-deploy remain separate checks; Studio 0.136.4 production deploy proof is pending
-because Pulumi lock recovery cleared but deploy failed on Core CrashLoopBackOff.
+(Arc 22.39.0 and later) is not available in code written into one. Screen render
+publication and browser behavior for the canonical corpus are verified on public
+CLI 3.40.7 / `cratis/stage:4.51.1`. Studio 0.141 is released and production runs
+v0.139.0 or later, but production UI automation is pending a
+test-account decision, so Studio production Play proof is not claimed.
 
 ## Model-first rule
 
@@ -185,10 +188,10 @@ read models `when_<snake>_is_projected`.
 
 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 packaged CLI 3.40.3 / Stage 4.49.5 the canonical corpus publishes and
-`scene.json` contains Arc `commandForm` components while `src/bindings.ts`
-registers the modeled commands and queries. That is render-output evidence, not
-browser or Studio production proof. Require an explicit plan, manifest entry or
+On public CLI 3.40.7 / `cratis/stage:4.51.1` the canonical corpus publishes,
+`scene.json` contains Arc `commandForm` components, `src/bindings.ts` registers
+the modeled commands and queries, and the browser acceptance run passes. That is
+not Studio production proof. Require an explicit plan, manifest entry or
 generated artifact for each
 screen/template/form/toolbar/component/outlet/route/package-icon use, or a
 blocking diagnostic explaining why it was not generated.

package/package.json

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