@cratis/pi 7.23.0 → 7.25.0

package/package/corpus/skills/cratis-screenplay-ui-composition/references/guarded-interactions.md

@@ -0,0 +1,71 @@
+<!-- Copyright (c) Cratis. All rights reserved. -->
+<!-- Licensed under the MIT license. See LICENSE file in the project root for full license information. -->
+
+# Choose a gesture's whole action list
+
+`on click`, `on double click` and `on select` accept ordered block-form `when`
+alternatives and an optional final `otherwise`. Use the same strict condition
+language and data-item subject as [guarded screen actions](../../cratis-screenplay-read-surface/references/guarded-actions.md):
+`item.<path>` compared with a literal, joined by `and`, `or` and parentheses.
+At least one `when` and a nonempty action list in every branch are required.
+Do not mix alternatives with plain actions or `where`; a one-line
+`when … execute …` belongs to labeled actions, not interactions.
+
+This complete model validates on standalone Screenplay 4.127.0:
+
+```screenplay
+module Billing
+  feature Invoices
+    slice StateView InvoiceHistory
+      event InvoiceRecorded
+        status String
+      readmodel InvoiceView
+        invoiceId String
+        status String
+      projection Invoices => InvoiceView
+        from InvoiceRecorded
+          invoiceId = $eventSourceId
+          status = status
+      query InvoiceById => InvoiceView optional
+        by invoiceId String
+      screen InvoiceDetails
+        data InvoiceView via query InvoiceById by invoiceId
+        table InvoiceView
+          column status
+          on double click
+            when item.status == "draft"
+              notify info "The draft can be edited"
+              refresh InvoiceById
+            otherwise
+              notify info "Only drafts can be edited"
+```
+
+The first matching branch runs once on the rendered item at gesture time, without
+refetch or re-evaluation while its list runs. No match uses fallback or does
+nothing; **no subject does nothing, including fallback**. Failure, denial or an
+unavailable command never falls through; backend commands retain their rules.
+Unlike labeled actions, no choice was displayed beforehand to refresh at click.
+
+A table click/double click uses the activated row; select uses the newly selected
+item, and clearing selection runs nothing. Elsewhere use the nearest enclosing
+single item or selected row, with guarded actions' sibling precedence. Check named
+behaviors at each `uses` site. Component `context` or `selectedItem` bindings do
+not supply the subject in this version; unresolved/equally near subjects report
+PLAY0346.
+
+Submit, event, change, interval and application triggers have no alternatives.
+The one-line `on row-click navigate to … by …` remains unchanged. Opaque `where`
+on click/double click/select is deprecated (PLAY0564): strict item conditions warn
+and C# offers a typed repair to one `when` with no fallback; other guard text is
+Information without repair. Other triggers' `where` remains unchanged. Repairs
+require individual review, canonical formatting, preserve comments and refuse
+comment loss; TypeScript diagnoses but offers no repair. PLAY0563 has a C# repair
+expanding a one-line alternative to the block form. Neither repair supports
+pinned evidence.
+
+UI is deferred from backend ESM (PLAY0269), not executable gesture proof. The
+board draws a static prototype; renderers must explicitly admit alternatives or
+report unsupported, never flatten them into plain actions.
+
+Authority: Screenplay v4.127.0 `interactions.md`, `diagnostics.md`,
+`mcp/authoring-tools.md`; decision 0048.

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

@@ -59,7 +59,7 @@ renderers, authored screens are still reported as omitted/default composition.
 A component instance is a presentation of a typed Screenplay data context. The
 proposed syntax is:
 
-```screenplay
+```screenplay excerpt
 component <Package.Component> <instanceName>
   context <binding>
   property <property.path> from <binding>
@@ -115,7 +115,7 @@ screen actions with STAGE-SCENE-ACTION-001, not proof of runtime selection.
 
 Reusable templates can expose configuration and typed outlets:
 
-```screenplay
+```screenplay excerpt
 screen template MasterDetail
   category workflow
   type master-detail
@@ -148,14 +148,14 @@ installed parser/printer supports the scoped `template` directive before using i
 A form remains bound to exactly one command. The screens-release additions make
 its generated fields explicit when the automatic shape is not enough:
 
