Goal
Track explicit CLI admission of Screenplay ESM v6 from Cratis/Screenplay#369 and accepted decision 0022. A package bump must not imply render or execution support.
Current evidence
At cli 3f4b29687d39729c563bc7fd4c61139be2e7f8e4, Directory.Packages.props pins Screenplay 4.59.0 and Stage 4.23.0. Source/Cli/Commands/Render/ScreenplayPlanning.cs compiles an execution plan and delegates to the bundled Stage target, retaining its diagnostics; its specific version explanation covers v4, not v6.
At Stage fa485465f10ef6b93302d4f84173cc96164687fb, Screenplay is pinned to 4.60.0. SemanticCratisAdmission.Evaluate rejects versions outside EsmSchemaV3Support with STAGE-ESM-016 and admits only StateChange/StateView slice kinds. Stage rendering and shared execution remain tracked by Cratis/Stage#79 and Cratis/Stage#15. These observations do not claim CLI or Stage v6 support.
Acceptance
- Audit and explicitly declare CLI read/validate/render/run disposition for occurrence time, clocks, reactions, application triggers and captures; distinguish source validation from target admission.
- Until the provider admits a feature, preserve a blocking diagnostic and link its owning issue; never publish partial artifacts or report an unsupported run as passing.
- Exercise source-backed ReactionsCorpus.V6 with the actual bundled packages, including given-clock requirements, append consequences, callerless invocation and reached opaque Unsupported outcomes.
- Preserve v1–v5 behavior and unsupported v8/v9/v10 preflight rejection. Do not equate a dependency update with admission.
No consumer source changes are part of the Screenplay integration.
Status
State: Open
Scope: Explicit ESM v6 disposition across CLI consumer paths.
Delivered: - #287: cratis render admits ESM v5 to v7 and Stage 4.36.0 refuses the constructs it cannot render by name: reactions, captures, triggers and Automation/Translate slices (STAGE-ESM-024), read-model absence assertions (STAGE-ESM-027). Pinned by for_ScreenplayPlanning/when_planning_an_esm_v6_model with ReactionsCorpus.V6. cratis screenplay validate and cratis screenplay mcp admit v6.
Remaining: - cratis run: the Stage container's default eventmodel engine has no explicit v6 disposition, and ReactionsCorpus.V6 (given-clock requirements, append consequences, caller-less invocation, reached opaque Unsupported outcomes) is not exercised through it.
Goal
Track explicit CLI admission of Screenplay ESM v6 from Cratis/Screenplay#369 and accepted decision 0022. A package bump must not imply render or execution support.
Current evidence
At cli
3f4b29687d39729c563bc7fd4c61139be2e7f8e4,Directory.Packages.propspins Screenplay 4.59.0 and Stage 4.23.0.Source/Cli/Commands/Render/ScreenplayPlanning.cscompiles an execution plan and delegates to the bundled Stage target, retaining its diagnostics; its specific version explanation covers v4, not v6.At Stage
fa485465f10ef6b93302d4f84173cc96164687fb, Screenplay is pinned to 4.60.0.SemanticCratisAdmission.Evaluaterejects versions outsideEsmSchemaV3Supportwith STAGE-ESM-016 and admits only StateChange/StateView slice kinds. Stage rendering and shared execution remain tracked by Cratis/Stage#79 and Cratis/Stage#15. These observations do not claim CLI or Stage v6 support.Acceptance
No consumer source changes are part of the Screenplay integration.
Status
State: Open
Scope: Explicit ESM v6 disposition across CLI consumer paths.
Delivered: - #287:
cratis renderadmits ESM v5 to v7 and Stage 4.36.0 refuses the constructs it cannot render by name: reactions, captures, triggers and Automation/Translate slices (STAGE-ESM-024), read-model absence assertions (STAGE-ESM-027). Pinned byfor_ScreenplayPlanning/when_planning_an_esm_v6_modelwithReactionsCorpus.V6.cratis screenplay validateandcratis screenplay mcpadmit v6.Remaining: -
cratis run: the Stage container's default eventmodel engine has no explicit v6 disposition, andReactionsCorpus.V6(given-clock requirements, append consequences, caller-less invocation, reached opaque Unsupported outcomes) is not exercised through it.