Release v4.97.0

Summary

Stage now warns when a render would change or drop an event revision that a release baseline says has already shipped (Screenplay decision 0070). The warnings never stop the render; screenplay baseline check remains the gate in CI.

Added

• StageReleaseBaseline.Check builds a ReleaseBaselineAssessment from a Screenplay workspace or a compilation and a release baseline, using Screenplay's own baseline comparison. SemanticModelLoader reads .screenplay/release-baseline.json from the model root (it never writes it) and exposes the result as ReleaseBaseline. Callers that already hold an assessment pass it on ArtifactRenderRequest.ReleaseBaseline or through PlanFrom. (#375)
• Render plans that carry an assessment report warnings for the whole application, whatever the render scope: STAGE-BASELINE-001 when an admitted event revision changed, STAGE-BASELINE-002 when it is missing, STAGE-BASELINE-003 when the baseline cannot be read or belongs to another application, and STAGE-BASELINE-004 when the check could not run or was made for a different model revision. A plan with only these warnings still succeeds with the same artifacts. Without an assessment, plans are unchanged. (#375)
• The rendering guides explain where the baseline comes from, how these warnings relate to the screenplay baseline check gate and to the publication check, and that callers that pass only an executable model get no baseline warnings. (#375)

Changed

• Stage builds on Screenplay and its canonical corpus 4.154.0. (#375)