-```screenplay
+```screenplay excerpt
 form RegisterInvoiceForm for RegisterInvoice
   columns auto
 ```
 
 or:
 
-```screenplay
+```screenplay excerpt
 form RegisterInvoiceForm for RegisterInvoice
   columns manual
     column invoiceNumber label "Invoice #"
@@ -171,7 +171,7 @@ field.
 
 `ui profile` owns package priority and icon sets:
 
-```screenplay
+```screenplay excerpt
 ui profile Desktop
   target platform web
   layout AppShell
@@ -194,7 +194,7 @@ ui profile Desktop
 Navigation and toolbar items target the same typed destination contract: screen,
 named outlet, optional route parameters, and optionally a dialog.
 
-```screenplay
+```screenplay excerpt
 toolbar InvoiceToolbar
   item register action RegisterInvoice
     label "Register"

package/package/corpus/skills/cratis-screenplay-ui-composition/verification.json

@@ -3,6 +3,7 @@
   "input": "Declare the application shell, a screen template and a command form.",
   "fixtures": [],
   "assertions": [
+    { "kind": "play-compiles" },
     {
       "kind": "skill-contains",
       "value": "main `fd18129`"

package/package/corpus/skills/cratis-specification-by-example/verification.json

@@ -0,0 +1,14 @@
+{
+  "skill": "cratis-specification-by-example",
+  "input": "Organize and name the specifications for a new behavior.",
+  "fixtures": [],
+  "assertions": [
+    {
+      "kind": "play-compiles"
+    },
+    {
+      "kind": "skill-contains",
+      "value": "for_"
+    }
+  ]
+}

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

@@ -52,8 +52,11 @@ Everything below was read at those tags (`Source/Rendering.Cratis/**`, `README.m
 [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`. 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 render
+`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
+[rendered application](references/rendered-application.md) for the source checks. 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

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

@@ -7,18 +7,29 @@ render (see [render-example.md](render-example.md)).
 
 ## Scaffold pins
 
+The pin rows below are source-checked at Stage `v4.51.3`,
+`Source/Rendering.Cratis/Scaffolding/CratisBackendApplicationScaffoldProfile.cs`,
+`CratisBackendApplicationScaffold.cs` and `CratisFrontendPackageSet.cs`.
+Earlier runtime/customization probes above keep their original labels.
+
 | Item | Value |
 | --- | --- |
 | Target framework | .NET 10 (`net10.0`), `Microsoft.NET.Sdk.Web` |
-| Arc packages (`Cratis`, `Cratis.Arc.MongoDB`, Arc testing) | `22.25.0` |
-| Chronicle client | `Cratis.Chronicle` and `.AspNetCore` `19.8.1`, matched to the `cratis/chronicle:19.8.1-development` image in the compose file |
+| Arc packages (`Cratis`, `Cratis.Arc.MongoDB`, Arc testing) | `22.50.5` |
+| Chronicle client | `Cratis.Chronicle`, `.AspNetCore` and `.Testing` `19.32.0`, matched to the `cratis/chronicle:19.32.0-development` image in the compose file |
+| Embedded reverse extraction | `CratisEmbeddedScreenplayEnabled=false`: the source `.play` is authoritative |
 | Test packages | xunit, NSubstitute, Cratis.Specifications; **Debug configuration only** (`IsTestProject` when Debug) |
-| Frontend | Vite and React, Components `4.14.0`, Scene `4.2.0`, Fundamentals `7.19.6` |
+| Frontend | Vite and React, Components `4.14.0`, Scene `4.10.0`, Fundamentals `7.19.8` |
 | Package management | central package management **off**; `Directory.Packages.props` is managed, do not edit it |
 
-Consequences: `[ProtectedDecision]` and `DecisionRead<T>` (Arc 22.39.0 and later) are not
-available in a rendered application; `[ExecuteCommandsAsSystem]` (Arc 20.56.0 and later)
-is. Upgrading Arc or Chronicle inside a rendered application is a re-render under a newer
+Consequences: `[ProtectedDecision]` (`Cratis.Arc.Chronicle.ReadModels`) and
+`DecisionRead<T>` / `IDecisionReads` (`Cratis.Chronicle.ReadModels`) are available
+in this scaffold's package set, as is `[ExecuteCommandsAsSystem]`. This is API
+availability, not Stage emission or runtime protection: gap-fill must opt into
+the protected command profile and enroll an admitted projection/key read in the
+active unit of work. Source-checked at Arc v22.50.5 `ProtectedDecisionAttribute.cs`
+and `CommandDecisionReads.cs`, Chronicle v19.32.0 `DecisionRead.cs`/`IDecisionReads.cs`.
+Stage does not turn `.play` `reads`/`require` into protected decisions. Upgrading Arc or Chronicle inside a rendered application is a re-render under a newer
 Stage, not an edit of the managed files. The compose file binds local ports `27017` and
 `35000`, keeps data in the named volumes `chronicle-data` and `chronicle-config`, and
 `docker compose down --volumes` is the only thing that deletes them.

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

@@ -3,6 +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": "play-compiles" },
     { "kind": "skill-contains", "value": "`cratis render`" },
     { "kind": "skill-contains", "value": "`--name <NAME>` | **Required for plain source**" },
     { "kind": "skill-contains", "value": "`.cratis-render.json`" },
@@ -10,7 +11,7 @@
     { "kind": "skill-contains", "value": "means stop and reconcile" },
     { "kind": "skill-contains", "value": "STAGE-ESM-016" },
     { "kind": "skill-contains", "value": "**Render never builds, tests or runs**" },
-    { "kind": "skill-contains", "value": "Arc `22.25.0`" },
+    { "kind": "skill-contains", "value": "Arc `22.50.5`" },
     { "kind": "skill-contains", "value": "`[ProtectedDecision]`" },
     { "kind": "skill-contains", "value": "`Customizations/`" },
     { "kind": "skill-contains", "value": "`Stage__Runtime__Engine=semantic`" },

package/package.json

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