cratis render: pass the release-baseline assessment to Stage and report STAGE-BASELINE warnings #356

Stage PR Cratis/Stage#385 (Cratis/Stage#375) makes a render plan warn when a release baseline says an event revision has already shipped (Screenplay decision 0070): STAGE-BASELINE-001 changed, STAGE-BASELINE-002 missing, STAGE-BASELINE-003 baseline unreadable or for another application, STAGE-BASELINE-004 check could not run or was made for another model revision. The warnings never refuse a render; screenplay baseline check (and cratis screenplay baseline check, #351) stay the CI gate.

Stage only warns when the caller supplies the assessment: SemanticModelLoader reads .screenplay/release-baseline.json from the model root, and callers that already hold an assessment pass it on ArtifactRenderRequest.ReleaseBaseline or through PlanFrom. A caller that passes only an executable model gets no baseline warnings.

What cratis render needs

• Compute the release-baseline assessment for the model being rendered and pass it to Stage, so cratis render (and --check, --scope) report STAGE-BASELINE-* warnings in text and JSON output, without changing the exit code or the published artifacts.
• For workspace-file input (the model is loaded from files rather than a model root), take the baseline from the model root that holds .screenplay/ and allow an explicit override, for example --baseline <FILE> or --model-root <DIR>, so a render from a copied or generated workspace can still be checked. No baseline file means no warnings and no error.
• Document the warnings and their relation to cratis screenplay baseline check and the publication check (CLI-RENDER-016).

Implementation waits for the Stage release that contains #385.

Status

State: Done — Released in v3.61.0 (PR #359).
Branch: cli-esm-v16 (#359)
Scope: Design now; implement after the Stage release with #385.
Delivered: Nothing yet.
Remaining: To be confirmed.
Follow-ups: None.