@cratis/pi 7.15.1 → 7.17.0

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

@@ -121,27 +121,32 @@ 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.
 
-Verified screens-release vector (executed 2026-10-09 against the released
-checkout toolchain):
+Round-5 vector and executable checks (2026-10-09):
 
+- 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;
 - fixture root: `Source/DotNET/Screenplay.CanonicalCorpus/Corpus/ScreenComposition/v1/source/folder`
   in the Screenplay repository;
-- Screenplay repo tool (4.105.0 query-shapes era): `dotnet run --project
-  Source/DotNET/Tool -- <corpus-folder> --warnaserror` → exit `0`, `10 file(s)
-  compiled - 0 error(s), 0 warning(s)`;
-- MCP (`dotnet run --project cli/Source/Cli -- screenplay mcp <corpus-folder>`,
-  CLI 3.40.0 bundling Screenplay 4.105.0): `sourceSuccess true`, `semanticSuccess
-  true`, `executableReady true`, 10 documents; a scratch `propose-rename`
-  transcript proved revision/catalog checks but apply did not complete because
-  the target handle contract rejected the supplied target shape;
-- render (`dotnet run --project cli/Source/Cli -- render <corpus-folder> --name
-  ScreenComposition --destination <dir> -o json`, CLI 3.40.0 / Stage 4.49.1):
-  exit `0`, status `published`, `.cratis-render.json`, backend files, `.frontend`,
-  `scene.json` and `src/bindings.ts` written. The generated Scene includes Arc
-  `commandForm` components and query registrations.
-
-Report a corpus the released compiler or renderer refuses as a capability/version
-pairing gap with the exact diagnostics; never soften it to a pass.
+- Screenplay repo tool (available checkout): `dotnet run --project Source/DotNET/Tool
+  -- <corpus-folder> --warnaserror` → exit `0`, `10 file(s) compiled - 0 error(s),
+  0 warning(s)`;
+- stdio MCP protocol harness: the AI repository carries `screenplay-mcp-transcript.ts`;
+  run it with packaged `cratis` on `PATH`, `--corpus <corpus-folder>` and
+  `--scratch <scratch-folder>`. It sends `initialize`, `tools/list`,
+  `open-workspace`, `read-workspace`, `propose-source`, `read-proposal`, stale
+  `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;
+- render (`cratis render <corpus-folder> --name ScreenComposition --destination
+  <dir> -o json`) with packaged CLI 3.40.3 publishes the corpus.
+
+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
+pass.
 
 When the fixture is not yet published, report the parity checks as blocked by the
 fixture contract and continue verifying the independently authored guidance and

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.0` (checkout `082df13`) | `cratis render` options, exit codes, publication receipt; `Directory.Packages.props` pins Stage 4.49.1 and bundled Screenplay 4.105.0, `cratis/stage:4.49.1` as the default run image. Reading baselines: 3.39.0 (Stage 4.43.0 / Screenplay 4.93.0) and 3.28.3 (`8b43fef`) |
-| Stage | `4.49.1` (worktree `f64c3da`) | admission (`STAGE-ESM-*`, and `PLAY0268` render refusals surfaced by the CLI), ownership manifest, `Customizations/` seams, Debug-only specifications, generated query specs and guarded-action safety. Reading baselines: 4.43.0 and `v4.24.2` (`32dcac4`) |
-| Screenplay | `4.105.0` query-shapes release | standalone compiler for V1 to V3; binding codes `PLAY0268` and the code-attachment rules, read at `v4.66.0`; CLI 3.40.0 bundles 4.105.0 and renders the canonical screen corpus |
-| 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 because the 4.49.1 corpus render observed Scene 4.10 packages even though the release vector names Scene 4.12.0 |
+| 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 |
 
 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`); at CLI 3.40.0 it was run over the canonical `ScreenComposition`
-corpus and published successfully. The renderer facts are owned by `cratis-stage-rendering-and-sandbox`;
+(`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`
+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.
 
 ## When to use / when not

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.0` (checkout `082df13`) | `Directory.Packages.props` pins `StageVersion` 4.49.1 and `ScreenplayVersion` 4.105.0; the `cratis run` container defaults to `cratis/stage` at the rendered Stage version (`cratis/stage:4.49.1`). Reading baselines: 3.39.0 with Stage 4.43.0 / Screenplay 4.93.0; 3.28.3 (`8b43fef`) with Screenplay 4.66.0 and Stage 4.24.2 |
-| Screenplay | `4.105.0` query-shapes release | admits the canonical `ScreenComposition` corpus v1 with zero authoring diagnostics (`dotnet run --project Source/DotNET/Tool -- <corpus> --warnaserror` → `10 file(s) compiled - 0 error(s), 0 warning(s)`); the CLI 3.40.0 MCP reports `executableReady true` for the same corpus |
-| Stage | `4.49.1` (worktree `f64c3da`) | renders the canonical screen corpus through CLI 3.40.0 and publishes Scene output with Arc `CommandForm` shells plus query bindings. The generated app observed locally still pins Scene 4.10 packages, so check the generated package set before claiming Scene 4.12 runtime parity. Reading baselines: 4.43.0 and 4.24.2 (`32dcac4`) |
+| 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 |
 | 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/references/screen-composition-contract.md

