@cratis/pi 7.24.0 → 7.26.0

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

@@ -0,0 +1 @@
+4.127.0

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

@@ -25,6 +25,8 @@ probe; older probes retain their original labels in the other references.
 | 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 |
 
+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.
+
 Check the actual executable before relying on this table: `screenplay --version`,
 `cratis --version`, MCP `initialize` → `serverInfo.version`. An older executable
 on PATH can shadow a newer install; inspect `which -a cratis`.

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

@@ -3,6 +3,7 @@
   "input": "Check a Screenplay model folder: which compiler should I run, what do V1 to V3 mean, and what does the cratis CLI do with my Automation slice?",
   "fixtures": [],
   "assertions": [
+    { "kind": "play-compiles" },
     { "kind": "skill-contains", "value": "4.127.0" },
     { "kind": "skill-contains", "value": "PLAY0653", "file": "references/diagnostics.md" },
     { "kind": "skill-contains", "value": "PLAY0646", "file": "references/diagnostics.md" },

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

@@ -74,11 +74,11 @@ work on a screen whose purpose is unsettled is rework.
 2. **Review the flow before adding layout.** Walk it screen by screen as text
    (format in `references/flow-review.md`). When the host advertises the MCP-Apps
    extension for the `screenplay` MCP server, `visualize-model` (a `proposalId` or a `sketch`) can also show it on
-   a board; that is optional, and the text review is enough on its own. Do not
+   a board; that is optional, and the text review is enough. Do not
    use the Stage sandbox as the review: it renders only part of a screen, and
    nothing here establishes that Stage renders an authored screen faithfully.
 3. **Add structure only to screens whose Level 1 is agreed**: template, sections,
-   forms, `on`/`uses`. Use Level 3 inline code last, and only where Level 2 cannot
+   forms, `on`/`uses`. Use Level 3 inline code last, only where Level 2 cannot
    say it.
 4. **Trace every field.** Each `form` `field` is a property of the form's command.
    A prefilled value comes from `populate` or `from`; a derived one from
@@ -132,7 +132,7 @@ or `regular` — phone landscape, phone portrait, desktop short, desktop tall.
 **`arrangement freeform`** declares one variant per matrix point. Excerpt, inside
 the `layout` above in place of its `arrangement flow`:
 
-```screenplay
+```screenplay excerpt
 arrangement freeform
   variant width regular, height regular
     place navigation at 0,0 size 240,fill
@@ -149,7 +149,7 @@ arrangement freeform
 
 Declared at module level, referenced by screens. Excerpt, inside a `module`:
 
-```screenplay
+```screenplay excerpt
 screen template MasterDetail
   fits slot content
   sidebar
@@ -178,7 +178,7 @@ difference. See `cratis-screenplay-read-surface` for the directives that go insi
 Excerpt, inside a `module`; the command, query and screen are declared in its
 slices.
 
-```screenplay
+```screenplay excerpt
 form RegisterInvoiceForm for RegisterInvoice
   populate via query GetInvoiceDefaults by customerId
   field invoiceNumber label "Invoice #"
@@ -204,7 +204,7 @@ level, so it disambiguates by module rather than by feature or slice.
 Excerpt, inside a `module` or `feature`; `Navigation` is the contribution point
 the layout above declares.
 
-```screenplay
+```screenplay excerpt
 contribute to Navigation
   navigate to InvoiceList
   label "Invoices"
@@ -315,7 +315,7 @@ An existing success continuation does not imply a response contract.
 
 Excerpt: `AppShell` is the layout above.
 
-```screenplay
+```screenplay excerpt
 ui profile Desktop
   target platform web
   target size regular

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/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`" },

package/package.json

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