[woksin]

Added

• cratis render (publish, --check and --scope) reports Stage's release-baseline warnings when a render would change (STAGE-BASELINE-001) or drop (STAGE-BASELINE-002) an event revision admitted to the model's release baseline, or when the baseline cannot be read (STAGE-BASELINE-003) or checked (STAGE-BASELINE-004). The warnings cover the whole application, also for scoped renders, and never change the exit code, the written artifacts or the receipt; keep cratis screenplay baseline check as the gate in CI. See Release-baseline warnings. (cratis render: pass the release-baseline assessment to Stage and report STAGE-BASELINE warnings #356)
• cratis render --workspace <FILE> --baseline <FILE> selects the release baseline for workspace input; without it, render uses .screenplay/release-baseline.json beside the workspace file. PATH input reads the baseline from the model root's .screenplay/ folder. (cratis render: pass the release-baseline assessment to Stage and report STAGE-BASELINE warnings #356)

Changed

• The CLI bundles Stage 4.97.0.

[woksin]

Reviewer notes

• Design: PATH input bridges through Screenplay's read-only ReleaseBaselineCommands.Check(root) because Stage's StageReleaseBaseline.Check(compilation) is always unavailable for the temporary identities a PATH render uses; the result is stamped with the rendered model revision (documented in code). Upstream gaps that would remove the bridge: Public API to open a model root as a workspace with its persisted identities Screenplay#740 (open a model root with persisted identities) and SemanticModelLoader cannot read a model root's .screenplay/identities.json (MCP identity wrapper) Stage#388 (loader can't read the MCP identity wrapper).
• Full cross-provider review: round 1 found one blocking issue (an exception type from the root reader escaped and failed the render); fixed in e08f56a by mapping every non-cancellation failure to STAGE-BASELINE-004; round 2 passed with 0 blocking.
• Local: Release build clean; docs, pack and packaged placement green; Cli.Specs 3965 passed with 6 failures all in for_LinuxDirectSecrets (load flake on this machine, passes 20/20 alone; filed for_LinuxDirectSecrets specs time out waiting 10 s for the fake secret tool under load #358); Chronicle integration and Templating green.
• Rendered React lane not run locally (it hits the Stage harness race generated-react-browser harness runs scenarios before the host's read models are registered Stage#387 on this loaded machine); CI's dotnet-build job covers it, as it did for Release baseline commands, open-question gate, ESM v16 and event identity publication check #357.