@cratis/pi 7.36.0 → 7.36.1

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

@@ -168,10 +168,12 @@ Historical verified public vector and executable checks:
 - render (`cratis render <corpus-folder> --name ScreenComposition --destination
   <dir> -o json`) with CLI 3.43.0 publishes the corpus; the browser acceptance
   run on CLI 3.40.7 passed 51 assertions (Cratis/Screenplay#605);
-- still refused by design: guarded Close (`STAGE-SCENE-ACTION-001`) and
-  double-click (`STAGE-SCENE-INTERACTION-001`); still pending: Studio production
-  Play proof (test-account decision). UI-profile rejection and render-then-recover
-  shipped in Cratis/cli#301.
+- guarded Close and double-click: refused with `STAGE-SCENE-ACTION-001` and
+  `STAGE-SCENE-INTERACTION-001` on this historical vector, rendered and run since
+  Stage 4.65 (live browser run on CLI 3.53.1 with `cratis/stage:4.73.1`,
+  Cratis/Screenplay#671); the codes remain for a guard Stage cannot evaluate. Studio
+  production Play proof is a separate vector (Cratis/Screenplay#173). UI-profile
+  rejection and render-then-recover shipped in Cratis/cli#301.
 
 ## Replay the workflow in CI without a Screenplay checkout
 

package/package/corpus/skills/cratis-screenplay-read-surface/references/guarded-actions.md

@@ -77,7 +77,9 @@ second command. Screens remain outside portable ESM execution. A downstream
 renderer must explicitly admit guarded selection or report unsupported behavior,
 not approximate it as a plain action. Checked at historical CLI 3.41.0: its bundled
 screen renderer reported unsupported guarded actions with STAGE-SCENE-ACTION-001; source compilation alone
-cannot establish usable controls.
+cannot establish usable controls. Since Stage 4.65 a guard comparing `item.<field>` with a literal is
+rendered and evaluated at runtime (public CLI 3.53.1 with `cratis/stage:4.73.1`, Cratis/Screenplay#671);
+STAGE-SCENE-ACTION-001 remains for a guard Stage cannot evaluate.
 
 Authority: Screenplay `v4.125.0:Documentation/screenplay/screens.md`;
 CLI `v3.41.0:Documentation/reference/screenplay.md` for renderer disposition.

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

@@ -35,8 +35,9 @@ Runs: the worked example (`references/worked-example.md`) was probed with cratis
 corpus was rendered and published successfully, and an MCP-edited copy was rendered, run and checked in
 the browser; the CLI 3.40.7 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. Guarded Close actions (`STAGE-SCENE-ACTION-001`) and double-click interactions
-(`STAGE-SCENE-INTERACTION-001`) are refused and recorded as unsupported, never emulated. UI-profile
+packaged CLI. Guarded Close actions and double-click interactions were refused (`STAGE-SCENE-ACTION-001`,
+`STAGE-SCENE-INTERACTION-001`) on that vector; since Stage 4.65 they render and run, and the codes
+remain for a guard Stage cannot evaluate, which is never emulated (Cratis/Screenplay#671). UI-profile
 rejection (`CLI-RENDER-007` to `-010`) and render-then-recover shipped in 3.41.0 (Cratis/cli#301). 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-ui-composition/references/screen-composition-contract.md

@@ -54,10 +54,11 @@ All three levels hold for the canonical `ScreenComposition` corpus on the histor
   comments, deep links, stale-response handling and theme included. On CLI
   3.43.0 an agent-edited column was rendered, run and seen in the browser.
 
-Still true: a guarded Close action and a double-click interaction are refused
-(`STAGE-SCENE-ACTION-001`, `STAGE-SCENE-INTERACTION-001`, defined from Stage
-4.51 through 4.57) and recorded as unsupported, never emulated; Studio production
-Play proof is pending a test-account decision. Refusing an unresolvable UI
+Guarded Close and double-click: Stage refused both with `STAGE-SCENE-ACTION-001` and
+`STAGE-SCENE-INTERACTION-001` from Stage 4.51 through 4.57. Since Stage 4.65 they render and
+run (public CLI 3.53.1 with `cratis/stage:4.73.1`, Cratis/Screenplay#671); the codes remain the
+refusal for a guard Stage cannot evaluate, which is never emulated. Studio production Play
+proof is a separate vector (Cratis/Screenplay#173). Refusing an unresolvable UI
 profile and recovering a rendered application shipped in Cratis/cli#301. (History: on Stage 4.24.2 or
 cratis 3.28.x renderers authored screens were reported as omitted/default composition; Stage 4.73.1
 (CLI 3.53.1) renders navigation contributions and toolbars, and `CLI-RENDER-015`, which refused them, is retired.)
@@ -124,7 +125,8 @@ 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`. Historical CLI 3.41.0/Stage 4.51.3 checks reported
-unsupported screen actions with STAGE-SCENE-ACTION-001, not proof of runtime selection.
+unsupported screen actions with STAGE-SCENE-ACTION-001; since Stage 4.65 a guard of the form
+`item.<field>` compared with a literal is evaluated at runtime (Cratis/Screenplay#671).
 
 ## Exposed template configuration
 

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

@@ -24,10 +24,10 @@ browser assertions passed, none blocked or pending (Cratis/Screenplay#605).
 Native command forms, required fields, scoped comments, deep links,
 stale-response handling and theme all pass there. On public CLI 3.43.0 (default
 `cratis/stage:4.52.0`) an agent-edited table column was rendered, run and seen in
-the browser. 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
+the browser. Guarded Close and guarded double-click run since
+Stage 4.65: on CLI 3.53.1 with `cratis/stage:4.73.1` Close shows only while the item is
+open and a double click navigates or notifies by row (Cratis/Screenplay#671). `STAGE-SCENE-ACTION-001` and `STAGE-SCENE-INTERACTION-001` still
+refuse a guard Stage cannot evaluate: no artifacts. 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.
 

package/package.json

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