@@ -31,15 +31,20 @@ 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 against the
-screens-release vector (2026-10-09): Screenplay 4.105.0 accepts the canonical
-`ScreenComposition` corpus v1 with zero authoring diagnostics; CLI 3.40.0’s
-bundled Screenplay 4.105.0 reports `executableReady true`; `cratis render` with
-Stage 4.49.1 publishes Scene output with Arc `commandForm` shells and query
-registrations. Runtime/browser behavior, Studio Play and production deploy are
-separate checks; Studio 0.136.3 production deploy proof remains pending behind the
-stale Pulumi lock. 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. 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.
 
 ## 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.1 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.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`)."
 license: MIT
 ---
 
@@ -18,10 +18,12 @@ 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. Stage 4.49.1 (via
-CLI 3.40.0, bundling Screenplay 4.105.0) renders the canonical screen corpus and
-publishes Scene 4.12 output with Arc `CommandForm` shells and query bindings;
-the sandbox image is `cratis/stage:4.49.1`. Runtime/browser parity is still a
+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.
 Silent fallback to a default screen is a failure, not a partial render.
@@ -37,10 +39,10 @@ argument or an invalid semantic option.
 
 | Source | Pin | Notes |
 | --- | --- | --- |
-| Stage | `4.49.1` (worktree `f64c3da`) | Renderer, sandbox host, spec runner; Stage 4.49.0 generated query specs and 4.49.1 adds the guarded-action safety fix. It consumes Scene 4.12 in the released vector and renders Arc `CommandForm` shells plus query bindings for the canonical screen corpus. Earlier reading baselines: `4.43.0` (Scene 4.10, `b9a7c76`) and `v4.24.2` (`32dcac4`) |
-| cratis CLI | `3.40.0` (checkout `082df13`) | `cratis render`, `cratis run`; `Directory.Packages.props` pins `StageVersion` **4.49.1** and `ScreenplayVersion` **4.105.0**, and the `cratis run` container defaults to `cratis/stage:4.49.1`. Earlier reading baselines: 3.39.0 (`6b2beb5`) with Stage 4.43.0 / Screenplay 4.93.0; `v3.28.3` (`8b43fef`) with Stage 4.24.2 / Screenplay 4.66.0; `v3.28.2` (`141c499`, Cratis/cli#253) |
-| Screenplay | `4.105.0` query-shapes release | The canonical `ScreenComposition` corpus compiles `0 error(s), 0 warning(s)`, the MCP reports `sourceSuccess true`, `semanticSuccess true` and `executableReady true`, and CLI 3.40.0 renders it. Earlier baseline: 4.97.0 admitted what the CLI 3.39.0 bundle refused |
-| Rendered applications | Arc, Chronicle, Scene 4.12.0, .NET 10 | The Stage 4.49.1 render of the canonical corpus published `.cratis-render.json`, backend artifacts, `.frontend/**`, `scene.json`, `src/bindings.ts`, and package pins including Scene 4.10 packages in the generated app observed locally; verify the generated package set for each render before claiming a newer frontend runtime |
+| 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 |
 
 Everything below was read at those tags (`Source/Rendering.Cratis/**`, `README.md`,
 `Documentation/**` in Stage; `Source/Cli/Commands/Render/**` and
@@ -49,10 +51,10 @@ 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 parity for the canonical corpus is verified at CLI 3.40.0 / Stage
-4.49.1 for publication, command-form shell emission and query bindings. Browser
-runtime behavior, Studio Play and production deploy remain separate checks; Studio 0.136.3
-production deploy proof is pending the stale Pulumi lock.
+(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.
 
 ## Model-first rule
 
@@ -183,10 +185,11 @@ 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 Stage 4.49.1 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 generated artifact for each
+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
+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.15.1",
+  "version": "7.17.0",
   "description": "Configuration-aware Cratis AI integration for Pi",
   "type": "module",
   "files": [