This page tracks the screens release against the original issue bodies. Each row is one acceptance criterion from a
scoped issue, marked with the strongest evidence that exists for it today:
Status
Meaning
PASS
Delivered and proven. A language-only criterion is proven by a merged specification; a behavior criterion by executing a released artifact against the canonical corpus. The proof is linked.
PARTIAL
Part of the criterion is delivered. The row states what remains, including any execution proof that has not run.
OPEN
Nothing delivered satisfies the criterion yet. The row states the required work.
A closed issue is not proof, and a merged pull request proves only that code exists. Behavior counts as proven when a
released artifact was executed. A run on a local build is listed as progress, not acceptance.
The matrix was reconciled on 9 and 10 October 2026, last against this vector:
Component
Version
Notes
Scene
4.14.0
Navigation diagnostics, template provenance and third-party design-time extensions (Scene#81); navigation history, template preview states and dual-host package proof (Scene#82).
Screenplay
4.124.0
Conformance harness and corpus, and screen composition syntax for exposures, instances and template content (Screenplay#602). The CLI and Stage bundle the 4.114.0 screen ABI.
Stage
4.51.3 / 4.52.0
4.51.3 is the CLI 3.41.0 default. 4.52.0 renders generated React applications on the Stage frontend runtime (Stage#289); no public CLI bundles it yet.
CLI
3.41.0
Defaults to Stage 4.51.3. Refuses a UI profile it cannot honor with nothing published, and lets cratis screenplay generate recover a rendered application (cli#301).
Studio
0.141.0
Deployed. Adds generation previews with digests, Play and static parity, guarded slice planning and migration checks (Studio#1638), and composite template selection (Studio#1639). Production requires a signed-in user, so no Studio behavior has run against it.
AI
7.20.0
Screen guidance names the passing public vector (AI#573); real MCP stdio transcript (AI#563).
Pass: 51 assertions, none blocked. Two-item scoped selection, only B’s comment, selected-row query and deep-link identity, delayed A response discarded, clear-selection, Create, Rename and AddComment with invalid and valid submits, persistence after reload, and the dark theme effect. Recorded as browser-native-controls-runtime-3.41.0-4.51.3 (Screenplay#630).
Failed: the work item list stayed empty (R1, fixed in Stage 4.51.1).
Browser runtime, public
CLI 3.40.5 + cratis/stage:4.50.0
Partial: 49 assertions pass, 2 are blocked. Scoped selection, the selected-row query and deep-link identity, the delayed A request, clear-selection, and Create, Rename and AddComment with invalid and valid submits all pass. So does the dark theme effect. B1 and B4 remain blocked.
Browser runtime, public
CLI 3.40.4 + cratis/stage:4.49.7
Partial. Endpoints, two-item seeding, list and row B details, dotted and punctuated stable ids, enabled native controls and an invalid native create that sends zero requests pass. Recorded as browser-native-controls-runtime-3.40.4-4.49.7 in ScreenCompositionCorpus.V1 (#596).
MCP stdio transcript
CLI 3.41.0
Pass. Initialize, 37 tools, open, propose, stale apply refused with StaleRevision, apply, and reopen with a changed revision and a preserved comment.
Pass. for_ScreenCompositionCorpus; the single-file, folder, reordered and relocated forms produce identical outcomes.
CLI render
CLI 3.41.0 + Stage 4.51.3
Pass, with two preserved guarded-action warnings. 38 artifacts, byte-identical across two renders, with no timestamps, foreign GUIDs, absolute paths or environment bytes (screen-composition-render-audit.cjs).
CLI profile rejection
CLI 3.41.0
Pass. A profile naming an unknown package is refused with CLI-RENDER-007 and one naming a missing layout with CLI-RENDER-008, each with exit 5 and nothing published; a modified managed scene.json is refused and left untouched. On CLI 3.40.6 both profile changes still published every artifact.
Render then recover
CLI 3.41.0
Pass. cratis screenplay generate recovers the rendered application to all 45 slices and command, event, read model and query members the source declares. CLI 3.40.6 refused it with CLI0017.
Studio production Play
Studio 0.141.0
Not executed. Automation exists (Studio#1628). Production returns 401 to every unauthenticated request; the run needs the access described under Studio production access.
Rerun every harness against the installed CLI, and the Stage image it defaults to, with one command:
It first runs the self-tests of the browser and render-audit harnesses, then the browser harness, the render audit
(determinism, portable artifacts, profile rejection and render-then-recover), the MCP transcript and the Studio
harness. It fails when the CLI or the started Stage image differs from the expected versions, so a drifted vector
cannot pass as the intended one.
Every browser blocker below passes on public CLI 3.41.0 with Stage 4.51.3, and did on CLI 3.40.7 with Stage 4.51.1.
The table keeps how each one cleared, so a regression can be traced. The browser assertions were never relaxed to
clear them.
Blocker
Cleared in
Earlier public observation
R1 Work item list
Stage 4.51.1
CLI 3.40.6 + Stage 4.50.1: the list bound to the single-item work-item-by-id route and stayed empty.
B1 Scoped comments
Stage 4.51.1
CLI 3.40.5 + Stage 4.50.0: A’s comment showed under B.
B2 Selected query identity
Stage 4.50.0
CLI 3.40.4 + Stage 4.49.7: no query carried the selected row’s identity.
B3 Deep-link identity
Stage 4.50.0
CLI 3.40.4 + Stage 4.49.7: the URL stayed #/WorkItemList.
B4 Stale response
Stage 4.51.1
CLI 3.40.5 + Stage 4.50.0: the delayed A request was aborted, but A’s comment still showed.
B5 Native fields
Stage 4.50.0
CLI 3.40.4 + Stage 4.49.7: no form inputs rendered.
B6 Theme effect
Stage 4.50.0
CLI 3.40.4 + Stage 4.49.7: the background did not change.
B7 Guarded actions
Not cleared, by design
Guarded Close and the double-click interaction stay fail-closed with STAGE-SCENE-ACTION-001 and STAGE-SCENE-INTERACTION-001.
Studio 0.139.0 is deployed at https://app.cratis.studio. Every path, including /, returns 401 without a session,
because the whole host sits behind Studio’s AuthProxy, which handles OpenID Connect sign-in and the invitation flow.
The production automation from Studio#1628
(scripts/screen-editor/check-studio-production-play.mjs) cannot get through that proxy as written. It authenticates
by sending the local development X-MS-CLIENT-PRINCIPAL headers for the test user Alice Admin, and AuthProxy strips
caller-supplied identity headers before forwarding. Those headers only work against a local Studio without AuthProxy.
To run it against production, the automation needs:
Requirement
Detail
A Studio user
A real account that can sign in through the production identity provider, is a member of an organization, and has access to a project.
A signed-in session
Sign in interactively once, save the browser state (for example with Playwright storageState), and have the automation load it instead of the Alice headers. Agents must not hold the account password.
A target event model
STUDIO_URL plus STUDIO_PROJECT_ID, STUDIO_APPLICATION_ID, STUDIO_DOMAIN_ID and STUDIO_EVENT_MODEL_ID, or a full STUDIO_EVENT_MODEL_ROUTE.
Fixture content
An event model whose screens include the destination the script edits (STUDIO_SCREEN_DESTINATION_ITEM, defaulting to Orders), and STUDIO_IMPORT_JSON_FILE for the import step.
Permission to write
The run saves, imports and starts Play in that project, so the account and project should be dedicated to testing.
Creating that account and choosing the project is a decision for the Studio owner; this harness does not create
accounts or change authentication.
The browser harness requires the add-comment form to expose a commentId input. The expectation is taken from the
authored model, not from what the runtime renders. In the corpus, AddComment declares
commentId CommentId identifier. The identifier is client-supplied rather than generated: the caller provides it, the
command routes CommentAdded to that event source with for commentId, and the slice’s own AddingAComment
specification supplies commentId when it executes the command. A native form for this command therefore has to
collect commentId.
The local CLI build with Stage 4.49.10 renders that input with the label “Comment Id” and submits the identifier the
user enters, together with the selected row’s workItemId.
when_reading_the_add_comment_command_identity pins this by reading the released corpus document. If the model ever
changes to commentId CommentId generated identifier, that specification fails first, and the browser assertion must
change from expecting an input to verifying the generated identifier in the projection.
A master/detail application binds a query to a table, selection to details, and an auto/manual multi-column form.
PASS
Query table, selection driving details, and native command forms with validation and submission all pass in the browser. Proven on public CLI 3.41.0 with Stage 4.51.3 (browser-native-controls-runtime-3.41.0-4.51.3).
Survives Screenplay parse, print and MCP edits. Studio save/export/import has not run, because production Studio is not deployed.
7.3
One package contract across Studio, embedded Event Models/VS Code, Stage runtime and generated React.
PARTIAL
Scene hosts cover standalone, embedded and webview rendering (Scene#79); the Stage runtime loads the package profile. The embedded host and generated React are not exercised.
7.4
An AI agent creates and modifies the multi-file application through Screenplay MCP; examples compile and run.
PARTIAL
MCP authoring and the stdio transcript pass on CLI 3.41.0, and the authored application runs in the browser. An AI-edited application has not been run end to end.
7.5
Studio Play uses the full surface with only the upper-right toolbar and restores authoring chrome on Stop.
The canonical release vector proves runtime and render behavior and CLI/Studio parity, with no silent fallback.
PARTIAL
Runtime and render pass on public CLI 3.41.0 with Stage 4.51.3, deterministically, with portable artifacts, profile rejection and recovery. Studio parity has not run.
Typed data-context, query, component-output and literal sources (Scene#77); preserved cleared values (Scene#78). Runtime null behavior is not observed (B1).
69.2
Expose output properties such as the selected item and propagate them to a detail component or query parameter.
PARTIAL
Component output scope (Scene#77) and selected-row outputs (Stage#275). Propagation into the comment query fails (B1, B2).
69.3
Validate types, scope, missing or renamed elements, lifecycle cleanup and cycles.
PARTIAL
Resolver diagnostics for cycles, missing components and type mismatches, plus lifecycle cleanup (Scene#77). No negative binding vector exercises them; tracked with 168.3.
69.4
One shared runtime resolver with C#/TypeScript parity, not a Studio-only evaluator.
PARTIAL
Stage renders through the Scene runtime (Stage#244). No conformance vector compares the C# and TypeScript resolvers.
69.5
Executable proof of master/detail selection, clearing, nested template scope and query rebind.
PASS
Selection, clearing, the comment query rebinding to the selected row, and discarding a delayed response for the previous row all pass in the browser. Proven on public CLI 3.41.0 with Stage 4.51.3 (browser-native-controls-runtime-3.41.0-4.51.3).
Scene#70 package designers and design-time actions
Versioned extension points for previews, designers, property editors and display renderers, with fallbacks.
PARTIAL
Generic lookups for previews, designers, property editors, displays and actions, with a fallback and a diagnostic for each unknown or incompatible extension (Scene#81). No executed host run loads them.
70.2
Actions with stable identity and owner-controlled state that run canonical edit batches; separate from application commands.
PARTIAL
runDesignTimeAction submits an action’s canonical edit batch whole or not at all (Scene#81); Studio runs batches through editor history (Studio#1608). Owner-controlled visible and enabled state is not verified.
70.3
Platform-neutral metadata in Scene.Model; design-time React in an optional bundle.
PARTIAL
Runtime-only and design-time packages are separated (Scene#79). No harness asserts that a runtime host loads no design-time code.
70.4
Research and record WinForms/ASP.NET designer patterns.
PASS
A design record compares the WinForms and ASP.NET designer patterns with Scene’s extension points (Scene#81).
70.5
A third-party component supplies every extension point, with unknown-extension diagnostics and a Generate fields action.
PARTIAL
Third-party design-time extensions load through the generic host with unknown-extension diagnostics (Scene#81). No third-party fixture supplies every extension point and a Generate fields action.
Scene#71 auto and authored multi-column CommandForms
Adds a MasterDetail screen template (Scene#82) to the list, live list and command form blueprints (Scene#78). Dashboard and settings templates are not evidenced.
73.3
Templates use shared categories, exposed configuration, bindings, toolbar actions and recursive slots.
PARTIAL
Applicability, categories and scopes (Scene#76, Scene#78). Exposed configuration is not exercised by a vector.
73.4
Package-backed previews with realistic data, empty, loading and error states, responsive and accessible.
PARTIAL
Previews take a populated, empty, loading or error state, and the data table announces loading and error (Scene#82). Accessibility and responsive behavior are not verified by an executed run.
73.5
Compatibility, attribution and license metadata, and tests, for each template.
PARTIAL
TemplateMetadata carries compatibility ranges, attribution and an SPDX license, validated by validateTemplateMetadata (Scene#81). Not every shipped template is shown to carry them.
Scene#74 navigation, URLs and toolbar destinations
Stable destination identity, named outlet, route and typed parameters.
PASS
Stable destinations with typed route parameters: the selected row’s identity reaches the URL as #/WorkItemDetails?workItemId=<B>. Proven on public CLI 3.41.0 with Stage 4.51.3 (browser-native-controls-runtime-3.41.0-4.51.3).
74.2
Recursive composition that resolves navigation into the correct outlet.
PARTIAL
Outlets declare the template types they accept (Scene#81), and the selected row resolves into the details outlet in the browser. Recursive nested composition is not exercised.
74.3
Toolbar items configure label, icon, presentation, slice and destination.
PARTIAL
Authored, parsed and rendered as controls. The dialog destination flow is blocked by B5.
74.4
URL overrides, deep links, refresh, back/forward, dialog close/return and parameters.
PARTIAL
Browser history, refresh, dialog close and return, and URL parameters are delivered (Scene#82); the deep link and dialog open and close pass on public CLI 3.41.0 with Stage 4.51.3. Back/forward and refresh are not asserted by the harness.
74.5
Diagnose duplicate routes, incompatible or missing outlets, cycles and unavailable targets.
PARTIAL
diagnoseNavigation reports duplicate routes, missing and incompatible outlets, cycles and unavailable targets in TypeScript and C# (Scene#81). No negative navigation vector runs it.
Package-backed custom designer output and exposed inherited settings; deterministic data and identities.
PARTIAL
Deterministic data and identities are pinned. The corpus has no package-backed custom designer output.
168.3
Negative vectors for incompatible types and packages, missing outlets and references, and cycles; round-trip and behavior expectations.
PARTIAL
Round-trip and behavior expectations exist. Negative screen vectors for packages, outlets and cycles do not.
168.4
Consumers use the released corpus package, with no copied fixtures.
PASS
Stage consumes Cratis.Screenplay.CanonicalCorpus 4.114.0 (when_planning_the_screen_composition_corpus_scene); the MCP transcript requires --corpus and has no built-in fixture.
168.5
Application, document, semantic, event-contract and specification ids are reviewed literals.
PASS
Pinned in when_loading_the_v1_screen_corpus.
168.6
Single-file, folder, reordered and relocated forms produce identical bytes, ids and outcomes.
PASS
Pinned per form in for_ScreenCompositionCorpus.
168.7
Copied Screenplay fixtures migrate with byte and semantic parity before v2.
Stage consumes the corpus and pins ordered artifact paths, hashes and bytes.
PARTIAL
Pinned for RegisterProject (Stage#75). The screens vector pins the Scene digest, not every artifact.
168.9
The CLI materializes the corpus forms and produces exactly the Stage plan.
PARTIAL
CLI 3.41.0 renders the authored composition deterministically. Plan parity with Studio has not run.
168.10
Studio export matches the corpus source, identities, ESM and Stage plan.
OPEN
Studio export has not run; production Studio is not deployed.
168.11
Arc/Generation render-then-recover compares portable ids, contracts and outcomes.
PASS
screen-composition-render-audit.cjs renders the corpus with CLI 3.41.0, recovers it with cratis screenplay generate, and finds all 45 slices and command, event, read model and query members the source declares, with none missing or added.
168.12
v2 preserves ids, advances the event revision, removes the payload id and carries stream context.
Unsupported, stale or conflicting vectors commit zero artifacts or model changes.
PARTIAL
A stale MCP apply is refused with StaleRevision, and a refused UI profile publishes nothing on CLI 3.41.0. Unsupported screen semantics still publish with guarded warnings (B7).
168.14
The corpus package is test-framework-free and consumers stay deterministic.
PASS
Screenplay.CanonicalCorpus references only the Screenplay compiler.
Run the application through Studio authoring/export, Studio Play, CLI run and generated React.
PARTIAL
CLI run passes on public CLI 3.41.0 with Stage 4.51.3. Generated React renders on the Stage runtime in Stage 4.52.0 (Stage#289), not yet from a public CLI. Studio has not run.
173.2
Compare plans, package resolution, artifact bytes and behavior across consumers.
PARTIAL
Only the CLI side runs, and it passes. Studio and generated React are not compared.
173.3
A host-configured package set in embedded rendering; consistent diagnostics, no fallback UI.
OPEN
No embedded-host run.
173.4
Record the exact released matrix and browser results before closing the tracker.
PARTIAL
Recorded for every public vector so far in ReleasedVectorResults; not yet green.
173.5
CLI and Studio use the same released Screenplay and Stage packages.
OPEN
Studio is not deployed on the released vector.
173.6
Identical inputs produce identical profile and plan digests.
PARTIAL
Two CLI 3.41.0 renders of the same input are byte-identical across all 38 artifacts. Studio reports deterministic profile and plan digests (Studio#1638); the two have not been compared.
173.7
Artifact paths, bytes and hashes are byte-identical.
OPEN
Requires both consumers.
173.8
Unsupported semantics produce matching diagnostics and zero artifacts.
PARTIAL
Guarded-action warnings and PLAY0268/PLAY0269 are preserved on the CLI side only.
173.9
Both consumers reject changed or stale profile inputs.
PARTIAL
CLI 3.41.0 rejects a changed profile (unknown package CLI-RENDER-007, missing layout CLI-RENDER-008) and a modified managed artifact, each with nothing published. The Studio side has not run.
173.10
The test runs from package dependencies, not repository source copies.
PARTIAL
The browser harness runs the published CLI and image. It reads the corpus source from this repository rather than from the package.
173.11
Version or digest drift fails loudly before publication.
PARTIAL
run-public-acceptance.sh fails on an unexpected CLI version or Stage tag. No gate runs before publication.
173.12
No timestamps, random GUIDs, absolute paths or environment bytes in artifacts.
PASS
All 38 artifacts of a CLI 3.41.0 render contain no timestamps, no GUIDs absent from the source, no absolute paths and no host, user or folder bytes (screen-composition-render-audit.cjs, which plants each case in its self-test).
173.13
The final release candidate reruns parity against the pinned matrix as the closing record.
OPEN
Not reached. run-public-acceptance.sh is that rerun.
A capability matrix from the release tracker to syntax, semantics, missing constructs and diagnostics.
PARTIAL
This page maps criteria to proof; the construct-level capability matrix maps each criterion to syntax, semantics, diagnostics and what is not expressible.
Parser-printer-parser preservation and multi-file edits; validate references and cycles.
PARTIAL
Round-trip and multi-file MCP edits pass. Re-exposure cycles and broken references are diagnosed (PLAY0621 to PLAY0632, Screenplay#602), but no corpus vector pins them.
536.5
.NET and TypeScript parsers, schema, printers, language services and documentation together; authoring distinct from executable readiness.
PARTIAL
Both compilers are held together by the conformance documents, and backend ESM refuses UI with PLAY0268/PLAY0269 as intended. Editor surfaces are not verified here.
536.6
Design-time functions stay in packages; their output has a Screenplay representation.
PARTIAL
No callbacks are serialized. Package-produced output has no corpus vector.
Compile once into one shared typed plan for disk rendering and live hosting.
PARTIAL
One Scene with native command form metadata serves both the live Stage and generated applications (Stage#289). Disk and live outputs are not compared by a conformance run.
236.2
A complete buildable React app with shells, routing, outlets, dialogs, bindings and icons.
PARTIAL
cratis render emits the Stage frontend runtime into the generated application, with routes, Scene, theme and pinned packages (Stage#289, Stage 4.52.0). Public proof waits for a CLI that bundles Stage 4.52.0.
Explicit package composition; no silent fallback to a default shell or flattened screen.
PARTIAL
The authored composition renders. Unsupported guarded actions warn rather than block; that policy is preserved, not resolved.
236.5
Determinism, diagnostics, zero-output failures and building the full fixture.
PARTIAL
Stage’s Verification/generated-react-browser builds the generated application and runs the browser scenarios against it (Stage#289). Not yet run from a public CLI.
Real query data, reactive bindings, command inputs, validation and responses, and package components.
PASS
Real query data, selection-driven bindings, native command inputs with validation and responses, and package components all pass in the browser. Proven on public CLI 3.41.0 with Stage 4.51.3 (browser-native-controls-runtime-3.41.0-4.51.3).
237.2
The recursive hierarchy with authored URLs, outlets, dialogs and toolbars.
PARTIAL
URLs and the parameterized details outlet pass on public CLI 3.41.0 with Stage 4.51.3. Recursive hierarchy beyond the corpus is not exercised.
237.3
Production lifecycle, loading, error and empty states, and admission diagnostics; authorization preserved.
PARTIAL
Guarded actions stay fail-closed (B7), and forms without metadata fail closed (Stage#275). Loading and error states are not asserted.
237.4
The same scenarios against live Stage and generated React.
PARTIAL
The live scenarios pass on public CLI 3.41.0 with Stage 4.51.3; Stage runs the same scenarios against a generated application (Stage#289). Not yet from a public CLI.
237.5
Studio Play and CLI run host this runtime without Studio-specific semantics.
PARTIAL
CLI run hosts it. Studio Play on the released runtime has not run.
Resolve the application context and UI profile for cratis run and cratis render.
PASS
cli#293; the folder source renders and runs with the Desktop profile.
284.2
Forward bundles, assets and profile to the released Stage runtime and planner; custom packages work without Studio.
PARTIAL
Built-in packages forward. A custom package set is not exercised.
284.3
Input scoping, import safety, read-only mounts and compatibility checks; diagnose before reporting success.
PASS
CLI 3.41.0 diagnoses an unknown package (CLI-RENDER-007) and a missing layout (CLI-RENDER-008) before publishing, with nothing published and earlier managed artifacts untouched, and refuses a modified managed artifact without --force.
284.4
Integration tests run the multi-file app, exercise deep links, forms and outlets, and launch the rendered React.
PARTIAL
The multi-file app runs, with deep links, forms and outlets passing on public CLI 3.41.0 with Stage 4.51.3. Launching the rendered React waits for a CLI bundling Stage 4.52.0.
284.5
Document configuration and the compatible package and image set.
PARTIAL
This page records the compatible set. The CLI documentation is not verified here.
Screen authoring and guidance name the passing public vector (AI#573). Design-time generation results are not covered.
536.2
An agent workflow that creates and edits the multi-file app through MCP, then runs and renders it.
PARTIAL
Create and edit through MCP pass, and the authored application runs in the browser. Running an AI-edited application end to end has not been exercised.
536.3
Correct old limitations only after upstream ships; distinguish authoring, admission and runtime support.
PASS
Guidance was updated only after the public vector passed: older-vector gaps are removed, and the guarded Close and double-click refusals stay (AI#573).
536.4
Compile examples, run the MCP transcript and runtime smoke coverage; skill routing finds the workflow.
PARTIAL
The MCP transcript and the browser runtime pass on CLI 3.41.0. Skill-routing coverage is not verified here.
536.5
Link the Screenplay-owned fixtures rather than copying them.
PASS
The transcript has no built-in fixture: it requires --corpus and copies the Screenplay corpus into a scratch folder for each run.
No Studio behavior has been executed against the deployed build: production requires a signed-in user (see
Studio production access). Merged implementation is listed so that, where it exists, only the production execution remains.
StudioIssues#156 the Scene-based editor with designers and actions
Another owner closed this issue on 8 October 2026 under decision 0012
(Studio#1610) and moved the remaining implementation to StudioIssues#275
and Screenplay#536. The closure is a scoping decision, not proof of native delivery, so its criteria are tracked here.
#
Criterion
Status
Evidence or remaining work
165.1
Export and import every authored UI element without loss.
PARTIAL
Typed transport (Studio#1615, Studio#1620) and destination metadata through import and export (Studio#1624). No golden production export has run.
165.2
Preserve hierarchy and qualified references across folder export and import.
PARTIAL
Preserved by the Screenplay transport. The Studio folder round-trip has not run.
165.3
Feed the same application into Play and static rendering.
PARTIAL
Studio feeds the same typed Screenplay to Play and to static generation (Studio#1636). Not executed in production.
165.4
Unsupported UI blocks or is reported; never empty Screens output.
PARTIAL
Export warns about a dropped screen (Studio#1569). Blocking behavior has not run.
165.5
Golden save, export, compile, import and reopen cases.
Pass the complete UI and package composition into the shared Stage plan for preview and implementation.
PARTIAL
Typed transport exists. Plan parity with the CLI has not run.
275.2
Studio Play on the released Stage runtime; diagnostics before a partial frontend.
PARTIAL
Play and specification runs use the Stage 4.49.9 images, and export names any member that keeps a screen out of Play (Studio#1636). Not executed in production.
275.3
Prove the application through preview, Play and generated output; retire legacy under the parity gate.
OPEN
Not executed.
275.4
One exact Stage package version and one facade for preview and implementation.
PARTIAL
Studio builds on Screenplay 4.114 and Stage 4.49.9, one version for Play and generation (Studio#1636). The CLI now defaults to Stage 4.50.1, so the two consumers differ.
275.5
The input is the compiled model and execution plan, not a pruned event model.
PARTIAL
Typed Screenplay transport (Studio#1620). Not verified against the plan.
275.6
A read-only preview of paths, bytes, hashes, diagnostics and gaps.
PARTIAL
A generation preview lists each file with size, hash and status, with the digests, diagnostics and gaps (Studio#1638). Not executed in production.
275.7
No target-specific rendering logic left in Studio.
OPEN
Not audited.
275.8
Deterministic profile and plan digests for corpus input.
PARTIAL
Studio reports deterministic profile and plan digests regardless of file order or location (Studio#1638). Not run against the corpus.
275.9
Retire legacy generation behind a flag once parity is green.
A dry-run, resumable, idempotent migration before the release.
PARTIAL
A guarded migration tool exists: a read-only plan, and an apply that refuses production, requires --max-subjects, stops rather than trimming and is a no-op on a second run (Studio#1636). Not run against data before the release.
470.2
Preservation checks for templates, identities, exposed values and bindings; report malformed documents.
PARTIAL
The migration checks each document keeps inherited templates and slots, component identities and exposed values, and writes a report; apply --resume never migrates a screen twice (Studio#1638). Not run against data.
470.3
Export and import parity on migrated documents without rewriting events.
OPEN
No migrated documents have been exported or imported.
The full UI comes from the same plan as Play; the scaffolding boundary is preserved.
PARTIAL
Static generation renders through Stage from the same typed Screenplay as Play (Studio#1636). Not executed in production.
502.2
Screen artifacts in the ownership manifest; gaps block publication.
PARTIAL
Implementation gaps and Stage errors block before anything is written (Studio#1638). Not executed.
502.3
Validate the generated full application, not backend slices.
OPEN
Not run.
502.4
Screenplay first, then Stage, as two commits in one session.
PARTIAL
Slice implementation commits the Screenplay before the code (Studio#1638). Not executed.
502.5
Render exactly the unit of work’s feature and slices into the right folders.
PARTIAL
Generation writes into a folder the user selects and refuses one outside the application’s source folder (Studio#1636). Not executed.
502.6
Never write scaffold files.
PARTIAL
Slice implementation writes only the slice’s own files and never scaffold files (Studio#1638). Not executed.
502.7
Errors and gaps block with nothing committed.
PARTIAL
Generation is refused with the reason shown when a screen cannot be rendered or nothing would be generated (Studio#1636). Not executed.
502.8
The same input produces byte-identical output.
PARTIAL
Generation reports files already up to date (Studio#1636). Byte identity is not verified for Studio; the CLI render of the same corpus is byte-identical.
Native generation mode (Studio#1621). Not executed in production.
556.2
A Generate fields action with correct state and non-destructive behavior.
PARTIAL
Generated command fields (Studio#1608, Studio#1621). Visibility and non-destructive behavior are not verified.
556.3
Edit columns and widths; drag fields among columns and resize them on the canvas.
PARTIAL
Manual placement, unequal widths, gaps and spans (Studio#1621). Not executed in production.
556.4
Canvas and properties stay synchronized with the model, validation and undo/redo; schema changes handled.
PARTIAL
Geometry persists through undo, dirty state, save and reload (Studio#1621). Schema-change handling is not verified.
556.5
Save and reopen, round-trip and runtime-render equivalence for a two-column form.
PARTIAL
Runtime rendering of command-form fields with validation and submission passes on public CLI 3.40.5 + Stage 4.50.0 (B5). Studio save and reopen of a two-column form has not run in production.
Searchable categorized browsing with previews, provenance and compatibility.
PARTIAL
A Scene-backed template selector (Studio#1614); every package template, including composite ones, can now be chosen (Studio#1639). Search and provenance are not evidenced.
557.2
Scene types and applicability rules, including custom categories.
PARTIAL
Category and scope editing (Studio#1614) over Scene applicability (Scene#76). Not executed in production.
557.3
Choose or inherit a template at every scope, with slot fit and inherited visuals.
OPEN
Not executed.
557.4
Realistic package previews at different sizes; draft, apply and discard preserved.
OPEN
Not executed.
557.5
Large catalogs, keyboard navigation, unavailable packages and selection persistence.
