Release v3.60.0

Added

• cratis screenplay baseline check [ROOT] and cratis screenplay baseline admit [ROOT] --release <LABEL> [--from-esm <FILE>] check a model against its committed release baseline and admit a release into it, using Screenplay's own baseline rules. They exit 0 when clean or admitted, 1 on violations and 2 when they could not run, so a CI job can gate on check and a release job can run admit --release $TAG. See the Screenplay command reference. (#351)
• cratis screenplay validate --open-questions report|fail reads the model's open questions from its notes. report prints them and keeps the validation result; fail exits 5 while an open question remains, and unreadable notes exit 1. (Cratis/Screenplay#694)
• cratis render admits ESM v16: an event's id pin keeps its stored event type name when you rename the event. (#353)

Changed

• Every cratis render, at application scope and for selected scopes, including --check, now runs Stage's publication check against the destination before writing. A render that would change an existing Chronicle event type id, or cannot read one safely, is refused with CLI-RENDER-016 and Stage's STAGE-EVENT-002 diagnostic; nothing is written and --force does not bypass it. Pin the event's id to keep its stored name. (#354)
• An existing destination file that cannot be read for that check is refused instead of failing with an unhandled error. (#354)
• The CLI bundles Screenplay 4.154.0 and Stage 4.96.0, which brings Chronicle 19.55.2 and Arc 22.87.0 to rendered applications.